date:20180302

** Changed in: ppp (Debian)
   Status: Unknown => Fix Released

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

Title:
  ppp 2.4.7-2+1ubuntu1 bionic mschap broken

Status in ppp package in Ubuntu:
  Confirmed
Status in ppp package in Debian:
  Fix Released

Bug description:
  pppd 2.4.7-2+1ubuntu1 breaks vpn connections to Windows and Mikrotik Servers.
  It seams only mschap is broken.
  manually compiling https://github.com/paulusmack/ppp/ fixes it, so the problem
  seams to be downstream.

  Removing replace-vendored-hash-functions.patch seams to fix the
  problem

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

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

[Desktop-packages] [Bug 335662] Re: [jaunty] hplip status service cannot find system tray

2018-03-02 Thread dino99

this works as expected since ages; but it have settings. So reconfigure
it if it does display as you would like. Otherwise it might be a 'theme'
related issue on your side.

** Changed in: hplip
   Status: Fix Committed => Fix Released

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

Title:
  [jaunty] hplip status service cannot find system tray

Status in HPLIP:
  Fix Released
Status in hplip package in Ubuntu:
  Fix Released
Status in hplip package in Debian:
  Fix Released

Bug description:
  Binary package hint: hplip

  After login to ubuntu hplip status service cannot find system tray. It
  shows dialog box: "No system tray detected on this system. Unable to
  start, exiting".

  hplip version is 2.8.12-3ubuntu1 on jaunty

  I found the same bug reported in Debian
  http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg618714.html

  Regards

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

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

[Desktop-packages] [Bug 1629251] Re: Some app-indicators not showing menus

2018-03-02 Thread dino99

@Simon

If you think understanding that report, tell me why 'importance' & 'assigned to 
' are still not set by devs ?
When that report have been opened (2016), there was a transitional time where 
many users have hit the problem, then only a few (with rolling systems/mixed 
install/...)
About xenial, it will never receive 'cosmetic' fixed but only 'security' ones 
and maybe some SRU/backport; nothing related to such report.

So you can still spend your time to undo what i have set, its useless
and does not help to get solutions nor 'makes ubuntu better'.

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

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

** Changed in: appmenu-qt (Ubuntu)
   Status: New => Incomplete

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

Title:
  Some app-indicators not showing menus

Status in appmenu-qt package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Impact
  ==
  In Ubuntu 16.10 the menus of the Dropbox and hplip app-indicators are not 
working. I attach a video of the problem.

  Test Case
  =
  sudo apt install hplip-gui
  Log out
  Log in (to Unity)
  Click the hp indicator in the top left of the screen.
  Does it show items or is it blank?

  appmenu-qt 0.2.7+14.04.20140305-0ubuntu2  is installed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity 7.5.0+16.10.20160906.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Fri Sep 30 11:44:26 2016
  DistUpgraded: 2016-09-01 11:00:51,009 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.4.0-9136-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-11-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-15-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-16-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to yakkety on 2016-09-01 (29 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 08:45:37 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1629251/+subscriptions

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

[Desktop-packages] [Bug 1629251] Re: Some app-indicators not showing menus

2018-03-02 Thread Simon Quigley

> Unity is dead; nobody will spend time about it.

You're wrong there, Unity is still maintained and will be for the rest
of the 16.04 cycle at minimum.

Also, about the "mixed install" part of this, that shouldn't matter, as
this is reported against appmenu-qt.

Please, stop marking the status to Invalid. Let's keep it at New where
it belongs.

** Changed in: appmenu-qt (Ubuntu)
   Status: Invalid => New

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

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

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

Title:
  Some app-indicators not showing menus

Status in appmenu-qt package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Impact
  ==
  In Ubuntu 16.10 the menus of the Dropbox and hplip app-indicators are not 
working. I attach a video of the problem.

  Test Case
  =
  sudo apt install hplip-gui
  Log out
  Log in (to Unity)
  Click the hp indicator in the top left of the screen.
  Does it show items or is it blank?

  appmenu-qt 0.2.7+14.04.20140305-0ubuntu2  is installed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity 7.5.0+16.10.20160906.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Fri Sep 30 11:44:26 2016
  DistUpgraded: 2016-09-01 11:00:51,009 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.4.0-9136-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-11-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-15-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-16-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to yakkety on 2016-09-01 (29 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 08:45:37 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1629251/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-02 Thread Simon Quigley

I'm subscribing Jeremy Bicha for a review because he is the last
uploader of this package.

Thanks, and sorry for the delay!

-- 
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 1721707] Re: Rhythmbox crashes after pressing "Install Additional Software"

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

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

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

Title:
  Rhythmbox crashes after pressing "Install Additional Software"

Status in rhythmbox package in Ubuntu:
  Expired

Bug description:
  Steps:

  1. Add .m4a music to the library (or any music with not installed codecs)
  2. Go to 'Import Errors' on the left sidebar
  3. Press 'Install Additional Software' at the bottom right
  4. Rhythmbox crashes

  I attached a backtrace.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: rhythmbox 3.4.1-2ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 09:11:16 2017
  InstallationDate: Installed on 2017-10-02 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1753039] [NEW] unable to install Filezilla - error: package libjpeg62:amd64 1:6b2-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstal

2018-03-02 Thread Peter Smerdon

Public bug reported:

Could not find Filezilla on system - though I'm sure I've used it before.
Cannot reinstall Fileszilla from "Ubuntu Software" or apt-get install command.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjpeg62:amd64 1:6b2-2
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sat Mar  3 14:32:36 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu10
DuplicateSignature:
 package:libjpeg62:amd64:1:6b2-2
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package libjpeg62:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-01-10 (51 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: libjpeg6b
Title: package libjpeg62:amd64 1:6b2-2 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  unable to install Filezilla - error: package libjpeg62:amd64 1:6b2-2
  failed to install/upgrade: package is in a very bad inconsistent
  state; you should  reinstall it before attempting configuration

Status in libjpeg6b package in Ubuntu:
  New

Bug description:
  Could not find Filezilla on system - though I'm sure I've used it before.
  Cannot reinstall Fileszilla from "Ubuntu Software" or apt-get install command.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg62:amd64 1:6b2-2
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar  3 14:32:36 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu10
  DuplicateSignature:
   package:libjpeg62:amd64:1:6b2-2
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libjpeg62:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-10 (51 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libjpeg6b
  Title: package libjpeg62:amd64 1:6b2-2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1621539] Re: Unable to schedule "PM" events in Gnome Calendar 3.20.2

Alan, please open a new bug. You can run this command to include useful
information for the bug triagers:

ubuntu-bug gnome-calendar

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

Title:
  Unable to schedule "PM" events in Gnome Calendar 3.20.2

Status in GNOME Calendar:
  Fix Released
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Xenial:
  Fix Released

Bug description:
  Impact
  ==
  Users who have their computer time set to 12-hour time (AM/PM) instead of 
24-hour are unable to schedule PM events in gnome-calendar. 12-hour time is the 
default in the United States.

  The update fixes this issue and a few more.

  https://git.gnome.org/browse/gnome-calendar/tree/NEWS?h=gnome-3-20
  https://git.gnome.org/browse/gnome-calendar/log/?h=gnome-3-20

  Test Case
  =
  1. Open the Calendar app.
  2. Click on a date to schedule a new event. Click Edit Details.
  3. Are you able to set an event that starts and ends in the afternoon?

  Open the System Settings app. Click Time & Date. Switch time from
  12-hour to 24-hour (or the opposite). Repeat steps 1-3.

  4. Schedule a new event that starts on one day and ends on the next.
  Click the all-day box and hit Done.

  The event should span both days on the calendar.

  Regression Potential
  
  Low. This is a new upstream stable bugfix release and is recommended for all 
distros shipping GNOME 3.20.

  The 3.20.3 release was insufficient and might have made things worse (
  https://bugzilla.gnome.org/770679 ), but for 3.20.4 I helped identify
  the git commits already applied in the 3.21 series to fix this issue.

  Original Bug Report
  ===
  The bug is 100% reproducible. I can schedule "AM" events and all day events, 
but no "PM" events. I would expect the part of to advance after I had passed 
noon, but I can keep cycling through the first 12 hours of the day.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.20.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep  8 10:56:05 2016
  InstallationDate: Installed on 2013-04-26 (1231 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to xenial on 2016-04-02 (159 days ago)

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

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

[Desktop-packages] [Bug 1621539] Re: Unable to schedule "PM" events in Gnome Calendar 3.20.2

2018-03-02 Thread Alan Van Art

This is still broken as of 3.20.4. I am linked to Google Calendars and
seeing 24hr format regardless of time format setting.

** Attachment added: "screen shot"

https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1621539/+attachment/5067676/+files/Screenshot%20from%202018-03-02%2021-43-39.png

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

Title:
Unable to schedule "PM" events in Gnome Calendar 3.20.2

Status in GNOME Calendar:
Fix Released
Status in gnome-calendar package in Ubuntu:
Fix Released
Status in gnome-calendar source package in Xenial:
Fix Released

Bug description:
Impact
==
Users who have their computer time set to 12-hour time (AM/PM) instead of
24-hour are unable to schedule PM events in gnome-calendar. 12-hour time is the
default in the United States.

The update fixes this issue and a few more.

https://git.gnome.org/browse/gnome-calendar/tree/NEWS?h=gnome-3-20
https://git.gnome.org/browse/gnome-calendar/log/?h=gnome-3-20

Test Case
=
1. Open the Calendar app.
2. Click on a date to schedule a new event. Click Edit Details.
3. Are you able to set an event that starts and ends in the afternoon?

Open the System Settings app. Click Time & Date. Switch time from
12-hour to 24-hour (or the opposite). Repeat steps 1-3.

4. Schedule a new event that starts on one day and ends on the next.
Click the all-day box and hit Done.

The event should span both days on the calendar.

Regression Potential

Low. This is a new upstream stable bugfix release and is recommended for all
distros shipping GNOME 3.20.

The 3.20.3 release was insufficient and might have made things worse (
https://bugzilla.gnome.org/770679 ), but for 3.20.4 I helped identify
the git commits already applied in the 3.21 series to fix this issue.

Original Bug Report
===
The bug is 100% reproducible. I can schedule "AM" events and all day events,
but no "PM" events. I would expect the part of to advance after I had passed
noon, but I can keep cycling through the first 12 hours of the day.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-calendar 3.20.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 8 10:56:05 2016
InstallationDate: Installed on 2013-04-26 (1231 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to xenial on 2016-04-02 (159 days ago)

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

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

[Desktop-packages] [Bug 1621539] Re: Unable to schedule "PM" events in Gnome Calendar 3.20.2

2018-03-02 Thread Alan Van Art

This is still broken as of 3.20.4. I am linked to Google Calendars and
seeing 24hr format regardless of time format setting.

** Attachment added: "screen shot"

https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1621539/+attachment/5067675/+files/Screenshot%20from%202018-03-02%2021-43-39.png

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

Title:
Unable to schedule "PM" events in Gnome Calendar 3.20.2

Status in GNOME Calendar:
Fix Released
Status in gnome-calendar package in Ubuntu:
Fix Released
Status in gnome-calendar source package in Xenial:
Fix Released

The update fixes this issue and a few more.

https://git.gnome.org/browse/gnome-calendar/tree/NEWS?h=gnome-3-20
https://git.gnome.org/browse/gnome-calendar/log/?h=gnome-3-20

Test Case
=
1. Open the Calendar app.
2. Click on a date to schedule a new event. Click Edit Details.
3. Are you able to set an event that starts and ends in the afternoon?

Open the System Settings app. Click Time & Date. Switch time from
12-hour to 24-hour (or the opposite). Repeat steps 1-3.

4. Schedule a new event that starts on one day and ends on the next.
Click the all-day box and hit Done.

The event should span both days on the calendar.

Regression Potential

Low. This is a new upstream stable bugfix release and is recommended for all
distros shipping GNOME 3.20.

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

[Desktop-packages] [Bug 1068495] Re: Firefox 16.0.1 Crash Report [@ unity_webapps_available_application_get_application_domain ]

** Changed in: firefox
   Status: Confirmed => Won't Fix

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

Title:
  Firefox 16.0.1 Crash Report [@
  unity_webapps_available_application_get_application_domain ]

Status in Mozilla Firefox:
  Won't Fix
Status in WebApps: libunity-webapps:
  Fix Released
Status in libunity-webapps package in Ubuntu:
  Fix Released
Status in libunity-webapps source package in Quantal:
  Fix Released
Status in libunity-webapps source package in Raring:
  Fix Released

Bug description:
  This has increased in frequency a lot since yesterday:

  https://crash-stats.mozilla.com/report/index/ea964fd9-9aca-
  41f8-a1b1-f9ca12121018

  Some comments:

  "Tried to use gmail integration with ubuntu 12.10 and firefox crashed"

  "opening a google calendar invite link from thunderbird"

  "I just opened facebook"

  "I click on view document in the gmail. What different: may be because
  I installed gmail plugin."

  Crashing thread:

  0 libunity-webapps-repository.so.0.0.0
unity_webapps_available_application_get_application_domain  
unity-webapps-available-application.c:65
  1 libxul.so   libxul.so@0x15cc717 
  2 libxul.so   ffi_callffi64.c:485
  3 libxul.so   js::ctypes::FunctionType::Call  CTypes.cpp:5576
  4 libxul.so   js::InvokeKerneljscntxtinlines.h:382
  5 libxul.so   js::Invoke  jsinterp.h:119
  6 libxul.so   js::IndirectProxyHandler::call  jsproxy.cpp:442
  7 libxul.so   js::DirectWrapper::call jswrapper.cpp:383
  8 libxul.so   js::CrossCompartmentWrapper::call   
jswrapper.cpp:777
  9 libxul.so   proxy_Call  jsproxy.cpp:1143
  10libxul.so   js::InvokeKerneljscntxtinlines.h:382
  11libxul.so   js::Interpret   jsinterp.cpp:2442
  12libxul.so   js::RunScript   jsinterp.cpp:301
  13libxul.so   js::InvokeKerneljsinterp.cpp:355
  14libxul.so   js::Invoke  jsinterp.h:119
  15libxul.so   js::IndirectProxyHandler::call  jsproxy.cpp:442
  16libxul.so   js::DirectWrapper::call jswrapper.cpp:383
  17libxul.so   js::CrossCompartmentWrapper::call   
jswrapper.cpp:777
  18libxul.so   proxy_Call  jsproxy.cpp:1143
  19libxul.so   js::InvokeKerneljscntxtinlines.h:382
  20libxul.so   js::Interpret   jsinterp.cpp:2442
  21libxul.so   js::RunScript   jsinterp.cpp:301
  22libxul.so   js::InvokeKerneljsinterp.cpp:355
  23libxul.so   js_fun_applyjsinterp.h:119
  24libxul.so   js::InvokeKerneljscntxtinlines.h:382
  25libxul.so   js::Interpret   jsinterp.cpp:2442
  26libxul.so   js::RunScript   jsinterp.cpp:301
  27libxul.so   js::InvokeKerneljsinterp.cpp:355
  28libxul.so   array_forEach   jsinterp.h:119
  29libxul.so   js::InvokeKerneljscntxtinlines.h:382
  30libxul.so   js::Interpret   jsinterp.cpp:2442
  31libxul.so   js::RunScript   jsinterp.cpp:301
  32libxul.so   js::InvokeKerneljsinterp.cpp:355
  33libxul.so   js_fun_applyjsinterp.h:119
  34libxul.so   js::InvokeKerneljscntxtinlines.h:382
  35libxul.so   js::Interpret   jsinterp.cpp:2442
  36libxul.so   js::RunScript   jsinterp.cpp:301
  37libxul.so   js::InvokeKerneljsinterp.cpp:355
  38libxul.so   js::Invoke  jsinterp.h:119
  39libxul.so   JS_CallFunctionValuejsapi.cpp:5604
  40libxul.so   nsXPCWrappedJSClass::CallMethod 
XPCWrappedJSClass.cpp:1436
  41libxul.so   nsXPCWrappedJS::CallMethod  XPCWrappedJS.cpp:580
  42libxul.so   PrepareAndDispatch  xptcstubs_x86_64_linux.cpp:121
  43libxul.so   libxul.so@0x10c1d02 
  44libxul.so   nsDocLoader::FireOnLocationChange   
nsDocLoader.cpp:1391
  45libxul.so   nsDocShell::CreateContentViewer 
nsDocShell.cpp:7698
  46libxul.so   nsDSURIContentListener::DoContent   
nsDSURIContentListener.cpp:119
  47libxul.so   nsDocumentOpenInfo::TryContentListener  
nsURILoader.cpp:678
  48libxul.so   nsDocumentOpenInfo::DispatchContent 
nsURILoader.cpp:375
  49libxul.so   nsDocumentOpenInfo::OnStartRequest  
nsURILoader.cpp:263
  50libxul.so   mozilla::net::nsHttpChannel::CallOnStartRequest 
nsHttpChannel.cpp:964
  51libxul.so   mozilla::net::nsHttpChannel::ContinueProcessNormal  
nsHttpChannel.cpp:1462
  52libxul.so   mozilla::net::nsHttpChannel::ProcessNormal  
nsHttpChannel.cpp:1397
  53libxul.so   mozilla::net::nsHttpChannel::ProcessResponse
nsHttpChannel.cpp:1310
  54libxul.so   mozilla::net::nsHttpChannel::OnStartRequest

[Desktop-packages] [Bug 1718931] Re: No VPN autoconnect

** Changed in: network-manager
   Status: Unknown => Confirmed

** Changed in: network-manager
   Importance: Unknown => Critical

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

Title:
  No VPN autoconnect

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

Bug description:
  When setting up VPN to auto connect with wifi (done through nm-
  connection-editor) the wifi never manages to connect. However if I
  unselect the auto connect option while it is attempting a reconnection
  then it manages to connect to both (wifi and VPN). Doing the
  connection manually also poses no issues

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 13:15:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-09 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.0.1 dev wlp6s0 proto static metric 600 
   169.254.0.0/16 dev wlp6s0 scope link metric 1000 
   192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp6s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
VM5055940   85b8f881-7ed9-477a-9c39-9afb5a40bda9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1701783] Re: xdg-mime query default inode/directory returns wrong result

** Changed in: xdg-utils (Debian)
   Status: Confirmed => Fix Released

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

Title:
  xdg-mime query default inode/directory returns wrong result

Status in Lubuntu Next:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Fix Released
Status in xdg-utils package in Debian:
  Fix Released

Bug description:
  On 17.10 alpha:

  $ xdg-mime query default inode/directory
  nautilus-folder-handler.desktop

  I assume the correct result for now would be pcmanfm.desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-next/+bug/1701783/+subscriptions

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

[Desktop-packages] [Bug 1752578] Re: Evolution 3.27/3.28 transition

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Evolution 3.27/3.28 transition

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-ews package in Ubuntu:
  New

Bug description:
  The Ubuntu Desktop Team would like to update evolution-data-server,
  evolution, and evolution-ews to 3.27.91 in preparation for evolution
  3.28 (expected release March 12).

  Evolution bumped its sonames so we'll need a transition.

  Trackers
  =
  
https://people.canonical.com/~ubuntu-archive/transitions/html/evolution-data-server.html

  https://release.debian.org/transitions/html/auto-evolution-data-
  server.html

  Successfully staged at
  https://launchpad.net/~jbicha/+archive/ubuntu/tempeds/+packages

  Justification
  =
  This transition was ready two weeks ago, but we wanted to do one major GNOME 
transition at a time. libgweather transition went smoothly. gnome-desktop3 got 
entangled with some other incomplete transitions (in particular, 
mesa/libglvnd). A Qt transition and a kdepim transition the week of 18.04 
Feature Freeze made it impossible for those transitions to clear before Feature 
Freeze.

  We could have uploaded evolution now to avoid paperwork, but it feels
  like it would be smoother to be a bit more patient and do this soon
  after Feature Freeze.

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

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

[Desktop-packages] [Bug 1753030] [NEW] package gnome-calculator 1:3.18.3-0ubuntu1 failed to install/upgrade: package gnome-calculator is not ready for configuration cannot configure (current status 'h

2018-03-02 Thread Kishor Misal

Public bug reported:

This package in fail to install.
Errors were encountered while processing:
 gnome-calculator
 mongodb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to start mongodb.service: Unit mongodb.service is not loaded properly: 
Invalid argument.
See system logs and 'systemctl status mongodb.service' for details.
invoke-rc.d: initscript mongodb, action "start" failed.
● mongodb.service - High-performance, schema-free
   Loaded: error (Reason: Invalid argument)
   Active: inactive (dead)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gnome-calculator 1:3.18.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sat Mar  3 06:40:19 2018
DuplicateSignature:
 package:gnome-calculator:1:3.18.3-0ubuntu1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package gnome-calculator (--configure):
  package gnome-calculator is not ready for configuration
ErrorMessage: package gnome-calculator is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2016-02-11 (750 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: gnome-calculator
Title: package gnome-calculator 1:3.18.3-0ubuntu1 failed to install/upgrade: 
package gnome-calculator is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package gnome-calculator 1:3.18.3-0ubuntu1 failed to install/upgrade:
  package gnome-calculator is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  This package in fail to install.
  Errors were encountered while processing:
   gnome-calculator
   mongodb-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Failed to start mongodb.service: Unit mongodb.service is not loaded properly: 
Invalid argument.
  See system logs and 'systemctl status mongodb.service' for details.
  invoke-rc.d: initscript mongodb, action "start" failed.
  ● mongodb.service - High-performance, schema-free
 Loaded: error (Reason: Invalid argument)
 Active: inactive (dead)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-calculator 1:3.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar  3 06:40:19 2018
  DuplicateSignature:
   package:gnome-calculator:1:3.18.3-0ubuntu1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package gnome-calculator (--configure):
package gnome-calculator is not ready for configuration
  ErrorMessage: package gnome-calculator is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-02-11 (750 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: gnome-calculator
  Title: package gnome-calculator 1:3.18.3-0ubuntu1 failed to install/upgrade: 
package gnome-calculator is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)

** Changed in: xorg (Debian)
   Status: Unknown => New

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  From duplicate bug 1720364 report.

  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher in mate-control-center
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ---
  Original description below:

  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

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

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

[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

2018-03-02 Thread Ra

I also have this problem.
Every time at startup the "No system tray detected" erro message shows up.
I use Ubuntu 17.10 and HPLIP 3.17.11 (last version at the time of writing).

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

Title:
  HPLIP is not compatible with modern GNOME (No system tray detected on
  this system. Unable to start, exiting.)

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install hplip-gui
  3. Launch GNOME session.
  4. Get error message window with header "HPLIP Status Service"
  and text
  "No system tray detected on this system.
  Unable to start, exiting."

  Expected results:
  hp-systray is compatible with modern GNOME

  Actual results:
  hp-systray is not compatible with modern GNOME

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 
(dbus://) went away, retrying!
  CurrentDesktop: GNOME
  Date: Sat Sep  2 14:10:19 2017
  InstallationDate: Installed on 2017-08-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. UX32A
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1493582] Re: Could not rotate PDF document with keyboard shortcuts

** Changed in: evince
   Status: Confirmed => Expired

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

Title:
  Could not rotate PDF document with keyboard shortcuts

Status in Evince:
  Expired
Status in evince package in Ubuntu:
  Triaged

Bug description:
  Evince was unable to rotate the PDF document left or right using the
  keyboard shortcuts, ctrl-left, ctrl-right.

  Rotating works using the rotate commands in the Edit menu.

  evince:
Installed: 3.16.1-0ubuntu1
Candidate: 3.16.1-0ubuntu1
Version table:
   *** 3.16.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
  100 /var/lib/dpkg/status

  Distributor ID:   Ubuntu
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  Codename: wily

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: evince 3.16.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu9
  Architecture: i386
  Date: Tue Sep  8 18:40:20 2015
  InstallationDate: Installed on 2015-05-18 (113 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150517)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1037411] Re: [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0 than it was in 0.9.7

** Changed in: mesa
   Status: Confirmed => Won't Fix

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

Title:
  [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0
  than it was in 0.9.7

Status in Compiz:
  Fix Released
Status in Mesa:
  Won't Fix
Status in compiz package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Triaged
Status in compiz source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Invalid
Status in compiz source package in Quantal:
  Fix Released
Status in mesa source package in Quantal:
  Won't Fix

Bug description:
  (This is no longer the primary performance regression bug for compiz
  0.9.8.0. Look at bug 1024304 instead)

  TEST CASE:
  1. CCSM > OpenGL >
   framebuffer_object = OFF
   vertex_buffer_object = OFF
   always_swap_buffers = OFF
  2. Run graphics benchmarks.

  Expected: Similar results to compiz 0.9.7
  Observed: Much lower results than compiz 0.9.7

  
  ORIGINAL DESCRIPTION:
  Comparing graphics performance in a two-monitor configuration, I find the 
gles2 branch is 25-40% slower than trunk.

  This would not normally be surprising, however the slowdown REMAINS
  even when I turn off the new rendering features in the gles2 branch:
  framebuffer_object, vertex_buffer_object, always_swap_buffers

  So both branches should be using the same code path. But gles2 is
  still dramatically slower than trunk using two monitors.

  The good news is that this bug only affects benchmark results and
  seemingly a little lag. The physical frame rate achieved with two
  monitors still seems to be higher using the gles2 branch, meaning it
  drops from 60Hz to 30Hz much less often than trunk does.

  NOTE 1: This regression was allowed in compiz 0.9.8.0 because it is
  generally only visible in benchmark results. Meanwhile, physical
  compiz rendering performance (as reported by the compiz Benchmark
  plugin) is higher in compiz 0.9.8.0 than previous versions, in most
  cases.

  NOTE 2: If you're just worried about fullscreen game performance, then
  you don't need to wait for this bug to be resolved. You can get
  optimal graphics performance with unredirect mode. But see bug 980663
  first.

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

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

[Desktop-packages] [Bug 1519778] Re: Single click opening of selected items in file-selector is confusing

** Changed in: gtk
   Status: Confirmed => Fix Released

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

Title:
  Single click opening of selected items in file-selector is confusing

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Since the GNOME 3.18 upgrade I keep opening files by error in the gedit 
file-selector. It took me a while to understand, what's going on why sometime 
single click acts like double click it seems to be due to this change
  https://git.gnome.org/browse/gtk%2B/commit/?id=fb0a13b7

  "file chooser: Allow activating without double-click
  Interpret a unmodified primary click on the selection like a double
  click. This makes it possible to activate a file or open a folder
  without using double-click."

  
  That has several issues:

  - the behaviour seems inconsistant, it's not easy to understand what's
  going on as an user (I first though my mouse buttons was having
  issues)

  - if you double click on a selected directory to browse it, it opens
  it with the first click then open an item directly in the directory,
  which is not what you want (seems
  https://bugzilla.gnome.org/show_bug.cgi?id=757950 was meant to address
  that but it doesn't here)

  - if you select an item, switch to another windows and click back on
  the file-selector to focus it and manage to hit the selected item then
  it's opened...

  
  I'm unsure what the issue the change was trying to address, if that's about 
touch devices maybe the behaviour shouldn't impact pointer devices?

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

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

[Desktop-packages] [Bug 1752472] Re: [ffe] Implement an Ubuntu Single Sign-on Provider

** Changed in: gnome-online-accounts
   Status: Unknown => Confirmed

** Changed in: gnome-online-accounts
   Importance: Unknown => Medium

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

Title:
  [ffe] Implement an Ubuntu Single Sign-on Provider

Status in gnome-online-accounts:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Add an Ubuntu Single Sing-On provider in gnome-online-accounts. We plan to 
use this inside:
  1) gnome-software
  2) software-properties

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1752472/+subscriptions

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

[Desktop-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

2018-03-02 Thread Nicolás Abel Carbone

Fixed for me. Thank you for your hard work!!

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

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

[Desktop-packages] [Bug 1696305] Re: High CPU usage in gnome-shell just redrawing the screen (Firefox is running)

2018-03-02 Thread pierre

This bug is affecting me as well. I just ran `ubuntu-bug gnome-shell`,
hopefully you can see my files?

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

Title:
  High CPU usage in gnome-shell just redrawing the screen (Firefox is
  running)

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

Bug description:
  Even when doing nothing at all, gnome-shell uses around 70% CPU.

  ```
  inxi -t cm
  Processes: CPU: % used - top 5 active
 1: cpu: 68.6% command: gnome-shell pid: 1399
 2: cpu: 50.4% command: Xwayland pid: 1405
 3: cpu: 19.7% command: firefox pid: 3684
 4: cpu: 2.4% command: gnome-shell pid: 1859
 5: cpu: 1.5% command: gnome-tweak-tool (started by: python) pid: 
13603
 Memory: MB / % used - Used/Total: 2350.1/11897.0MB - top 5 active
 1: mem: 1033.63MB (8.6%) command: firefox pid: 3684
 2: mem: 317.59MB (2.6%) command: gnome-shell pid: 1859
 3: mem: 267.55MB (2.2%) command: gnome-software pid: 2058
 4: mem: 111.25MB (0.9%) command: Xorg pid: 1506
 5: mem: 90.90MB (0.7%) command: nautilus-desktop pid: 2055
  ```

  It's also strange that Xwayland is active as I did choose the "normal" gnome 
session upon signin.
  ```
  echo $XDG_SESSION_TYPE
  x11
  ```

  While searching I found a recent problem with AMD GPUs, but I'm using an 
Intel GPU
  ```
  glxinfo 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: SGI
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
  GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
  GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
  GLX_SGI_make_current_read, GLX_SGI_swap_control
  client glx vendor string: Mesa Project and SGI
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) Haswell Mobile  (0xa16)
  Version: 17.1.0
  Accelerated: yes
  Video memory: 1536MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.1
  OpenGL vendor string: Intel Open Source Technology Center
  OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile 
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.0
  OpenGL core profile shading language version string: 4.50
  OpenGL core

[Desktop-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

This should be fixed now (or as soon as you get the pending updates).

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

** Changed in: mesa-demos (Ubuntu)
   Status: Confirmed => Invalid

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

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

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

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

[Desktop-packages] [Bug 1753020] [NEW] High CPU usage in gnome-shell, occurs randomly

2018-03-02 Thread pierre

Public bug reported:

I am running 17.10, and once in a while, for no apparent reason, I am
getting high CPU usage from gnome-shell. So much so that the system
becomes unusable and the only solution is to restart.

I'm using two monitors if that makes a difference, the laptop is on a
dock , one external monitor is in landscape mode, and the other one is
in portrait mode.

Not sure what else to provide, I have run the `ubuntu-bug gnome-shell`
command so hopefully there will be debug info attached.

I'm going to reboot now because the laptop is very noisy and slow.

```
$ sudo apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.26.2-0ubuntu0.1
  Candidate: 3.26.2-0ubuntu0.1
  Version table:
 *** 3.26.2-0ubuntu0.1 500
500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.26.1-0ubuntu4 500
500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
```

```
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
```

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
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
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  2 18:23:00 2018
DisplayManager: gdm3
InstallationDate: Installed on 2017-05-15 (291 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-27 (126 days ago)

** Affects: gnome-shell (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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1753020

Title:
  High CPU usage in gnome-shell, occurs randomly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am running 17.10, and once in a while, for no apparent reason, I am
  getting high CPU usage from gnome-shell. So much so that the system
  becomes unusable and the only solution is to restart.

  I'm using two monitors if that makes a difference, the laptop is on a
  dock , one external monitor is in landscape mode, and the other one is
  in portrait mode.

  Not sure what else to provide, I have run the `ubuntu-bug gnome-shell`
  command so hopefully there will be debug info attached.

  I'm going to reboot now because the laptop is very noisy and slow.

  ```
  $ sudo apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu4 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  ```

  ```
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  2 18:23:00 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-15 (291 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-27 (126 days ago)

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

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

[Desktop-packages] [Bug 1752313] Re: Desktop entries of some newly installed applications are untranslated until next reboot

2018-03-02 Thread AsciiWolf

It looks like it happens with apps that have "X-Ubuntu-Gettext-Domain"
instead of having the translated strings directly in the desktop file,
so it may be some bug in gettext or another component that Ubuntu uses.

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

Title:
  Desktop entries of some newly installed applications are untranslated
  until next reboot

Status in Ubuntu Translations:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Desktop entries of some newly installed applications are untranslated
  until next reboot on non-English Ubuntu 18.04 system. This happens
  only for some packages (for example gnome-games-app) and happens both
  when installing using GNOME Software as well as when using apt.

  Steps to Reproduce:
  1. Use non-English Ubuntu 18.04 system.
  2. Install "gnome-games-app".
  3. See the application entry in GNOME Shell Overview.
  4. Restart the computer.
  5. See the application entry in GNOME Shell Overview.

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

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

[Desktop-packages] [Bug 335662] Re: [jaunty] hplip status service cannot find system tray

2018-03-02 Thread Ra

I still have this bug in Ubuntu 17.10 and HPLIP 3.17.11. It has been 9
years since it was reported...

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

Title:
  [jaunty] hplip status service cannot find system tray

Status in HPLIP:
  Fix Committed
Status in hplip package in Ubuntu:
  Fix Released
Status in hplip package in Debian:
  Fix Released

Bug description:
  Binary package hint: hplip

  After login to ubuntu hplip status service cannot find system tray. It
  shows dialog box: "No system tray detected on this system. Unable to
  start, exiting".

  hplip version is 2.8.12-3ubuntu1 on jaunty

  I found the same bug reported in Debian
  http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg618714.html

  Regards

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

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

[Desktop-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

Nicolás, yes, we're waiting on libglvnd which is waiting on nvidia-
graphics-driver-390 to be straightened out. Even though it's late
Friday, it's being worked on now.

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in mesa-demos package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

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

[Desktop-packages] [Bug 1726516] Re: no progress bar while copying files

2018-03-02 Thread James Cobban

On the System 76 customized version of 17.10 there is a "pie" graph
symbol in the Nautilus top bar that provides access to the progress
indicator.

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

Title:
  no progress bar while copying files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  while copying files, it does not show progress or any copy dialogue at
  all. also there is no option to create new file while right clicking

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 23:08:22 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

2018-03-02 Thread Slavko Glamocanin

Adding -proposed to sources works.

Sent via the BlackBerry Hub for Android

  Original Message  
From: nicocarb...@gmail.com
Sent: March 2, 2018 10:50 PM
To: sla...@naprave.net
Reply-to: 1751...@bugs.launchpad.net
Subject: [Bug 1751414] Re: [regression] Missing Wayland login option and 
missing GL acceleration, after installing libegl1

I just got the whole mesa stack updated, including libgl1-mesa-glx (ver
18.0.0~rc4-1ubuntu3) and I still don't have gl acceleration, only llvm
pipe. Are there any other packages on hold?

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1752343).
https://bugs.launchpad.net/bugs/1751414

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in mesa-demos package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in mesa-demos package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

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

[Desktop-packages] [Bug 1752844] Re: Line drawing bug in applications using opengl 1

2018-03-02 Thread Robert Rojas

Tested 17.3.3, no success.

The artifacts appeared after the #1735594 fix, so they may be specific
to i965. My computer graphics indicate "Mobile Intel® GM45 Express
Chipset".

I found that the game titanion looks as expected when the window is
resized to 960x720 or greater. Inspecting the source I found the game
adjusts the line width at window resize while the other games keep it at
1 or 2, so I believe the driver is drawing the lines thinner than it
should.

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

Title:
  Line drawing bug in applications using opengl 1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04.3, as from the update fixing
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594, the line
  rendering in applications using Opengl 1 is incorrect.

  Blender and various games by Kenta Cho (tumiki-figthers, torus-
  trooper, parsec47, titanion) are affected.

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

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

[Desktop-packages] [Bug 1706421] Re: Wifi hotspot password is hard to read

** Changed in: gnome-control-center
   Status: Confirmed => Fix Released

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

Title:
  Wifi hotspot password is hard to read

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  When enabling a WiFi hotspot in the Network panel of g-c-c the
  password is shown in the default font.  With some fonts this makes it
  hard to read.  For example an uppercase "I" and a lowercase L in the
  Ubuntu font.

  Displaying the password in a monospace font should make this a bit
  easier to read.

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

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

[Desktop-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

2018-03-02 Thread Nicolás Abel Carbone

I just got the whole mesa stack updated, including libgl1-mesa-glx (ver
18.0.0~rc4-1ubuntu3) and I still don't have gl acceleration, only llvm
pipe. Are there any other packages on hold?

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in mesa-demos package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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()

2018-03-02 Thread Andrew Hunt

got this too. but not virtualbox installation. on older hardware.

-- 
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 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

2018-03-02 Thread Marcin Owsiany

Kirk, I think you missed my update #95, which explains the root cause.

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

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Confirmed
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

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

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

[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)

2018-03-02 Thread Norbert

>From duplicate bug 1720364 report.

Steps to reproduce:
1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
2. Set-up two keyboard layouts - English and Russian
3. Set  as keyboard layout switcher
4. Try to use shortcuts starting from :
4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click 
 to restore closed tab.
4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
4.3. Open pluma, write some text, try to navigate in it with .

Expected results:
 switches keyboard layout, shortcuts starting from  
work normally.

Actual results:
 switches keyboard layout, shortcuts starting from  
do not work.

Notes:
1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
2. This problem was discovered before on 13.10, 14.04 and other modern versions 
with GNOME desktop (Metacity and Compiz) - see bug 1245473.

** Bug watch added: Debian Bug tracker #891915
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891915

** Also affects: xorg (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891915
   Importance: Unknown
   Status: Unknown

** Tags removed: zesty

** Description changed:

+ From duplicate bug 1720364 report.
+ 
+ Steps to reproduce:
+ 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
+ 2. Set-up two keyboard layouts - English and Russian
+ 3. Set  as keyboard layout switcher
+ 4. Try to use shortcuts starting from :
+ 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
+ 4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
+ 4.3. Open pluma, write some text, try to navigate in it with 
.
+ 
+ Expected results:
+  switches keyboard layout, shortcuts starting from 
 work normally.
+ 
+ Actual results:
+  switches keyboard layout, shortcuts starting from 
 do not work.
+ 
+ Notes:
+ 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
+ 2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.
+ 
+ 
+ ---
+ Original description below:
+ 
  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.
  
  This is a bug about shortcuts mapped to combinations which include each
  other.
  
  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)
  
  The expected behavior is to fire shortcuts on the release (not on press)
  of the special keys (ctrl,shift,alt, etc) which is also how Windows
  behave. This is a serious problem for bilingual layouts, typically using
  Alt+Shift or Ctrl+Shift for keyboard layout change.
  
  Apparently, the bug has reappeared after the patch that used to fix the
  problem (208_switch_on_release.diff) has been removed from X.Org 1.19
  packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

** Description changed:

  From duplicate bug 1720364 report.
  
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
- 3. Set  as keyboard layout switcher
+ 3. Set  as keyboard layout switcher in mate-control-center
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma,

[Desktop-packages] [Bug 1752966] Re: Merge 3.4.2-2 from Debian

2018-03-02 Thread Hans Joachim Desserud

** Tags added: needs-debian-merge upgrade-software-version

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

Title:
  Merge 3.4.2-2 from Debian

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Please merge 3.4.2-2 from Debian. I cannot work on this merge myself.

  It has this cherry-pick (fix_mediakeys_api.patch: Fix use of mediakeys
  D-Bus API)

  More info upstream:
  mmkeys: media-player-keys: Fix usage to match API documentation
  See https://bugzilla.gnome.org/show_bug.cgi?id=781326
  https://bugzilla.gnome.org/show_bug.cgi?id=781664
  ---

  rhythmbox (3.4.2-2) unstable; urgency=medium

[ Simon McVittie ]
* gir1.2-rb-3.0 Provides gir1.2-mpid-3.0, since it also contains
  MPID-3.0.typelib

[ Laurent Bigonville ]
* debian/patches/fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API
* debian/control.in: Bump Standards-Version to 4.1.3 (no further changes)
* debian/source_rhythmbox.py: Install apport hook (thanks to Ubuntu)

   -- Laurent Bigonville   Thu, 08 Feb 2018 14:23:43
  +0100

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

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

[Desktop-packages] [Bug 1720364] Re: Unable to use <Ctrl+Shift+key> shortcuts with <Ctrl+Shift> keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

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

** This bug has been marked a duplicate of bug 1683383
   Keyboard layout change on hotkeys press instead of release and do not work 
well with shortcuts (reopen)

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

Status in MATE Desktop:
  New
Status in ubuntu-mate:
  New
Status in X.Org X server:
  Confirmed
Status in marco package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-hwe-16.04 package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: marco 1.18.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Sep 29 16:18:02 2017
  InstallationDate: Installed on 2017-08-26 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: marco
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752971] [NEW] lightdm don't started

2018-03-02 Thread Alex_ander

Public bug reported:

can not download system
does not start lgtdm
I have to start with the startx command from the console

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar  2 21:57:29 2018
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  lightdm don't  started

Status in lightdm package in Ubuntu:
  New

Bug description:
  can not download system
  does not start lgtdm
  I have to start with the startx command from the console

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar  2 21:57:29 2018
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

This bug was fixed in the package mesa - 18.0.0~rc4-1ubuntu3

---
mesa (18.0.0~rc4-1ubuntu3) bionic; urgency=medium

  * dont-enable-10bpc-by-default.diff: Replace the drirc hack, just flip
the default to not enable 10bpc configs by default for gallium drivers.
(LP: #1752123)

 -- Timo Aaltonen   Wed, 28 Feb 2018 19:34:58 +0200

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

-- 
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 cogl package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

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/cogl/+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 1747744] Re: [regression] Video playback in totem is corrupted in X11

This bug was fixed in the package mesa - 18.0.0~rc4-1ubuntu3

---
mesa (18.0.0~rc4-1ubuntu3) bionic; urgency=medium

  * dont-enable-10bpc-by-default.diff: Replace the drirc hack, just flip
the default to not enable 10bpc configs by default for gallium drivers.
(LP: #1752123)

 -- Timo Aaltonen   Wed, 28 Feb 2018 19:34:58 +0200

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

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND (1):

  Install these two together:
  
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libgl1-mesa-glx_17.2.4-0ubuntu2_amd64.deb
  
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libglapi-mesa_17.2.4-0ubuntu2_amd64.deb

  WORKAROUND (2):

  sudo apt remove gstreamer1.0-vaapi

  WORKAROUND (3):

  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---

  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Simple:   VAEntrypointEncSlice
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointEncSlice
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileH264MultiviewHigh  :   VAEntrypointVLD
    VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
    VAProfileH264StereoHigh :   VAEntrypointVLD
    VAProfileH264StereoHigh :   VAEntrypointEncSlice
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc
    VAProfileJPEGBaseline   :   VAEntrypointVLD

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752803] Re: [ffe] use locate informations in the search provider

This bug was fixed in the package nautilus - 1:3.26.2-0ubuntu3.1

---
nautilus (1:3.26.2-0ubuntu3.1) bionic; urgency=medium

  * debian/patches/search-engine-add-a-recent-search-engine-listing-Gtk.patch:
- use the correct patch info so there no line missing in the source

 -- Sebastien Bacher   Fri, 02 Mar 2018 18:31:10
+0100

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

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

Title:
  [ffe] use locate informations in the search provider

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  That's part of fixing bug #1732780 and making files listed in the
  desktop overview for the LTS (which is currently not working and a
  regression over Unity or upstream GNOME).

  The proposed change uses "locate" as a backend (same as unity was doing), the 
corresponding patch is available there
  
https://gitlab.gnome.org/3v1n0/nautilus/blob/ubuntu-3-26/debian/patches/0019-search-engine-add-locate-based-search-engine.patch

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

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

[Desktop-packages] [Bug 1752966] [NEW] Merge 3.4.2-2 from Debian

2018-03-02 Thread Amr Ibrahim

Public bug reported:

Please merge 3.4.2-2 from Debian. I cannot work on this merge myself.

It has this cherry-pick (fix_mediakeys_api.patch: Fix use of mediakeys
D-Bus API)

More info upstream:
mmkeys: media-player-keys: Fix usage to match API documentation
See https://bugzilla.gnome.org/show_bug.cgi?id=781326
https://bugzilla.gnome.org/show_bug.cgi?id=781664
---

rhythmbox (3.4.2-2) unstable; urgency=medium

  [ Simon McVittie ]
  * gir1.2-rb-3.0 Provides gir1.2-mpid-3.0, since it also contains
MPID-3.0.typelib

  [ Laurent Bigonville ]
  * debian/patches/fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API
  * debian/control.in: Bump Standards-Version to 4.1.3 (no further changes)
  * debian/source_rhythmbox.py: Install apport hook (thanks to Ubuntu)

 -- Laurent Bigonville   Thu, 08 Feb 2018 14:23:43
+0100

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

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

Title:
  Merge 3.4.2-2 from Debian

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Please merge 3.4.2-2 from Debian. I cannot work on this merge myself.

  It has this cherry-pick (fix_mediakeys_api.patch: Fix use of mediakeys
  D-Bus API)

  More info upstream:
  mmkeys: media-player-keys: Fix usage to match API documentation
  See https://bugzilla.gnome.org/show_bug.cgi?id=781326
  https://bugzilla.gnome.org/show_bug.cgi?id=781664
  ---

  rhythmbox (3.4.2-2) unstable; urgency=medium

[ Simon McVittie ]
* gir1.2-rb-3.0 Provides gir1.2-mpid-3.0, since it also contains
  MPID-3.0.typelib

[ Laurent Bigonville ]
* debian/patches/fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API
* debian/control.in: Bump Standards-Version to 4.1.3 (no further changes)
* debian/source_rhythmbox.py: Install apport hook (thanks to Ubuntu)

   -- Laurent Bigonville   Thu, 08 Feb 2018 14:23:43
  +0100

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2018-03-02 Thread Chituc Georgian

Maybe because it do not crash on skia anymore , this crash in
RootingAPI.h will be easier to fix ...

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2018-03-02 Thread Chituc Georgian

I installed debug symbols here are more crash about the crash , again
like i said is not in skia anymore :


Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
0xf4c3dcb4 in JS::MutableHandle::set (v=..., this=) at 
/root/firefox-58.0.2+build1/obj-arm-linux-gnueabihf/dist/include/js/RootingAPI.h:580
580 
/root/firefox-58.0.2+build1/obj-arm-linux-gnueabihf/dist/include/js/RootingAPI.h:
 Permission denied.
(gdb)

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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()

2018-03-02 Thread Thomas Beyer

got this too. but no virtualbox installation

-- 
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 1752950] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

2018-03-02 Thread Manfred Hampl

(correction: Virtualbox version 5.2.8)

** Description changed:

- Ubuntu 18.04 in virtualbox 5.0.8 on Windows 10
+ 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)!
+  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
+  ?? () 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

-- 
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 1720364] Re: Unable to use <Ctrl+Shift+key> shortcuts with <Ctrl+Shift> keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

** Changed in: xorg (Debian)
   Status: Unknown => New

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

Status in MATE Desktop:
  New
Status in ubuntu-mate:
  New
Status in X.Org X server:
  Confirmed
Status in marco package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-hwe-16.04 package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: marco 1.18.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Sep 29 16:18:02 2017
  InstallationDate: Installed on 2017-08-26 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: marco
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

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

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

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

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

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

  This problem is reproducible.

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

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

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

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

[Desktop-packages] [Bug 1728383] Re: Unable to create a DBus proxy for GnomeScreensaver

2018-03-02 Thread Reverend Fuzzy

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

I also got this...

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

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

Title:
  Unable to create a DBus proxy for GnomeScreensaver

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10, error on boot:
  gnome-session-b: 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

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

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

[Desktop-packages] [Bug 1751070] Re: FFe: mutter/gnome-shell 3.27/3.28

Freeze exception approved by Laney at LP: #1752928

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

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

Title:
  FFe: mutter/gnome-shell 3.27/3.28

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Feature Freeze Exception
  
  The Ubuntu Desktop Team would like to update mutter and gnome-shell to 
3.27.92.

  mutter's soname was bumped so we need to update budgie-desktop too.
  This has been done and tested successfully in the GNOME3 Staging PPA.

  https://gitlab.gnome.org/GNOME/mutter/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/NEWS

  Feature Freeze Exception Justification
  -
  GNOME was late in doing its mutter and gnome-shell release this cycle.

  We could have rushed those two in to 18.04 but there are a few
  regressions that we wanted to fix first, and a key developer had some
  time off in late February.

  Known Issues
  
  - The 70_allow_sound_above_100.patch needs to be rebased (probably by 
didrocks)
  - The "keycaps" (labels for Shift, Enter, etc.) in the new screen keyboard 
show in the GNOME session but not the Ubuntu session
  - ubuntu-session-mods/ubuntu.css probably needs to be rebased (and that will 
probably fix the keycaps issue)

  Relation to Other Transitions
  -
  This will unlock the gnome-settings-daemon transition

  budgie-desktop is part of the ongoing gnome-desktop3 transition.
  gnome-shell will be part of the evolution-data-server transition.

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2018-03-02 Thread Chituc Georgian

It successfully build a deb .I build all with gcc except gfx/skia build with 
clang .
There is again a crash but It looks now is not in _sk_xor__vfp4 the asm code 
where it crash is different from the asm code of _sk_xor__vfp4  .

firefox -g
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/firefox/firefox...(no debugging symbols 
found)...done.
(gdb) run
Starting program: /usr/lib/firefox/firefox 
Cannot parse expression `.L1185 4@r4'.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0xf2522450 (LWP 2431)]
[New Thread 0xf1d22450 (LWP 2432)]
[Thread 0xf1d22450 (LWP 2432) exited]
[New Thread 0xf1d22450 (LWP 2433)]
[New Thread 0xed17b450 (LWP 2434)]
[New Thread 0xec97b450 (LWP 2435)]
[New Thread 0xec17b450 (LWP 2436)]
[New Thread 0xf12ff450 (LWP 2437)]
[New Thread 0xf10ff450 (LWP 2438)]
[New Thread 0xeb97b450 (LWP 2439)]
[New Thread 0xeb77b450 (LWP 2440)]
[New Thread 0xeb57b450 (LWP 2441)]
[New Thread 0xeb37b450 (LWP 2442)]
[New Thread 0xeb17b450 (LWP 2443)]
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
0xf4c3dcb4 in ?? () from /usr/lib/firefox/libxul.so
(gdb) disas /r 0xf4c3dca0,0xf4c3dcd0
Dump of assembler code from 0xf4c3dca0 to 0xf4c3dcd0:
   0xf4c3dca0:  9b 68   ldr r3, [r3, #8]
   0xf4c3dca2:  05 eb 83 03 add.w   r3, r5, r3, lsl #2
   0xf4c3dca6:  16 46   mov r6, r2
   0xf4c3dca8:  0f 46   mov r7, r1
   0xf4c3dcaa:  98 44   add r8, r3
   0xf4c3dcac:  20 99   ldr r1, [sp, #128]  ; 0x80
   0xf4c3dcae:  d9 e9 00 23 ldrdr2, r3, [r9]
   0xf4c3dcb2:  82 46   mov r10, r0
=> 0xf4c3dcb4:  c1 e9 00 23 strdr2, r3, [r1]
   0xf4c3dcb8:  d9 f8 04 30 ldr.w   r3, [r9, #4]
   0xf4c3dcbc:  7b 33   addsr3, #123; 0x7b
   0xf4c3dcbe:  00 f0 4b 81 beq.w   0xf4c3df58
   0xf4c3dcc2:  b1 69   ldr r1, [r6, #24]
   0xf4c3dcc4:  c1 f3 56 25 ubfxr5, r1, #9, #23
   0xf4c3dcc8:  21 f4 ff 71 bic.w   r1, r1, #510; 0x1fe
   0xf4c3dccc:  21 f0 01 01 bic.w   r1, r1, #1


I dnt know where this asm code belongs too . I dnt know in what function
it crash , but is not in sk jumper generated .

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant

[Desktop-packages] [Bug 864951] Re: gwibber crashed with SIGSEGV in g_sequence_get()

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

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

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

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

Title:
  gwibber crashed with SIGSEGV in g_sequence_get()

Status in gwibber package in Ubuntu:
  Confirmed

Bug description:
  The crash happened when trying to check new posts after resuming from
  suspension.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gwibber 3.2.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Oct  2 20:43:33 2011
  ExecutablePath: /usr/bin/gwibber
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  ProcCmdline: gwibber -s messages
  SegvAnalysis:
   Segfault happened at: 0x7fd1afcd48db:mov0x18(%rdx),%rcx
   PC (0x7fd1afcd48db) ok
   source "0x18(%rdx)" (0x0058) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gwibber
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_sequence_get () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libdee-1.0.so.1
   ?? () from /usr/lib/libgwibber.so.2
   ?? () from /usr/lib/libgwibber.so.2
  Title: gwibber crashed with SIGSEGV in g_sequence_get()
  UpgradeStatus: Upgraded to oneiric on 2011-10-01 (1 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1752901] Re: If libegl1 is installed, modeset fails and rendering falls back to CPU (llvmpipe)

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

yes, sorry about that, it'll get fixed by tomorrow when the rest of the
packages migrate to bionic..

** This bug has been marked a duplicate of bug 1751414
   [regression] Missing Wayland login option and missing GL acceleration, after 
installing libegl1

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

Title:
  If libegl1 is installed, modeset fails and rendering falls back to CPU
  (llvmpipe)

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  When I updated my system today (
  https://paste.ubuntu.com/p/S7csQfNHT4/ ), logged off and logged in,
  the GPU rendering stopped working. Now using glxinfo it outputs:
  https://paste.ubuntu.com/p/njnbMHf7Bk/

  Before libegl1 was required I hadn't it installed, but as now it is
  unavoidable, it became a big problem.

  The only way to make GPU rendering work on this machine is to create a
  xorg.conf file at /etc/X11 and use the driver intel, but it is said
  this is not recommended to use it with hardware newer than 2007.

  Specifications:
  Intel Core i3-6100U
  Intel HD Graphics 520
  8 GB of RAM

  lspci output: https://paste.ubuntu.com/p/Djz3WxstQ5/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl1 0.2.999+git20170802-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar  2 12:01:51 2018
  Dependencies:
   gcc-8-base 8-20180218-1ubuntu1
   libc6 2.26-0ubuntu2.1
   libgcc1 1:8-20180218-1ubuntu1
   libglvnd0 0.2.999+git20170802-2
  InstallationDate: Installed on 2017-06-13 (261 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libglvnd
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (133 days ago)

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

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

[Desktop-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2018-03-02 Thread Erikas

Chris (#38) - try to put your computer to sleep and wake up while
listening to something. Issue still persists, but once you plug out and
plug in your headset - it returns back to normal volume as expected.

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Desktop-packages] [Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

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

** This bug has been marked a duplicate of bug 1751414
   [regression] Missing Wayland login option and missing GL acceleration, after 
installing libegl1

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

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

[Desktop-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

it's better to enable -proposed and install libgl1-mesa-glx after apt
update (and not do full dist-upgrade to avoid unrelated updates)... not
sure if just that is enough, might need some other packages too

the packages should migrate "soon", now that all the blockers have been
sorted out

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in mesa-demos package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

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

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

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

** This bug has been marked a duplicate of bug 1751414
   [regression] Missing Wayland login option and missing GL acceleration, after 
installing libegl1

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  New

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

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

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

  This problem is reproducible.

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

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

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

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

[Desktop-packages] [Bug 1554652] Re: nautilus-share broken with libpam-smbpass removed

2018-03-02 Thread Sam Webster

This is still an issue in yesterday's build of 18.04

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

Title:
  nautilus-share broken with libpam-smbpass removed

Status in nautilus-share package in Ubuntu:
  New

Bug description:
  Package libpam-smbpass is removed from 16.04 archives because of bug
  causing segfault.

  This makes nautilus-share very confusing since you won't be able to access 
the shares if they are set with authentication.
  Users might be stuck thinking file sharing simply doesn't work because of 
this.
  Perhaps nautilus-share should have a dialog explaining that a samba password 
has to be set or have it only with guest access for shares unless the issue 
with libpam-smbpass is fixed and back in archive.

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

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

[Desktop-packages] [Bug 1752908] Re: gnome-session is broken without 3d acceleration

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

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

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

Title:
  gnome-session is broken without 3d acceleration

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Mar  2 16:20:13 Jupiter gnome-session[1668]: X Error of failed request:  
BadWindow (invalid Window parameter)
  Mar  2 16:20:13 Jupiter gnome-session[1668]:   Major opcode of failed 
request:  155 (NV-GLX)
  Mar  2 16:20:13 Jupiter gnome-session[1668]:   Minor opcode of failed 
request:  4 ()
  Mar  2 16:20:13 Jupiter gnome-session[1668]:   Resource id in failed request: 
 0x63
  Mar  2 16:20:13 Jupiter gnome-session[1668]:   Serial number of failed 
request:  37
  Mar  2 16:20:13 Jupiter gnome-session[1668]:   Current serial number in 
output stream:  37
  Mar  2 16:20:13 Jupiter gnome-session[1668]: gnome-session-check-accelerated: 
GL Helper exited with code 256

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu9
  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
  Date: Fri Mar  2 16:35:45 2018
  InstallationDate: Installed on 2018-01-01 (59 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-01 (59 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: gnome-session 3.26.1-0ubuntu9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lp lpadmin netdev plugdev pulse 
pulse-access sambashare scanner sudo video
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1726143] Re: Automatic installation of samba fails with "could not find package libpam-smbpass"

2018-03-02 Thread Sam Webster

This is still an issue in yesterday's build of 18.04

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

Title:
  Automatic installation of samba fails with "could not find package
  libpam-smbpass"

Status in nautilus-share package in Ubuntu:
  Confirmed

Bug description:
  I actually have no idea if this is really a Nautilus issue but didn't
  know where else to file it.

  I have a fresh install of ubuntu 17.10.  I start nautilus (using
  File).  I right-click on a folder and select "Local Network Share".
  When I select "Share this folder" it says the sharing service is not
  installed, so I select "Install Service" and it offers to install
  samba for me.

  I click "install" and it proceeds, then throws up an error dialog:

  Could not find package 'libpam-smbpass'

  I can see that Samba packages are already installed at this point.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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: GNOME
  Date: Sun Oct 22 15:43:28 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742946] Re: "gio monitor" does not work

** Changed in: glib
   Status: Unknown => Fix Released

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

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

Title:
  "gio monitor" does not work

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  # ls -l /etc/adduser.conf
  -rw-r--r-- 1 root root 2981 Mar 11  2012 /etc/adduser.conf
  # gio monitor file:///etc/adduser.conf
  gio: No locations given

  Usage:
gio monitor [OPTION…] [LOCATION...]

  Monitor files or directories for changes.

  Options:
-d, --dir=LOCATIONMonitor a directory (default: depends on type)
-f, --file=LOCATION   Monitor a file (default: depends on type)
-D, --direct=LOCATION Monitor a file directly (notices changes made via 
hardlinks)
-s, --silent=LOCATION Monitors a file directly, but doesn’t report 
changes
-n, --no-movesReport moves and renames as simple 
deleted/created events
-m, --mounts  Watch for mount events

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 14:29:42 2018
  InstallationDate: Installed on 2012-03-12 (2131 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120311)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

2018-03-02 Thread exploder91

I tried removing the package from recovery mode as root, it would not
remove libegl1.

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in mesa-demos package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  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
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/libglvnd/+bug/1751414/+subscriptions

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

[Desktop-packages] [Bug 1752901] Re: If libegl1 is installed, modeset fails and rendering falls back to CPU (llvmpipe)

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

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

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

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

Title:
  If libegl1 is installed, modeset fails and rendering falls back to CPU
  (llvmpipe)

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  When I updated my system today (
  https://paste.ubuntu.com/p/S7csQfNHT4/ ), logged off and logged in,
  the GPU rendering stopped working. Now using glxinfo it outputs:
  https://paste.ubuntu.com/p/njnbMHf7Bk/

  Before libegl1 was required I hadn't it installed, but as now it is
  unavoidable, it became a big problem.

  The only way to make GPU rendering work on this machine is to create a
  xorg.conf file at /etc/X11 and use the driver intel, but it is said
  this is not recommended to use it with hardware newer than 2007.

  Specifications:
  Intel Core i3-6100U
  Intel HD Graphics 520
  8 GB of RAM

  lspci output: https://paste.ubuntu.com/p/Djz3WxstQ5/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl1 0.2.999+git20170802-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar  2 12:01:51 2018
  Dependencies:
   gcc-8-base 8-20180218-1ubuntu1
   libc6 2.26-0ubuntu2.1
   libgcc1 1:8-20180218-1ubuntu1
   libglvnd0 0.2.999+git20170802-2
  InstallationDate: Installed on 2017-06-13 (261 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libglvnd
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (133 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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()

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

** Changed in: deja-dup (Ubuntu)
   Status: New => Confirmed

-- 
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.0.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 1752950] [NEW] deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

2018-03-02 Thread Manfred Hampl

Public bug reported:

Ubuntu 18.04 in virtualbox 5.0.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

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages

** Information type changed from Private to Public

-- 
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.0.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 1726143] Re: Automatic installation of samba fails with "could not find package libpam-smbpass"

2018-03-02 Thread Sam Webster

This is still an issue in yesterday's build of 18.04

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

Title:
  Automatic installation of samba fails with "could not find package
  libpam-smbpass"

Status in nautilus-share package in Ubuntu:
  Confirmed

Bug description:
  I actually have no idea if this is really a Nautilus issue but didn't
  know where else to file it.

  I have a fresh install of ubuntu 17.10.  I start nautilus (using
  File).  I right-click on a folder and select "Local Network Share".
  When I select "Share this folder" it says the sharing service is not
  installed, so I select "Install Service" and it offers to install
  samba for me.

  I click "install" and it proceeds, then throws up an error dialog:

  Could not find package 'libpam-smbpass'

  I can see that Samba packages are already installed at this point.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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: GNOME
  Date: Sun Oct 22 15:43:28 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751578] Re: Totem no longer plays MP4s, despite correct plugins installed

2018-03-02 Thread Tom Brossman

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

** Description changed:

  Recently I tested several video players, and after uninstalling them I
  can no longer view MP4 videos. I do have the necessary gstreamer plugins
  installed, however Totem incorrectly reports "Required plugin could not
  be found".
  
- I've posted a related question here:
- https://askubuntu.com/questions/1008762/how-can-i-restore-totems-
- ability-to-play-mp4-videos
- 
  I'm on Ubuntu 16.04.4 LTS running Totem 3.18.1-1ubuntu4
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-07-21 (219 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  _MarkForUpload: True
+ 
+ (Edit: I've deleted the Ask Ubuntu link and question as this is off-
+ topic there)

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

Title:
  Totem no longer plays MP4s, despite correct plugins installed

Status in Totem:
  Unknown
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Recently I tested several video players, and after uninstalling them I
  can no longer view MP4 videos. I do have the necessary gstreamer
  plugins installed, however Totem incorrectly reports "Required plugin
  could not be found".

  I'm on Ubuntu 16.04.4 LTS running Totem 3.18.1-1ubuntu4
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-07-21 (219 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

  (Edit: I've deleted the Ask Ubuntu link and question as this is off-
  topic there)

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

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

[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop

2018-03-02 Thread Michael Thayer

Even though 3.28 is due out after the Bionic feature freeze?  What about
X.Org 1.20, which is due out a few days later?

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

Title:
  GNOME Shell disabling wrong screen when docking laptop

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  I often switch between working with a docking station, closed laptop
  and an external monitor, and an open laptop without docking station or
  monitor.  I noticed since updating to 17.10 that GNOME Shell would not
  switch correctly from the setup where the laptop was being used open
  without a docking station to the other.  When I opened the laptop in
  the docking station the external monitor would come on, and when I
  closed the laptop it went off again.  I manually switched the primary
  screen to be the external one and that solved it for now, so I assume
  that GNOME Shell was disabling the external screen instead of the
  internal one (it is a bit hard to see, and I have not yet tried ssh-
  ing in).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 09:06:34 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-05-31 (497 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago)

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

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

[Desktop-packages] [Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

2018-03-02 Thread Cliff Carson

The prior attempt to install was with a USB.  Create a bootable DVD with
the same daily build level and the install process failed at the same
location, right after the Who are You? screen.  Couldn't get to the
syslog because the install process was no longer responding so could not
verify the G_UDEV_IS_DEVICE failure message.

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

Title:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion
  'G_UDEV_IS_DEVICE (device)' failed

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have no idea about the package to blame: gvfs/udev/kernel ?

  This is now logged:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE 
(device)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.35.91-1ubuntu1
  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
  CurrentDesktop: GNOME
  Date: Tue Feb 27 14:21:10 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

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

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

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

Title:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion
  'G_UDEV_IS_DEVICE (device)' failed

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have no idea about the package to blame: gvfs/udev/kernel ?

  This is now logged:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE 
(device)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.35.91-1ubuntu1
  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
  CurrentDesktop: GNOME
  Date: Tue Feb 27 14:21:10 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752816] 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/1752816/+attachment/5066767/+files/CoreDump.gz

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

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

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

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

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

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

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

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Crashed soon after login.

  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: GNOME
  Date: Fri Mar  2 11:08:38 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-04-02 (333 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/usr/bin/zsh
  SegvAnalysis:
   Segfault happened at: 0x7fb9755c8588:movl   $0x0,(%rax)
   PC (0x7fb9755c8588) 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=0x7fb97583002c, 
init_routine=0x7fb96c6b2490 <__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-05 (24 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1752934] [NEW] Tabs not rendering in Thunderbird Preferences

2018-03-02 Thread pumpkinbeer

Public bug reported:

Possibly similar to #345834.
Under Edit->Preferences->Display The tabs for "Formatting, Tags, Advanced" do 
not look like tabs, just words.  Making it very difficult to realize they were 
tabs to be clicked on.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: thunderbird 1:52.6.0+build1-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  dhuffman   1342 F pulseaudio
 /dev/snd/controlC1:  dhuffman   1342 F pulseaudio
 /dev/snd/pcmC0D0p:   dhuffman   1342 F...m pulseaudio
 /dev/snd/controlC0:  dhuffman   1342 F pulseaudio
BuildID: 20180124151331
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  2 12:00:42 2018
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-03-01 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
IpRoute:
 default via 129.22.192.1 dev eno1 proto static metric 100 
 129.22.192.0/22 dev eno1 proto kernel scope link src 129.22.194.43 metric 100 
 169.254.0.0/16 dev eno1 scope link metric 1000
IwConfig:
 eno1  no wireless extensions.
 
 lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=52.6.0/20180124151331 (In use)
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1304
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1304:bd07/11/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


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

** Attachment added: "Screenshot from 2018-03-02 11-40-54.png"
   
https://bugs.launchpad.net/bugs/1752934/+attachment/5067244/+files/Screenshot%20from%202018-03-02%2011-40-54.png

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

Title:
  Tabs not rendering in Thunderbird Preferences

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Possibly similar to #345834.
  Under Edit->Preferences->Display The tabs for "Formatting, Tags, Advanced" do 
not look like tabs, just words.  Making it very difficult to realize they were 
tabs to be clicked on.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: thunderbird 1:52.6.0+build1-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dhuffman   1342 F pulseaudio
   /dev/snd/controlC1:  dhuffman   1342 F pulseaudio
   /dev/snd/pcmC0D0p:   dhuffman   1342 F...m pulseaudio
   /dev/snd/controlC0:  dhuffman   1342 F pulseaudio
  BuildID: 20180124151331
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  2 12:00:42 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IpRoute:
   default via 129.22.192.1 dev eno1 proto static metric 100 
   129.22.192.0/22 dev eno1 proto kernel scope link src 129.22.194.43 metric 
100 
   169.254.0.0/16 dev eno1 scope link metric 1000
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing

[Desktop-packages] [Bug 1752815] 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/1752815/+attachment/5066758/+files/CoreDump.gz

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Error just after login, system, seems to behave normal.

  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: Thu Mar  1 13:00:02 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  JournalErrors:
   -- Logs begin at Wed 2018-02-28 09:35:16 CET, end at Fri 2018-03-02 09:55:08 
CET. --
   mrt 02 09:46:25 hostname spice-vdagent[961]: Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0
   mrt 02 09:53:02 hostname spice-vdagent[2185]: Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0
   mrt 02 09:53:26 hostname pulseaudio[2086]: [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: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.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/1752815/+subscriptions

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

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

2018-03-02 Thread Hairong Zhu

Public bug reported:

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

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

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

This problem is reproducible.

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

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

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


** Tags: amd64 apport-bug bionic reproducible single-occurrence ubuntu

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  New

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

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

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

  This problem is reproducible.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04

[Desktop-packages] [Bug 1752793] 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 perl-base
no debug symbol package found for perl-base
package libgnome-desktop-3-12 does not exist, ignoring


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/1752793/+attachment/507/+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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1752793

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  when start ubuntu this bug happens

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar  2 10:26:35 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-03-05 (361 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   -- Logs begin at Sun 2018-02-11 17:38:20 IST, end at Fri 2018-03-02 11:05:51 
IST. --
   Mar 02 10:47:07 hostname systemd[1]: Failed to start AppArmor initialization.
   Mar 02 10:47:14 hostname NetworkManager[784]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   Mar 02 10:47:16 hostname gnome-session-binary[1074]: 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 10:48:10 hostname pulseaudio[1674]: [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: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2018-02-11 (18 days ago)
  UserGroups:

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  when start ubuntu this bug happens

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar  2 10:26:35 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-03-05 (361 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   -- Logs begin at Sun 2018-02-11 17:38:20 IST, end at Fri 2018-03-02 11:05:51 
IST. --
   Mar 02 10:47:07 hostname systemd[1]: Failed to start AppArmor initialization.
   Mar 02 10:47:14 hostname NetworkManager[784]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   Mar 02 10:47:16 hostname gnome-session-binary[1074]: 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 10:48:10 hostname pulseaudio[1674]: [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: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2018-02-11 (18 days ago)
  UserGroups:

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  when start ubuntu this bug happens

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar  2 10:26:35 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-03-05 (361 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   -- Logs begin at Sun 2018-02-11 17:38:20 IST, end at Fri 2018-03-02 11:05:51 
IST. --
   Mar 02 10:47:07 hostname systemd[1]: Failed to start AppArmor initialization.
   Mar 02 10:47:14 hostname NetworkManager[784]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   Mar 02 10:47:16 hostname gnome-session-binary[1074]: 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 10:48:10 hostname pulseaudio[1674]: [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: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2018-02-11 (18 days ago)
  UserGroups:

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  when start ubuntu this bug happens

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar  2 10:26:35 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-03-05 (361 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   -- Logs begin at Sun 2018-02-11 17:38:20 IST, end at Fri 2018-03-02 11:05:51 
IST. --
   Mar 02 10:47:07 hostname systemd[1]: Failed to start AppArmor initialization.
   Mar 02 10:47:14 hostname NetworkManager[784]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   Mar 02 10:47:16 hostname gnome-session-binary[1074]: 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 10:48:10 hostname pulseaudio[1674]: [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: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2018-02-11 (18 days ago)
  UserGroups:

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

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

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

StacktraceTop:
 g_log_structured (log_domain=0x7f34790a499c "", log_level=32564) at 
../../../../glib/gmessages.c:1797
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  when start ubuntu this bug happens

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar  2 10:26:35 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-03-05 (361 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   -- Logs begin at Sun 2018-02-11 17:38:20 IST, end at Fri 2018-03-02 11:05:51 
IST. --
   Mar 02 10:47:07 hostname systemd[1]: Failed to start AppArmor initialization.
   Mar 02 10:47:14 hostname NetworkManager[784]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   Mar 02 10:47:16 hostname gnome-session-binary[1074]: 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 10:48:10 hostname pulseaudio[1674]: [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: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2018-02-11 (18 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1752709] Re: Left mouse button gets stuck down (in software), usually after suspend/resume

2018-03-02 Thread gpothier

I can reproduce the issue by unplugging and usb stick! When I plug it in
nothing special happens, but when I unplug it the bug appears
immediately. The same workaroud (switching VTs) resolves it temporarily.

It does not happen 100% of the time though. It did happen 4 times in a
row a few minutes ago. I don't see anything unusual in the log. Here is
what I got when unplugging, the first time it triggered the bug:

Mar  2 13:48:02 tadzim3 kernel: [48565.861661] usb 2-2: USB disconnect, device 
number 15
Mar  2 13:48:02 tadzim3 upowerd[2322]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
Mar  2 13:48:02 tadzim3 upowerd[2322]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb2/2-2
Mar  2 13:48:02 tadzim3 dbus-daemon[1112]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1503' (uid=1000 
pid=3197 comm="/usr/bin/gnome-shell " label="unconfined")
Mar  2 13:48:02 tadzim3 systemd[1]: Starting Hostname Service...
Mar  2 13:48:02 tadzim3 dbus-daemon[1112]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Mar  2 13:48:02 tadzim3 systemd[1]: Started Hostname Service.
Mar  2 13:48:03 tadzim3 org.gnome.SettingsDaemon.Power.desktop[3308]: Error 
executing command as another user: Not authorized
Mar  2 13:48:03 tadzim3 org.gnome.SettingsDaemon.Power.desktop[3308]: This 
incident has been reported.
Mar  2 13:48:11 tadzim3 /usr/lib/gdm3/gdm-x-session[3036]: (**) Option "fd" "24"
Mar  2 13:48:11 tadzim3 /usr/lib/gdm3/gdm-x-session[3036]: (II) event2  - Power 
Button: device removed

What happens beginning at 13:48:11, 9 seconds after the USB disconnect,
seems to be the VT switch, when I worked around the bug.

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

Title:
  Left mouse button gets stuck down (in software), usually after
  suspend/resume

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libinput package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Sometimes the left mouse button stops working. The right button, the
  movements, and the keyboard all still work normally. The laptop's
  touch screen also still works. The left mouse button doesn't work
  anywhere, neither in the application nor in the shell widgets.

  Unplugging/plugging the (usb) mouse has no effect.

  Logging out and back in does temporarily solve the problem.

  It usually occurs after resuming from suspend, but it once did occur
  shortly after plugging in an usb pendrive (this might be a coincidence
  of course).

  This is with Gnome Shell on Wayland, on 18.04.

  This report is similar to bug 1743183, except in that bug it seems the
  left mouse button never works in Wayland. In my case, it usually
  works, but stops working after a while.

  ProblemType: Bug
  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
  Date: Thu Mar  1 17:26:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-01-23 (1132 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-01-10 (49 days ago)

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

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

[Desktop-packages] [Bug 1752804] 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/1752804/+attachment/5066713/+files/CoreDump.gz

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  happend at startuo

  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: Fri Mar  2 08:59:27 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.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/1752804/+subscriptions

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

[Desktop-packages] [Bug 1752877] 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/1752877/+attachment/5067032/+files/CoreDump.gz

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

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

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

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

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

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

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  This may have been caused by power hit.  Started the system and left
  the system to download some data.  Had a power hit (light flickered)
  and came back to check on the download.  Download continuing but had
  the problem report displayed.

  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 08:14:32 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-02-02 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180202)
  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: 0x7f1f74ad1588:movl   $0x0,(%rax)
   PC (0x7f1f74ad1588) 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=0x7f1f74d3902c, 
init_routine=0x7f1f6bbd4490 <__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/1752877/+subscriptions

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

Re: [Desktop-packages] [Bug 1752472] Re: [ffe] Implement an Ubuntu Single Sign-on Provider

2018-03-02 Thread Iain Lane

On Fri, Mar 02, 2018 at 07:51:58AM -, Sebastien Bacher wrote:
> The provider has been discussed with upstream and they are fine on the
> idea, Marco did a first code review and upstream said they would review
> it as well this week.

Please make sure to follow up on the comments upstream and get this
merged, but OK with me to upload.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [ffe] Implement an Ubuntu Single Sign-on Provider

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Add an Ubuntu Single Sing-On provider in gnome-online-accounts. We plan to 
use this inside:
  1) gnome-software
  2) software-properties

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1752472/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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()

** 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/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 1752803] Re: [ffe] use locate informations in the search provider

> Seems like a sensible approach --- this is to avoid tracker, right, and
> so will be dropped next cycle?

Indeed and correct, thanks!

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

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

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

Title:
  [ffe] use locate informations in the search provider

Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  That's part of fixing bug #1732780 and making files listed in the
  desktop overview for the LTS (which is currently not working and a
  regression over Unity or upstream GNOME).

  The proposed change uses "locate" as a backend (same as unity was doing), the 
corresponding patch is available there
  
https://gitlab.gnome.org/3v1n0/nautilus/blob/ubuntu-3-26/debian/patches/0019-search-engine-add-locate-based-search-engine.patch

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

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

[Desktop-packages] [Bug 1752709] Re: Left mouse button gets stuck down (in software), usually after suspend/resume

2018-03-02 Thread gpothier

It seems Unity is not affected. I took some time to respond because I
could not reproduce the bug yesterday after rebooting the machine. It
seems something triggers the bug, and once it has been triggered I can
consistently reproduce it with pm-suspend, even after logging out and
back in (this in itself makes the issue disappear, but suspending makes
it appear again).

So now that it occurred again, I logged several times into Unity and
Gnome Shell (xorg), and executing pm-suspend always made the problem
appear in Gnome Shell, and never did in Unity.

I still do not know what triggers the bug in the first place, but it
seems to occur usually when I go from work to home or vice versa, which
implies suspending, closing the lid, unplugging the AC adapter, external
monitor and USB hub.

For what it's worth, the problem occurs with my USB mouse and with my
Bluetooth mouse.

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

Title:
  Left mouse button gets stuck down (in software), usually after
  suspend/resume

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libinput package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Sometimes the left mouse button stops working. The right button, the
  movements, and the keyboard all still work normally. The laptop's
  touch screen also still works. The left mouse button doesn't work
  anywhere, neither in the application nor in the shell widgets.

  Unplugging/plugging the (usb) mouse has no effect.

  Logging out and back in does temporarily solve the problem.

  It usually occurs after resuming from suspend, but it once did occur
  shortly after plugging in an usb pendrive (this might be a coincidence
  of course).

  This is with Gnome Shell on Wayland, on 18.04.

  This report is similar to bug 1743183, except in that bug it seems the
  left mouse button never works in Wayland. In my case, it usually
  works, but stops working after a while.

  ProblemType: Bug
  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
  Date: Thu Mar  1 17:26:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-01-23 (1132 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-01-10 (49 days ago)

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

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

Re: [Desktop-packages] [Bug 1752803] [NEW] [ffe] use locate informations in the search provider

2018-03-02 Thread Iain Lane

On Fri, Mar 02, 2018 at 07:45:20AM -, Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug by Sebastien Bacher (seb128):
> 
> That's part of fixing bug #1732780 and making files listed in the
> desktop overview for the LTS (which is currently not working and a
> regression over Unity or upstream GNOME).
> 
> The proposed change uses "locate" as a backend (same as unity was doing), the 
> corresponding patch is available there
> https://gitlab.gnome.org/3v1n0/nautilus/blob/ubuntu-3-26/debian/patches/0019-search-engine-add-locate-based-search-engine.patch

Seems like a sensible approach --- this is to avoid tracker, right, and
so will be dropped next cycle?

Go ahead - we should get this in early to shake out bugs if there are
any.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [ffe] use locate informations in the search provider

Status in nautilus package in Ubuntu:
  New

Bug description:
  That's part of fixing bug #1732780 and making files listed in the
  desktop overview for the LTS (which is currently not working and a
  regression over Unity or upstream GNOME).

  The proposed change uses "locate" as a backend (same as unity was doing), the 
corresponding patch is available there
  
https://gitlab.gnome.org/3v1n0/nautilus/blob/ubuntu-3-26/debian/patches/0019-search-engine-add-locate-based-search-engine.patch

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

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

[Desktop-packages] [Bug 1752862] 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/1752862/+attachment/5066990/+files/CoreDump.gz

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It happened at startup.

  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: Fri Mar  2 00:38:04 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-24 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180224)
  ProcCmdline: /usr/bin/gnome-shell
  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/1752862/+subscriptions

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

[Desktop-packages] [Bug 1752859] 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/1752859/+attachment/5066978/+files/CoreDump.gz

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

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

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

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

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

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

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

Status in deja-dup package in Ubuntu:
  New

Bug description:
  not sure.

  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 05:23:45 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180122)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0860d68588:movl   $0x0,(%rax)
   PC (0x7f0860d68588) 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=0x7f0860fd002c, 
init_routine=0x7f0857db5490 <__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/1752859/+subscriptions

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

[Desktop-packages] [Bug 1752751] Re: package libreoffice-common 1:4.2.8-0ubuntu5.3 failed to install/upgrade: cannot compute MD5 hash for file '/etc/bash_completion.d/libreoffice.sh': failed to read (

2018-03-02 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package libreoffice-common 1:4.2.8-0ubuntu5.3 failed to
  install/upgrade: cannot compute MD5 hash for file
  '/etc/bash_completion.d/libreoffice.sh': failed to read (Input/output
  error)

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  i got a bug from pornhub

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-common 1:4.2.8-0ubuntu5.3
  ProcVersionSignature: Ubuntu 4.4.0-113.136~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-113-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Thu Mar  1 18:47:51 2018
  DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu5.3:cannot 
compute MD5 hash for file '/etc/bash_completion.d/libreoffice.sh': failed to 
read (Input/output error)
  ErrorMessage: cannot compute MD5 hash for file 
'/etc/bash_completion.d/libreoffice.sh': failed to read (Input/output error)
  InstallationDate: Installed on 2015-04-03 (1063 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:4.2.8-0ubuntu5.3 failed to 
install/upgrade: cannot compute MD5 hash for file 
'/etc/bash_completion.d/libreoffice.sh': failed to read (Input/output error)
  UpgradeStatus: Upgraded to trusty on 2017-12-31 (60 days ago)
  modified.conffile..etc.bash.completion.d.libreoffice.sh: [inaccessible: 
[Errno 5] Input/output error]

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

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

[Desktop-packages] [Bug 1752905] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-03-02 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/1752905

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I have no idea what is it or how i fix it.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  Uname: Linux 4.13.2-041302-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Mar  2 17:16:47 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9qWUp6/5-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-01-03 (422 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-21 (132 days ago)

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

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

[Desktop-packages] [Bug 1682695] Re: System stops recognizing correct screen resolution

2018-03-02 Thread John David Galt

I can't tell if it's still valid because my monitor stopped working and
had to be replaced within a month afterward, and the problem hasn't
happened since.

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

Title:
  System stops recognizing correct screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Up to last night, I was using my system just fine, with my 1280x1024
  monitor.  Today, the system boots up with all the text and icons much
  larger, and Settings -> Displays now informs me that my monitor is
  only 1024x768 and won't permit me to change it back to the correct
  setting.  I haven't changed anything, hardware or software.  How do I
  make it work correctly again?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 13 19:07:58 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8321]
  InstallationDate: Installed on 2017-03-26 (18 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: MSI MS-7865
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: AM1I (MS-7865)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd02/21/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7865
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Apr 13 19:04:54 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 04f3:0103KEYBOARD, id 8
   inputHID 04f3:0103KEYBOARD, id 9
   inputUSB Optical MouseMOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output DVI-I-1   
VGA-1
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

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

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

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

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

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 #1724439, 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/1752853/+attachment/5066948/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724439
   gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from 
ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from 
function_call()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This crash appeared shortly after waking the computer up from suspend
  and logging in.

  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: ubuntu:GNOME
  Date: Fri Mar  2 00:47:50 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ffa410ae2d4 :mov
0x18(%rax),%eax
   PC (0x7ffa410ae2d4) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1742946] Re: "gio monitor" does not work

Thank you for your bug report, indeed that's an upstream bug which was fixed 
after .1 but before .3. The fix is in the current bionic version
The corresponding upstream bug is 
https://bugzilla.gnome.org/show_bug.cgi?id=790093

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

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

** Also affects: glib via
   https://bugzilla.gnome.org/show_bug.cgi?id=790093
   Importance: Unknown
   Status: Unknown

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

Title:
  "gio monitor" does not work

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  # ls -l /etc/adduser.conf
  -rw-r--r-- 1 root root 2981 Mar 11  2012 /etc/adduser.conf
  # gio monitor file:///etc/adduser.conf
  gio: No locations given

  Usage:
gio monitor [OPTION…] [LOCATION...]

  Monitor files or directories for changes.

  Options:
-d, --dir=LOCATIONMonitor a directory (default: depends on type)
-f, --file=LOCATION   Monitor a file (default: depends on type)
-D, --direct=LOCATION Monitor a file directly (notices changes made via 
hardlinks)
-s, --silent=LOCATION Monitors a file directly, but doesn’t report 
changes
-n, --no-movesReport moves and renames as simple 
deleted/created events
-m, --mounts  Watch for mount events

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 14:29:42 2018
  InstallationDate: Installed on 2012-03-12 (2131 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120311)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-02 Thread Alexander Stohr

probably related to bug #1749261

-- 
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: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1723376] Re: Disk read / Disk write are backwards in the Processes page

The issue has been fixed in 3.27 which is in bionic now

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

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

Title:
  Disk read / Disk write are backwards in the Processes page

Status in Gnome System Monitor:
  Fix Released
Status in gnome-system-monitor package in Ubuntu:
  Fix Released

Bug description:
  Disk read / Disk write are backwards in the Processes page of gnome-
  system-monitor.

  For a process that is only reading from disk it shows values under
  "Disk write". And for a process that is only writing to disk, it shows
  values under "Disk read".

  Running iotop or monitoring /proc/PID/io shows no such bug anywhere
  else. Only in gnome-system-monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-system-monitor 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 13 17:30:30 2017
  InstallationDate: Installed on 2017-05-03 (163 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/1723376/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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)

2018-03-02 Thread Alexander Stohr

switching to "beta" version of gcc (Ubuntu 7.3.0-5ubuntu1~14.04.york0) 7.3.0
and rebuilding the kernel modules in question for 4.4.0-116 seemingly did the 
job.

is this really what you wanted from a good amount of the end users by
publishing those kernel?

** Summary changed:

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

** Also affects: gcc
   Importance: Undecided
   Status: New

-- 
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: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1302546] Re: gtk drawing area - missing or incorrect expose or draw event

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gtk drawing area - missing or incorrect expose or draw event

Status in GTK+:
  Fix Released
Status in LiVES:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Application is Fotoxx 14.04. A GTK notebook is used with tabs
  containing drawing areas inside scrolled windows. The program works on
  Ubuntu 13.10 and earlier (GTK 3.8) and fails on Ubuntu 14.04 beta (as
  of April 4) (GTK 3.10).

  When the notebook tab is changed the new tab's drawing area is not
  updated (Fotoxx gallery page). Some prior data is present and the rest
  is background color only. Clicking elsewhere and then clicking the
  window title bar (unfocus and refocus the app) causes the tab to
  update correctly. Removing the default "double buffered" attribute
  from the drawing area widget after it is created makes everything work
  correctly on Ubuntu 14.04. However on earlier Ubuntu releases the
  background is not updated and is filled with data from the previous
  tab.

  This seems to be a problem with missing "draw" events or events with
  incorrect update regions. I have verified that draw events are not
  sent when the tab is switched but are sent when the window acquires
  focus.

  The GTK bug tracking system seems to have related bugs but I cannot be
  sure (too much technical jargon for my knowledge of GTK internals). I
  did not file a report there because the expected knowledge of
  internals is missing. The bug may be fixed in GTK 3.12.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-0 3.10.7-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 13:28:59 2014
  InstallationDate: Installed on 2014-03-28 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1168978] Re: Evince crashes consistently, reading 50+ pages into specific PDF document