date:20180521

João Gabriel, thank you for reporting this and helping make Ubuntu better. 
However, your crash report is missing. Please follow these instructions to have 
apport report a new bug about your crash that can be dealt with by the 
automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && 
sudo apt-get -y install libreoffice-dbg uno-libs3-dbg ure-dbg && sudo service 
apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your 
/var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'. If you run the command against the crash 
report and a window pops up asking you to report this, but then never opens a 
new report, you would be affected by 
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to 
WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

Please follow https://wiki.ubuntu.com/LibreOfficeBugWrangling when you
file this crash report so the necessary information is provided.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently.

Please do not attach your crash report manually to this report and
reopen it.

As well, please do not announce in this report you created a new bug
report.

Thank you for your help.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

Title:
  Libreoffice crashed

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Libreoffice crashed without evident reason.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 26 10:11:43 2017
  InstallationDate: Installed on 2017-03-18 (129 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1709713] Re: Libreoffice freezes

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

** This bug has been marked a duplicate of bug 1706605
   Libreoffice crashed

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

Title:
  Libreoffice freezes

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Libreoffice freezes without apparent cause.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  9 17:37:13 2017
  InstallationDate: Installed on 2017-03-18 (144 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1710476] Re: Libreoffice crashed

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

** This bug has been marked a duplicate of bug 1706605
   Libreoffice crashed

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

Title:
  Libreoffice crashed

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Libreoffice writer crashed while drawing in it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 13 12:11:43 2017
  InstallationDate: Installed on 2017-03-18 (148 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716295] Re: LibreOffice 5.1.6.2 Crashes unity in Ubuntu 16.04

** Package changed: libreoffice (Ubuntu) => unity (Ubuntu)

** Summary changed:

- LibreOffice 5.1.6.2 Crashes unity in Ubuntu 16.04
+ Unity crashes in Ubuntu 16.04

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

Title:
  Unity crashes in Ubuntu 16.04

Status in unity package in Ubuntu:
  New

Bug description:
  Every time I open LibreOffice apps, the app seems to start up and
  display OK initially but after 5-10 seconds "flashes" (window gets
  slightly larger then goes back to normal) repeatedly and Unity crashes
  (all icons gone from top menu panel).

  dmesg shows:
  [  307.892818] show_signal_msg: 36 callbacks suppressed
  [  307.892823] unity-panel-ser[2395]: segfault at 0 ip 7fdf932c6425 sp 
7ffea2dec098 error 4 in libc-2.23.so[7fdf93239000+1c]
  [  311.363310] unity-panel-ser[4138]: segfault at 0 ip 7f51e8421425 sp 
7ffe281fdbe8 error 4 in libc-2.23.so[7f51e8394000+1c]
  [  311.702691] unity-panel-ser[4156]: segfault at 0 ip 7f7aecd23425 sp 
7ffc7cc7b268 error 4 in libc-2.23.so[7f7aecc96000+1c]
  [  312.071409] unity-panel-ser[4205]: segfault at 0 ip 7fe867000425 sp 
7ffe7831a388 error 4 in libc-2.23.so[7fe866f73000+1c]
  [  312.430360] unity-panel-ser[4215]: segfault at 0 ip 7f8798378425 sp 
7ffd18c59a28 error 4 in libc-2.23.so[7f87982eb000+1c]
  [  312.781823] unity-panel-ser[4225]: segfault at 0 ip 7f78ee443425 sp 
7ffcb81e1768 error 4 in libc-2.23.so[7f78ee3b6000+1c]
  [  313.127139] unity-panel-ser[4234]: segfault at 0 ip 7f41b6e4a425 sp 
7ffef9ccc198 error 4 in libc-2.23.so[7f41b6dbd000+1c]
  [  313.465614] unity-panel-ser[4244]: segfault at 0 ip 7f917c289425 sp 
7fffa4829b88 error 4 in libc-2.23.so[7f917c1fc000+1c]
  [  313.812785] unity-panel-ser[4253]: segfault at 0 ip 7fae47baa425 sp 
7ffc6b8b9dd8 error 4 in libc-2.23.so[7fae47b1d000+1c]
  [  314.150345] unity-panel-ser[4262]: segfault at 0 ip 7f32d5dcf425 sp 
7ffe2ababa38 error 4 in libc-2.23.so[7f32d5d42000+1c]

  Crash file attached.

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

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

[Desktop-packages] [Bug 1669242] Re: libreoffice equations disappear upon editing in impress

Fixed in LO 5.x as per
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1669242/comments/10
.

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

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

Title:
  libreoffice equations disappear upon editing in impress

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Libreoffice
  Version: 4.2.8.2
  Build ID: 420m0(Build:2)

  I am running Ubuntu 14.04.5 LTS with all the latest updates. I have a
  number of Libreoffice presentation documents (.odp) with equations in
  them. I have used and edited these documents for the last year without
  any problem. Today, every time I double click on an equation and go to
  edit it, upon leaving equation mode the equation becomes invisible. I
  don't even have to modify the equation for this to happen and the
  equations are invisible in both editing and full-screen presentation
  mode. If I save my document, restart my machine and reopen my
  document, the equations are still invisible. The equation objects are
  there - I can select the region with the equation and even open up the
  math editor to see that the equation code is definitely present, but I
  have found no way to make them appear outside of the math editor.

  I am attaching a number of screenshots and a test document
  demonstrating the problem.

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

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

[Desktop-packages] [Bug 1649295] Re: LibreOffice Writer docx fails to load styles

Richard, the issue you are reporting is an upstream one. Could you
please send the bug to the developers of the software by following the
instructions at http://wiki.documentfoundation.org/BugReport ? Please
provide the upstream URL so it may be added as a bugwatch that will
advise about the status. Thanks in advance.

** Description changed:

- On recovery, LibreOffice Recovery of docx format documents lose all styles in 
20% of cases.
- (this is improvement b/c in 16.04 recovery was not functional)
+ 1. Open
+ 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1649295/+attachment/4794230/+files/Linux%20Operations.docx
  
- Text Body style becomes Default Style
- All style information is reset and has to be reloaded using LibreOffice - 
Styles - Styles and Formatting F11 - Load Styles… - Overwrite, OK
+ 2. Put caret on first line noting “Linux Operations”, which has style
+ “Default Style”. Change to style “Title” using the Apply Paragraph Style
+ of the Formatting toolbar.
+ 
+ 3. Save as docx.
+ 
+ 4. Close, reopen, and notice that the style is now "Default Style"
+ instead of "Title".
+ 
+ WORKAROUND: Save file as .odt.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:44:49 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

** Tags added: bionic

** Changed in: libreoffice (Ubuntu)
   Importance: High => Low

** Changed in: libreoffice (Ubuntu)
   Status: New => Triaged

** Summary changed:

- LibreOffice Writer docx fails to load styles
+ Writer doesn't preserve Style after saving to Microsoft Word 2007-2013 XML 
(.docx), close, and reopening file

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

Title:
  Writer doesn't preserve Style after saving to Microsoft Word 2007-2013
  XML (.docx), close, and reopening file

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  1. Open
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1649295/+attachment/4794230/+files/Linux%20Operations.docx

  2. Put caret on first line noting “Linux Operations”, which has style
  “Default Style”. Change to style “Title” using the Apply Paragraph
  Style of the Formatting toolbar.

  3. Save as docx.

  4. Close, reopen, and notice that the style is now "Default Style"
  instead of "Title".

  WORKAROUND: Save file as .odt.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:44:49 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1640632] Re: Libreoffice Word uses 100% cpu after font change

Fixed in 5.2+ as per
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1640632/comments/2
.

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

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

Title:
  Libreoffice Word uses 100% cpu after font change

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  On a fully patched 16.04 Ubuntu 11/9/2016, running a default Libreoffice 
installation (1:5.1.4-0ubuntu1) with just a browser running, start the system 
monitor.  Open the Libreoffice Word icon in the Dash, and type in two lines in 
different fonts:
  Liberation serif originally.
  Bitstream Charter originally.

  Select both lines (which may be as short as one letter), and change
  the font in the font input to comic sans, while watching the system
  monitor (default settings, cpu history). Note all cpu traces are near
  the 0-20% range.  One cpu trace will quickly go to 100% and stay
  there. On my system, I get 8 cpu traces, while the cpu may change, one
  will stay at 100% until exiting the document.  No further actions are
  necessary to keep the cpu at 100%.

  At the document exit, a dialog will appear, asking to "Save change to
  document "Untitled 1" before closing?" with buttons below --
  frequently (but not always) the entire dialog window will be blank,
  but the  invisible "Dont Save" button will still work if clicked.

  askubuntu question http://askubuntu.com/questions/847567/libreoffice-
  uses-100-cpu-after-changing-the-font-of-a-whole-document  has
  indicated that Libreoffice Calc displays the same problem, so the
  problem is probably in the common or core Libreoffice package.  First
  two cells, letter A in Liberation serif and next cell B in Bitstream
  Charter, select both lines, and change font to comic serif -- a cpu
  quickly goes to 100%.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy libreoffice-core
  libreoffice-core:
Installed: 1:5.1.4-0ubuntu1
Candidate: 1:5.1.4-0ubuntu1
Version table:
   *** 1:5.1.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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

[Desktop-packages] [Bug 1627874] Re: Document crashes Libreoffice Writer

Confirmed fixed in Bionic.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Document crashes Libreoffice Writer

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  The attached document crashes LibreOffice writer when attempting to
  open it. The first page gets displayed, and the the application
  crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-writer 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 26 19:17:10 2016
  InstallationDate: Installed on 2015-01-23 (612 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-03-21 (189 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1627874/+subscriptions

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

[Desktop-packages] [Bug 1637468] Re: Opening large SpreadsheetML cause "General input/output error"

Confirmed fixed in Bionic.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Opening large SpreadsheetML cause "General input/output error"

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  After fixing this bug
  https://bugs.documentfoundation.org/show_bug.cgi?id=90999 opening
  large SpreadsheetML takes a very long time and causes an "General
  input/output error"

  To reproduce just try to open attached file

  In my case:
  Ubuntu 16.04
  LibreOffice 1:5.1.4-0ubuntu1
  Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
  opening takes more than 60 seconds and causes an "General input/output error"

  After some research I solved this problem and now opening takes only 5
  seconds

  The patch will be attached in next message

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1637468/+subscriptions

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

[Desktop-packages] [Bug 1645122] Re: package libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

2018-05-21 Thread Rolf Leggewie

from HookError_source_libmtp.txt:
NameError: name 'attach_related_packages' is not defined

Not sure if that relevant to this bug.  The duplicate report is in
German for those not so fluent in Finnish ;-)

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

Title:
  package libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libmtp package in Ubuntu:
  Confirmed

Bug description:
  Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
  Käsittelyssä tapahtui liian monta virhettä:
   libmtp-common
   libmtp9:i386
   libmtp-dev:i386
   libmtp-runtime
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  Date: Sun Nov 27 20:20:10 2016
  Dependencies:
   
  DuplicateSignature: 
package:libmtp-common:1.1.6-20-g1b9f164-1ubuntu2.1:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2012-08-09 (1570 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: libmtp
  Title: package libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-08-08 (842 days ago)

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

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

[Desktop-packages] [Bug 1522342] Re: package libmtp9:amd64 1.1.6-20-g1b9f164-1ubuntu2.1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

2018-05-21 Thread Rolf Leggewie

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

** This bug has been marked a duplicate of bug 1645122
   package libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration

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

Title:
  package libmtp9:amd64 1.1.6-20-g1b9f164-1ubuntu2.1 failed to
  install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in libmtp package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libmtp9:amd64 1.1.6-20-g1b9f164-1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17
  Uname: Linux 3.16.0-51-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Dec  2 10:30:42 2015
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2015-04-27 (219 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.10
  SourcePackage: libmtp
  Title: package libmtp9:amd64 1.1.6-20-g1b9f164-1ubuntu2.1 failed to 
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1645122] Re: package libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

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

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

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

Title:
  package libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libmtp package in Ubuntu:
  Confirmed

Bug description:
  Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
  Käsittelyssä tapahtui liian monta virhettä:
   libmtp-common
   libmtp9:i386
   libmtp-dev:i386
   libmtp-runtime
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  Date: Sun Nov 27 20:20:10 2016
  Dependencies:
   
  DuplicateSignature: 
package:libmtp-common:1.1.6-20-g1b9f164-1ubuntu2.1:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2012-08-09 (1570 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: libmtp
  Title: package libmtp-common 1.1.6-20-g1b9f164-1ubuntu2.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-08-08 (842 days ago)

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

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

[Desktop-packages] [Bug 1772567] [NEW] Alcatel Pop4 unknown to libmtp

2018-05-21 Thread Rolf Leggewie

Public bug reported:

$ mtp-detect
Device 0 (VID=1bbb and PID=a00f) is UNKNOWN in libmtp v1.1.13.
Please report this VID/PID and the device model to the libmtp development team

reported at https://sourceforge.net/p/libmtp/bugs/1776/

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


** Tags: bionic

** Description changed:

  $ mtp-detect
  Device 0 (VID=1bbb and PID=a00f) is UNKNOWN in libmtp v1.1.13.
  Please report this VID/PID and the device model to the libmtp development team
+ 
+ reported at https://sourceforge.net/p/libmtp/bugs/1776/

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

Title:
  Alcatel Pop4 unknown to libmtp

Status in libmtp package in Ubuntu:
  New

Bug description:
  $ mtp-detect
  Device 0 (VID=1bbb and PID=a00f) is UNKNOWN in libmtp v1.1.13.
  Please report this VID/PID and the device model to the libmtp development team

  reported at https://sourceforge.net/p/libmtp/bugs/1776/

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

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

[Desktop-packages] [Bug 1662281] Re: Firefox shows post-crash page after reboot or logoff

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

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

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

Title:
  Firefox shows post-crash page after reboot or logoff

Status in gnome-session:
  Invalid
Status in firefox package in Ubuntu:
  Expired
Status in gnome-session package in Ubuntu:
  Expired

Bug description:
  When rebooting or logging off, Firefox and thinks it crashed, and
  shows the post-crash session restore  page.

  See also Mozilla bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=557601 and related bugs
  there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 51.0.1+build2-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reuben 1902 F pulseaudio
   /dev/snd/controlC1:  reuben 1902 F pulseaudio
  BuildID: 20170201174907
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Feb  6 16:04:15 2017
  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 2017-02-02 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.2.1 dev enp0s31f6  proto static  metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000 
   192.168.2.0/24 dev enp0s31f6  proto kernel  scope link  src 192.168.2.6  
metric 100
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=51.0.1/20170201174907 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0225
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF Z270 MARK 2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0225:bd10/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ270MARK2:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1662281] Re: Firefox shows post-crash page after reboot or logoff

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

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

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

Title:
  Firefox shows post-crash page after reboot or logoff

Status in gnome-session:
  Invalid
Status in firefox package in Ubuntu:
  Expired
Status in gnome-session package in Ubuntu:
  Expired

Bug description:
  When rebooting or logging off, Firefox and thinks it crashed, and
  shows the post-crash session restore  page.

  See also Mozilla bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=557601 and related bugs
  there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 51.0.1+build2-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reuben 1902 F pulseaudio
   /dev/snd/controlC1:  reuben 1902 F pulseaudio
  BuildID: 20170201174907
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Feb  6 16:04:15 2017
  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 2017-02-02 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.2.1 dev enp0s31f6  proto static  metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000 
   192.168.2.0/24 dev enp0s31f6  proto kernel  scope link  src 192.168.2.6  
metric 100
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=51.0.1/20170201174907 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0225
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF Z270 MARK 2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0225:bd10/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ270MARK2:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1758102] Re: ubuntu setting not working

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

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

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

Title:
  ubuntu setting not working

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

Bug description:
  ubuntu setting not working

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 22 23:40:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-04 (383 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1772557] [NEW] FREETYPE_PROPERTIES environment variable is not respected

2018-05-21 Thread 丁卓成

Public bug reported:

As stated by the Freetype documentation, I should be able to use
`FREETYPE_PROPERTIES` to control some options such as whether TrueType
fonts are hinted using Hinting Engine v35 or v40, or whether stem
darkening for CFF(i.e. OpenType PostScript Flavor) fonts are enabled. I
think this should work in everything that uses FreeType, but apparently
it doesn't work in Gnome-Terminal. It does work in xterm, and even
xfce4-terminal, which also uses libVTE to provide terminal emulation.

Actual Results:
`FREETYPE_PROPERTIES` doesn't take effect.

Expected Results:
Should work as in xterm or xfce4-terminal.

Additional Information:
I'm on Ubuntu 18.04, with gnome-terminal 3.28.1. The correctly working
xfce4-terminal's version is 0.8.7.3.

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

** Attachment added: "xfce4-terminal (left) vs gnome-terminal (right)"

https://bugs.launchpad.net/bugs/1772557/+attachment/5142674/+files/freetype_properties.png

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

Title:
FREETYPE_PROPERTIES environment variable is not respected

Status in gnome-terminal package in Ubuntu:
New

Bug description:
As stated by the Freetype documentation, I should be able to use
`FREETYPE_PROPERTIES` to control some options such as whether TrueType
fonts are hinted using Hinting Engine v35 or v40, or whether stem
darkening for CFF(i.e. OpenType PostScript Flavor) fonts are enabled.
I think this should work in everything that uses FreeType, but
apparently it doesn't work in Gnome-Terminal. It does work in xterm,
and even xfce4-terminal, which also uses libVTE to provide terminal
emulation.

Actual Results:
`FREETYPE_PROPERTIES` doesn't take effect.

Expected Results:
Should work as in xterm or xfce4-terminal.

Additional Information:
I'm on Ubuntu 18.04, with gnome-terminal 3.28.1. The correctly working
xfce4-terminal's version is 0.8.7.3.

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-21 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: Triaged => Fix Released

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Fix Released
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  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
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button does nothing

2018-05-21 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => High

** Tags added: somerville

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

Title:
  ubiquity-dm / Install Ubuntu - Power button does nothing

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Artful Desktop 20170907

  In ubiquity-dm and 'Install Ubuntu' the power button does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity 17.10.6
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 09:55:57 2017
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1715602/+subscriptions

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

[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-05-21 Thread Chris Guiver

attached dmesg ( dmesg >~/dmesg_2018-05-22.txt )

this COULD be the key bit - unsure (thanks to well_laid_down in
#xubuntu)

[488956.180193] [drm:cypress_dpm_set_power_state [radeon]] *ERROR* 
rv770_restrict_performance_levels_before_switch failed
[488957.778128] traps: light-locker[9579] trap int3 ip:7f228a785c41 
sp:7ffdee1a6c50 error:0 in libglib-2.0.so.0.5600.1[7f228a734000+113000]


( dmesg file is unedited, contains other crash info i believe unreleated; but 
may contain detail on the same problem yesterday morning )

** Attachment added: "dmesg >~/dmesg_2018-05-22.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5142673/+files/dmesg_2018-05-22.txt

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442

[Desktop-packages] [Bug 1772550] Re: Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from InitOutput() from dix_main() from __libc_start_main()

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

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

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

Title:
  Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe()
  from InitOutput() from dix_main() from __libc_start_main()

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1772498] Re: Command "X -configure" segmentation fault

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

Make that bug 1753012.

** This bug is no longer a duplicate of bug 1772550
   Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from 
InitOutput() from dix_main() from __libc_start_main()
** This bug has been marked a duplicate of private bug 1753012

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

Title:
  Command "X -configure" segmentation fault

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Was searching for a method to disable DPMS via a custom
  /etc/X11/xorg.conf file and discovered this bug. Under a fresh Ubuntu
  18.04 minimal desktop installation, after stopping gdm3 and executing
  "sudo X -configure" in /etc/X11 subdirectory to create an xorg.conf
  file, this happens:

  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-119-generic x86_64 Ubuntu
  Current Operating System: Linux {hostname} 4.15.0-20-generic #21-Ubuntu SMP 
Tue Apr 24 06:16:15 UTC 2018 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=562f17d1-d033-4aa0-ba91-f8a04e7510a6 ro quiet splash vt.handoff=1
  Build Date: 13 April 2018  08:07:36PM
  xorg-server 2:1.19.6-1ubuntu4 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.34.0
  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 21 11:26:02 2018
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x564f083b08ad]
  (EE) 1: /usr/lib/xorg/Xorg (0x564f081f8000+0x1bc649) [0x564f083b4649]
  (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb92b9ca000+0x12890) 
[0x7fb92b9dc890]
  (EE) 3: /usr/lib/xorg/Xorg (0x564f081f8000+0xb2294) [0x564f082aa294]
  (EE) 4: /usr/lib/xorg/Xorg (xf86BusProbe+0x9) [0x564f08282229]
  (EE) 5: /usr/lib/xorg/Xorg (InitOutput+0x7f1) [0x564f08290e51]
  (EE) 6: /usr/lib/xorg/Xorg (0x564f081f8000+0x56cd3) [0x564f0824ecd3]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
[0x7fb92b5fab97]
  (EE) 8: /usr/lib/xorg/Xorg (_start+0x2a) [0x564f08238b8a]
  (EE)
  (EE) Segmentation fault at address 0x50
  (EE)
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE)
  (EE)
  Please consult the The X.Org Foundation support
  at http://wiki.x.org
  for help.
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE)
  (EE) Server terminated with error (1). Closing log file.

  lsb_release -rd

  Description: Ubuntu 18.04 LTS
  Release: 18.04

  apt-cache policy xorg

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

  What I expected:

I expected "X -configure" to write a default xorg.conf file in
  /etc/X11

  What happened instead:

X binary crashed

  Personal Note:

Will create ugly hack to solve my problem while this bug gets fixed.
  Not holding my breathe, please add "you don't need an xorg.conf file"
  comments below. :D

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

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

[Desktop-packages] [Bug 1772498] Re: Command "X -configure" segmentation fault

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

Thanks for the bug report.

This appears to be bug 1772550.

** This bug has been marked a duplicate of bug 1772550
   Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from 
InitOutput() from dix_main() from __libc_start_main()

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

Title:
  Command "X -configure" segmentation fault

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Was searching for a method to disable DPMS via a custom
  /etc/X11/xorg.conf file and discovered this bug. Under a fresh Ubuntu
  18.04 minimal desktop installation, after stopping gdm3 and executing
  "sudo X -configure" in /etc/X11 subdirectory to create an xorg.conf
  file, this happens:

  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-119-generic x86_64 Ubuntu
  Current Operating System: Linux {hostname} 4.15.0-20-generic #21-Ubuntu SMP 
Tue Apr 24 06:16:15 UTC 2018 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=562f17d1-d033-4aa0-ba91-f8a04e7510a6 ro quiet splash vt.handoff=1
  Build Date: 13 April 2018  08:07:36PM
  xorg-server 2:1.19.6-1ubuntu4 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.34.0
  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 21 11:26:02 2018
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x564f083b08ad]
  (EE) 1: /usr/lib/xorg/Xorg (0x564f081f8000+0x1bc649) [0x564f083b4649]
  (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb92b9ca000+0x12890) 
[0x7fb92b9dc890]
  (EE) 3: /usr/lib/xorg/Xorg (0x564f081f8000+0xb2294) [0x564f082aa294]
  (EE) 4: /usr/lib/xorg/Xorg (xf86BusProbe+0x9) [0x564f08282229]
  (EE) 5: /usr/lib/xorg/Xorg (InitOutput+0x7f1) [0x564f08290e51]
  (EE) 6: /usr/lib/xorg/Xorg (0x564f081f8000+0x56cd3) [0x564f0824ecd3]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
[0x7fb92b5fab97]
  (EE) 8: /usr/lib/xorg/Xorg (_start+0x2a) [0x564f08238b8a]
  (EE)
  (EE) Segmentation fault at address 0x50
  (EE)
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE)
  (EE)
  Please consult the The X.Org Foundation support
  at http://wiki.x.org
  for help.
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE)
  (EE) Server terminated with error (1). Closing log file.

  lsb_release -rd

  Description: Ubuntu 18.04 LTS
  Release: 18.04

  apt-cache policy xorg

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

  What I expected:

I expected "X -configure" to write a default xorg.conf file in
  /etc/X11

  What happened instead:

X binary crashed

  Personal Note:

Will create ugly hack to solve my problem while this bug gets fixed.
  Not holding my breathe, please add "you don't need an xorg.conf file"
  comments below. :D

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

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

[Desktop-packages] [Bug 1740865] Re: gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size → g_byte_array_set_size → read_cb

2018-05-21 Thread Robert Ancell

** Description changed:

- The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.3-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d94c431d27115bab216f9e1ea756f876e7cd933b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
- If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ [Impact]
+ snapd-glib can do an invalid memory access when parsing HTTP chunked data. 
Found doing code inspection and testing based on crash reports.
+ 
+ [Test Case]
+ No specific trigger - just look for reduced reports on errors.ubuntu.com.
+ 
+ [Regression Potential]
+ Some risk of further breaking HTTP handling in snapd-glib. Updated algorithm 
tested in a test program run through valgrind to give confidence in the changes.
+ 
+ Error reports:
+ 
+ https://errors.ubuntu.com/problem/d94c431d27115bab216f9e1ea756f876e7cd933b

** Changed in: snapd-glib (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size
  → g_byte_array_set_size → read_cb

Status in snapd-glib package in Ubuntu:
  Fix Committed
Status in snapd-glib source package in Bionic:
  In Progress
Status in snapd-glib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  snapd-glib can do an invalid memory access when parsing HTTP chunked data. 
Found doing code inspection and testing based on crash reports.

  [Test Case]
  No specific trigger - just look for reduced reports on errors.ubuntu.com.

  [Regression Potential]
  Some risk of further breaking HTTP handling in snapd-glib. Updated algorithm 
tested in a test program run through valgrind to give confidence in the changes.

  Error reports:

  https://errors.ubuntu.com/problem/d94c431d27115bab216f9e1ea756f876e7cd933b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1740865/+subscriptions

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

[Desktop-packages] [Bug 1772550] Re: Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from InitOutput() from dix_main() from __libc_start_main()

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

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

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

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

Title:
  Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe()
  from InitOutput() from dix_main() from __libc_start_main()

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1517660] Re: /usr/bin/Xorg:6:xf86InitViewport:InitOutput:dix_main:__libc_start_main:_start

Fix Released. Crash not seen since Ubuntu 15.10.

** Changed in: xorg-server (Ubuntu)
   Status: New => Fix Released

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

Title:
  /usr/bin/Xorg:6:xf86InitViewport:InitOutput:dix_main:__libc_start_main:_start

Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding xorg-server.  This problem was most recently seen with
  version 2:1.17.2-1ubuntu9, the problem page at
  https://errors.ubuntu.com/problem/db7861ea05594d5eea0169c9b8fdaebf01b3613e
  contains more details.

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

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

[Desktop-packages] [Bug 1772550] Re: Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from InitOutput() from dix_main() from __libc_start_main()

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

** Summary changed:

- 
/usr/lib/xorg/Xorg:6:xf86platformProbe:xf86BusProbe:InitOutput:dix_main:__libc_start_main
+ Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from 
InitOutput() from dix_main() from __libc_start_main()

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

Title:
  Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe()
  from InitOutput() from dix_main() from __libc_start_main()

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1772550] [NEW] Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from InitOutput() from dix_main() from __libc_start_main()

2018-05-21 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bionic trusty xenial yakkety

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

Title:
  Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe()
  from InitOutput() from dix_main() from __libc_start_main()

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1772268] Re: User change login freeze. gnome-session-check-accelerated crashed with SIGSEGV

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

Now tracking in bug 1715365.

** This bug has been marked a duplicate of bug 1715365
   gnome-session-check-accelerated crashed with SIGSEGV in 
g_hash_table_lookup_node()

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

Title:
  User change login freeze. gnome-session-check-accelerated crashed with
  SIGSEGV

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

  ---

  While trying to change to another user account without boot display
  manager freeze. ctr-alt-F2 return back to previous user. While trying
  to log in to another user account after log out from another result to
  same immediate freeze. ctr-alt-del boots and after this login works.

  I am using ubuntu 18.04 fresh install with final release. I have
  checked yes to the the bionic-proposed as similar kind of bug was
  reported to have a fix available.

  gdm3:
    Asennettu: 3.28.0-0ubuntu1.1
    Ehdokas:   3.28.0-0ubuntu1.1
    Versiotaulukko:
   *** 3.28.0-0ubuntu1.1 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.0-0ubuntu1 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 20 17:55:27 2018
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [deleted]

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

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

[Desktop-packages] [Bug 1740865] Re: gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size → g_byte_array_set_size → read_cb

2018-05-21 Thread Robert Ancell

** Package changed: gnome-software (Ubuntu Bionic) => snapd-glib (Ubuntu
Bionic)

** Changed in: snapd-glib (Ubuntu Bionic)
 Assignee: Robert Ancell (robert-ancell) => (unassigned)

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

Title:
  gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size
  → g_byte_array_set_size → read_cb

Status in snapd-glib package in Ubuntu:
  Fix Committed
Status in snapd-glib source package in Bionic:
  In Progress
Status in snapd-glib source package in Cosmic:
  Fix Committed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1740865/+subscriptions

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

[Desktop-packages] [Bug 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node()

It appears this crash might be one of the two top crashes (which look
like they might be the same one crash):

https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f
https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a


** Summary changed:

- gnome-session-check-accelerated crashed with SIGSEGV
+ gnome-session-check-accelerated crashed with SIGSEGV in 
g_hash_table_lookup_node()

** Tags added: bionic

** Description changed:

+ Possibly:
+ https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f
+ https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a
+ 
+ ---
+ 
  bug at login
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-bin 3.25.90-0ubuntu2
  Uname: Linux 4.12.0-041200-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep  3 09:34:09 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated
  InstallationDate: Installed on 2015-04-16 (874 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated
  SegvAnalysis:
-  Segfault happened at: 0x0:   Cannot access memory at address 0x0
-  PC (0x) not located in a known VMA region (needed executable region)!
+  Segfault happened at: 0x0:   Cannot access memory at address 0x0
+  PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
-  ()
-  g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  gdk_x11_atom_to_xatom_for_display () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
-  ()
-  __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291
+  ()
+  g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  gdk_x11_atom_to_xatom_for_display () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
+  ()
+  __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291
  Title: gnome-session-check-accelerated crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago)
  UserGroups:

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

Title:
  gnome-session-check-accelerated crashed with SIGSEGV in
  g_hash_table_lookup_node()

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Possibly:
  https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f
  https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

  ---

  bug at login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-bin 3.25.90-0ubuntu2
  Uname: Linux 4.12.0-041200-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep  3 09:34:09 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated
  InstallationDate: Installed on 2015-04-16 (874 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   ()
   g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gdk_x11_atom_to_xatom_for_display () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ()
   __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291
  Title: gnome-session-check-accelerated crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-05-21 Thread Diep Pham

@seb128 could you advice on next step to resolve this bug?

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1772468] Re: Issue witrh load after login into Ubuntu

When you only see the background colour, is that after you type your
password, or before?

Also, please run 'lspci -k' and attach the output here.

It sounds like you might be describing bug 1766137...

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

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

Title:
  Issue witrh load after login into Ubuntu

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I turn of computer, then turn on and change graphical environment
  (from default Ubuntu environments) in login manager, screen is empty
  and I see only background color. HDD stop load (don't load) gnome-
  shell and other important tasks.

  - On my computer is all software fully actual.
  - I am logged on in Ubuntu Single Sign-On (in PC Ubuntu). It is probably very 
helpful for developers for find issue.

  Tasks for developers of Ubuntu:
  - add/create in next update effective diagnostic tool for issue of this type. 
Source of issue will automatically instantly sent via internet to Ubuntu 
developers. If is it no possible, source of issue (bug report) will 
automatically saved on HDD, and when will successfully logged, issue will sent 
to Ubuntu developer team
  **
  Other bug with Ubuntu Software
  If I install any application from Snap Store and look on other application in 
Ubuntu Software during installation, I see small issues. More information you 
can see on print-screen – in was during installation moment of Skype. Text of 
notification is incorrect too.
  
http://linuxos.sk/media/attachment/blog_post/99/153/Skype_ako_snap_bal%C3%ADk_sa_mi_podarilo_nain%C5%A1talova%C5%A5_tie%C5%BE_na_druh%C3%BD_pokus.jpg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 20:01:26 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1673872] Re: Crash upon opening docx from origin MS Office

UlfZibis, thank you for reporting this and helping make Ubuntu better.

This is confirmed resolved in Bionic.

A couple options are to use a later version of LO via
https://launchpad.net/~libreoffice or upgrade your OS version.

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

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

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

Title:
  Crash upon opening docx from origin MS Office

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Version: 5.1.6.2
  Build-ID: 1:5.1.6~rc2-0ubuntu1~xenial1
  CPU-Threads: 2; BS-Version: Linux 4.4; UI-Render: Standard; 
  Gebietsschema: de-DE (de_DE.UTF-8); Calc: group

  Please refer to
  https://bugs.documentfoundation.org/show_bug.cgi?id=106603

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

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

[Desktop-packages] [Bug 1740865] Re: gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size → g_byte_array_set_size → read_cb

2018-05-21 Thread Robert Ancell

It looks like the cause is the HTTP chunk handling. Testing of this code
showed a couple of buffer overruns, which are now fixed in snapd-glib
1.40.

** Also affects: gnome-software (Ubuntu Cosmic)
   Importance: Medium
   Status: Confirmed

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

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Confirmed => Fix Committed

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

** Changed in: gnome-software (Ubuntu Bionic)
   Importance: Undecided => High

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

** Changed in: gnome-software (Ubuntu Cosmic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size
  → g_byte_array_set_size → read_cb

Status in snapd-glib package in Ubuntu:
  Fix Committed
Status in snapd-glib source package in Bionic:
  In Progress
Status in snapd-glib source package in Cosmic:
  Fix Committed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1740865/+subscriptions

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

[Desktop-packages] [Bug 1772268] Re: User change login freeze

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

Thanks.

It appears you are hitting a common crash in gnome-session-check-accelerated 
that is tracking in:
https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

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

** Description changed:

+ https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a
+ 
+ ---
+ 
  While trying to change to another user account without boot display
  manager freeze. ctr-alt-F2 return back to previous user. While trying to
  log in to another user account after log out from another result to same
  immediate freeze. ctr-alt-del boots and after this login works.
  
  I am using ubuntu 18.04 fresh install with final release. I have checked
  yes to the the bionic-proposed as similar kind of bug was reported to
  have a fix available.
  
  gdm3:
-   Asennettu: 3.28.0-0ubuntu1.1
-   Ehdokas:   3.28.0-0ubuntu1.1
-   Versiotaulukko:
-  *** 3.28.0-0ubuntu1.1 500
- 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.28.0-0ubuntu1 500
- 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Asennettu: 3.28.0-0ubuntu1.1
+   Ehdokas:   3.28.0-0ubuntu1.1
+   Versiotaulukko:
+  *** 3.28.0-0ubuntu1.1 500
+ 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.28.0-0ubuntu1 500
+ 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 20 17:55:27 2018
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=fi_FI.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=fi_FI.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [deleted]

** Summary changed:

- User change login freeze 
+ User change login freeze. gnome-session-check-accelerated crashed with SIGSEGV

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

** No longer affects: gdm3 (Ubuntu)

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

Title:
  User change login freeze. gnome-session-check-accelerated crashed with
  SIGSEGV

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

  ---

  While trying to change to another user account without boot display
  manager freeze. ctr-alt-F2 return back to previous user. While trying
  to log in to another user account after log out from another result to
  same immediate freeze. ctr-alt-del boots and after this login works.

  I am using ubuntu 18.04 fresh install with final release. I have
  checked yes to the the bionic-proposed as similar kind of bug was
  reported to have a fix available.

  gdm3:
    Asennettu: 3.28.0-0ubuntu1.1
    Ehdokas:   3.28.0-0ubuntu1.1
    Versiotaulukko:
   *** 3.28.0-0ubuntu1.1 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.0-0ubuntu1 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 20 17:55:27 2018
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [deleted]

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

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

[Desktop-packages] [Bug 1772212] Re: [nvidia] Night light only on half of 1st screen in dual monitor setup

Thanks for the screenshots.

This may be related to
https://bugzilla.gnome.org/show_bug.cgi?id=784068, but seems a little
different.

Please report the bug to the upstream developers here:
  https://gitlab.gnome.org/GNOME/mutter/issues
and then let us know the URL of that new bug.

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

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

Title:
  [nvidia] Night light only on half of 1st screen in dual monitor setup

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

Bug description:
  Hi,

  The GNOME night light only seems to work on the first half of the
  first screen within a dual monitor setup (Ubuntu 18.04 stock, using
  X11 with Gefore GT240, NVIDIA proprietary drivers).  See attached
  screenshots.

  br, Koen.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  koen   1820 F pulseaudio
   /dev/snd/controlC1:  koen   1820 F pulseaudio
   /dev/snd/controlC3:  koen   1820 F pulseaudio
   /dev/snd/controlC2:  koen   1820 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=9b7457bf-328f-4fe5-9e46-ed14b65d4fb2
  InstallationDate: Installed on 2018-05-05 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   lono wireless extensions.
   
   enp0s10   no wireless extensions.
  MachineType: . .
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5dcdbe58-6afd-4f90-ab58-1f53f5cfa9f4 ro
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 07/31/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: AN-M2HD(MCP68)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Unknow
  dmi.chassis.type: 3
  dmi.chassis.vendor: nVIDIA
  dmi.chassis.version: Unknow
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/31/2008:svn.:pn.:pvrUnknow:rvnhttp//www.abit.com.tw/:rnAN-M2HD(MCP68):rvr1.x:cvnnVIDIA:ct3:cvrUnknow:
  dmi.product.name: .
  dmi.product.version: Unknow
  dmi.sys.vendor: .

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

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

[Desktop-packages] [Bug 689349] Re: [Upstream] Draw file exported to PDF have erroneous pixel-sized dots in Acroread, not in Evince

Confirmed fixed in Bionic.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [Upstream] Draw file exported to PDF have erroneous pixel-sized dots
  in Acroread, not in Evince

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org
  Binary package hint: libreoffice

  1) lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  2) apt-cache policy libreoffice-draw
  libreoffice-draw:
    Installed: 1:3.6.2~rc2-0ubuntu4
    Candidate: 1:3.6.2~rc2-0ubuntu4
    Version table:
   *** 1:3.6.2~rc2-0ubuntu4 0
  900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 
Packages
  400 http://archive.ubuntu.com/ubuntu/ quantal-proposed/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.6.2~rc2-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages

  apt-cache policy acroread
  acroread:
    Installed: 9.5.1-1precise1
    Candidate: 9.5.1-1precise1
    Version table:
   *** 9.5.1-1precise1 0
  100 /var/lib/dpkg/status

  apt-cache policy evince
  evince:
    Installed: 3.6.0-0ubuntu2
    Candidate: 3.6.0-0ubuntu2
    Version table:
   *** 3.6.0-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one performs at the Terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/689349/+attachment/1763870/+files/classnetwork.odg
 && unoconv --listener && unoconv -f pdf classnetwork.odg && acroread 
classnetwork.pdf

  is it looks as it does in Evince.

  4) What happens instead is acroread displays erroneous pixel-sized
  dots as per screenshot
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/689349/+attachment/1763844/+files/garbagescreenshot.png
  , while evince does not.

  First reproduced in Maverick 1:3.3.1-1ubuntu3~maverick1, and
  reproduced in Natty, and Precise.

  Unconfirmed OOo WORKAROUND: The upstream version does _not_ produce
  these effects and is fine.

  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  CheckboxSubmission: 30b6638832e19720cfe8f7a91e5798a4
  CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
  DistroRelease: Ubuntu 12.10
  InstallationDate: Installed on 2012-06-11 (164 days ago)
  InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha i386 (20120131.1)
  MarkForUpload: True
  Package: libreoffice 1:3.6.2~rc2-0ubuntu4
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Tags: quantal
  Uname: Linux 3.5.0-17-generic i686
  UpgradeStatus: Upgraded to quantal on 2012-09-14 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/689349/+subscriptions

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

[Desktop-packages] [Bug 1770443] Re: gdm3 sometimes crash after logout and login again

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

No problem. A purple screen and mouse cursor is probably bug 1766137.
Let's deal with this there.

** This bug has been marked a duplicate of bug 1766137
   [regression] Password accepted but login fails (blank purple screen and 
mouse pointer only)

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

Title:
  gdm3 sometimes crash after logout and login again

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  gdm3 sometimes crash after logout and login again.
  I get a purple screen, a mouse cursor and nothing more.
  After crash, the second login always works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 10 18:19:23 2018
  InstallationDate: Installed on 2018-05-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2018-05-21 Thread Ken Wright

@Manuel,

I added the further content to my Rules file, but it didn't make any
difference.

In case I haven't mentioned it, and because it may be important, I am
able to scan as root, but not as a regular user.

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

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

Status in sane-backends package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1770238] Re: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine.

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

I think your answers would be:

> Does it have a project name?
Yes, "xorg-server". https://launchpad.net/xorg-server

> What would my role be? Debugger, customer, developer?
Customer / debugger.

> What software project are you requesting access for?
"xorg-server". https://launchpad.net/ubuntu/+source/xorg-server

> What is your role within that software project?
User.

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

Title:
  [nvidia] Logging in results in a black screen for many minutes after
  which the login screen reappears and I am able to login fine.

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

Bug description:
  ** Ubuntu Bionic; Nvidia GTX 1050 w/`nvidia-390` drivers

  ** Problem: Logging in results in a black screen for many minutes after which 
the login screen reappears and I am able to login fine. The below log seems to 
be the earliest error when this occurs.
  Note: This happened twice today so far, presumably each time I reboot.

  
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
NVIDIA(GPU-0): Failed to acquire modesetting permission.
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
NVIDIA(0): Failing initialization of X screen 0
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadModule: "nvidia"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadSubModule: "wfb"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadSubModule: "fb"
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
Screen(s) found, but none have a usable configuration.
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: Fatal 
server error:
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) no 
screens found(EE)
  May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)

  ** A systemd-logind watchdog seems to be responsible for the login
  screen reappearing

  May  9 11:20:02 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Watchdog 
timeout (limit 3min)!
  May  9 11:20:02 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Killing 
process 1697 (systemd-logind) with signal SIGABRT.
  May  9 11:20:03 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Main 
process exited, code=dumped, status=6/ABRT
  May  9 11:20:03 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Failed 
with result 'watchdog'.

  ** The Xorg.0.log doesn't seem to have any problem finding the screens
  just before the above error.

  29406:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(II) NVIDIA(0): NVIDIA GPU GeForce GTX 1050 (GP107-A) at PCI:23:0:0 (GPU-0)
  29407:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(0): Memory: 2097152 kBytes
  29408:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(0): VideoBIOS: 86.07.2f.00.68
  29409:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(II) NVIDIA(0): Detected PCI Express Link width: 16X
  29412:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): connected
  29413:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): Internal TMDS
  29414:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0): Acer AL1917 (DFP-0): 330.0 MHz maximum pixel clock
  29415:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: 
(--) NVIDIA(GPU-0):

  
  ** Note that I also saw the watchdog kick in while I was logged in and 
working when I was suddenly sent back to the login screen.  I believe that 
lines up with the syslog timestamp below:

  
  May  9 10:31:24 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Watchdog 
timeout (limit 3min)!
  May  9 10:31:24 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Killing 
process 1691 (systemd-logind) with signal SIGABRT.
  May  9 10:31:25 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Main 
process exited, code=dumped, status=6/ABRT
  May  9 10:31:25 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Failed 
with result 'watchdog'.
  May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: (EE)
  May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: Fatal 
server error:
  May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: (EE) 
systemd-logind disappeared (stopped/restarted?)
  May  9 10:31:25 jcormier-MS-7A93

[Desktop-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

pulseaudio (1:11.1-1ubuntu8) cosmic; urgency=medium

  * 0804-bluez5-device-Rewrite-of-thread-function-reduce-send.patch,
0805-bluez5-device-Fix-memory-leak-in-sco_process_render.patch:
- Reduce latency over bluetooth, using A2DP, when the connection drops
  temporarily (LP: #405294).

 -- Alberto Milone   Mon, 21 May 2018
16:41:41 +0200

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  When the connection drops temporarily, using A2DP, a noticeable latency is 
introduced, and the audio goes out of sync.

  [Test Case]
  1) Enable the -proposed repository, and install the new pulseaudio

  2) Restart your computer, connect it to a bluetooth device (e.g. a
  headset or a speaker), play one or more videos either locally or
  online, and see if you can still reproduce the problem.

  [Regression Potential]
  Low, as the changes are upstream, and, if anything, it should also fix a 
memory leak.

  
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working 
properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Desktop-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]