date:20190104

[Desktop-packages] [Bug 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted

2019-01-04 Thread Jeroen Evens

same issue
backup was working fine 2 weeks ago, now it started giving this error
Ubuntu 18.04

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

Title:
  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup package in Mandriva:
  New

Bug description:
  I've got my system set up with off-site backup over sftp. This works
  fine but the problem is that while deja-dup is gathering files and
  calculating the backup delta the connection to the server times out.
  This means that it's not available when deja-dup actually tries to
  push files to the server and results in this error message:

  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted (16)

  By sitting in the file manager and jumping between folders the
  connection can be kept alive but that's rather annoying and requires
  my presence. Would really like to see deja-dup actually trying to set
  up the connection again instead.

  
  Using:
  Manjaro 16.06.1
  deja-dup 34.2-1

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

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

[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive

2019-01-04 Thread Bryan Quigley

Should these removals happen first in Debian?  Otherwise we would need
to add all these to a blacklist IMU as well.

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

Title:
  Remove obsolete X11 drivers from the archive

Status in xf86-input-mtrack package in Ubuntu:
  New
Status in xf86-input-xwiimote package in Ubuntu:
  New
Status in xserver-xorg-input-aiptek package in Ubuntu:
  New
Status in xserver-xorg-input-elographics package in Ubuntu:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-keyboard package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New
Status in xserver-xorg-input-mutouch package in Ubuntu:
  New
Status in xserver-xorg-input-void package in Ubuntu:
  New
Status in xserver-xorg-video-ast package in Ubuntu:
  New
Status in xserver-xorg-video-geode package in Ubuntu:
  New
Status in xserver-xorg-video-mach64 package in Ubuntu:
  New
Status in xserver-xorg-video-neomagic package in Ubuntu:
  New
Status in xserver-xorg-video-r128 package in Ubuntu:
  New
Status in xserver-xorg-video-savage package in Ubuntu:
  New
Status in xserver-xorg-video-siliconmotion package in Ubuntu:
  New
Status in xserver-xorg-video-sisusb package in Ubuntu:
  New
Status in xserver-xorg-video-tdfx package in Ubuntu:
  New
Status in xserver-xorg-video-trident package in Ubuntu:
  New

Bug description:
  xserver-xorg-video-all has not depended on these drivers for quite
  some time now, meaning that installation images didn't have them
  either nor installed them on the system. Now would be the time to drop
  them from the archive before next LTS & HWE-18.04 stack and in
  preparation for xserver 1.20.

  Some rationale in detail for future reference:
  input:
  -aiptek: no upstream release in 7 years
  -elographics: no upstream release in 6 years
  -evdev: replaced by -libinput (not entirely, see comment #1)
  -keyboard: replaced by -libinput
  -mtrack: no upstream release in 3 years, should be replaceable by -libinput 
by now
  -mouse: replaced by -libinput
  -mutouch: no upstream release in 7 years
  -void: xserver can start without an input driver these days
  -xwiimote: no upstream release in 5 years
  video:
  -ast: no upstream release in 3 years, no KMS support
  -geode: i386 only, no kernel support since moving to i586 (or i686?)
  -mach64: no KMS support
  -neomagic: no upstream release in 3 years, no KMS support
  -r128: no KMS support
  -savage: no KMS support
  -siliconmotion: no KMS suppport
  -sisusb: no KMS support
  -tdfx: no KMS support
  -trident: no KMS support

  Fedora dropped drivers without KMS (kernel modesetting) support five years 
ago:
  https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html

  one exception to this is -openchrome, which we'll keep since it has
  some users and might even get KMS support before next LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions

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

[Desktop-packages] [Bug 1810496] [NEW] 1:26.1+1-3 FTBFS in disco on ppc64el (test fail)

2019-01-04 Thread Rik Mills

Public bug reported:

Version: 1:26.1+1-3
Release: Disco 19.04

FTBFS on ppc64el with failing tests.

SUMMARY OF TEST RESULTS
---
Files examined: 185
Ran 2563 tests, 2520 results as expected, 2 unexpected, 41 skipped
2 files contained unexpected results:
  src/lcms-tests.log
  lisp/eshell/em-ls-tests.log

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

** Summary changed:

- 1:26.1+1-3 FTBFS in disco on ppc64el
+ 1:26.1+1-3 FTBFS in disco on ppc64el (test fail)

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

Title:
  1:26.1+1-3 FTBFS in disco on ppc64el (test fail)

Status in emacs package in Ubuntu:
  New

Bug description:
  Version: 1:26.1+1-3
  Release: Disco 19.04

  FTBFS on ppc64el with failing tests.

  SUMMARY OF TEST RESULTS
  ---
  Files examined: 185
  Ran 2563 tests, 2520 results as expected, 2 unexpected, 41 skipped
  2 files contained unexpected results:
src/lcms-tests.log
lisp/eshell/em-ls-tests.log

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

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

[Desktop-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2019-01-04 Thread bitinerant

Same issue here, Ubuntu 18.04. We're having a hard time finding a way to
print these documents. I am attaching a screenshot.


** Attachment added: "Evince (left) and Print Preview (right)"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+attachment/5226856/+files/Evince%20%28left%29%20and%20Print%20Preview%20%28right%29.png

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

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

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

[Desktop-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2019-01-04 Thread bitinerant

And here is the 1-page PDF used in the above screenshot.

** Attachment added: "sample 'bad' PDF"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

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

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

[Desktop-packages] [Bug 1801496] Re: Printing job in 16.04 is slower than in 14.04

2019-01-04 Thread William.Yeung

Dear Till,
Happy new year!
I'am very sorry to bother you again.

We are still working hard to looking for cause why Ubuntu 16.04 printing
performance slowdown.

Here are some information that may can be helpful for the investigation:

We figure out that "foomatic-rip" is the key object which slowdown
printing performance.

Satistics the time of "foomatic-rip" use by the method of counting the
time from “[Job 691] Started filter /usr/lib/cups/filter/foomatic-rip”
to “ [Job 691] PID 11751 (/usr/lib/cups/filter/foomatic-rip) exited with
no errors.”

Attach file introduction:
--
CUPS_Log_14.04_16.04.xlsx: Log Satistics
--

Best Regards,

** Attachment added: "CUPS_Log_14.04_16.04.zip"

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801496/+attachment/5226865/+files/CUPS_Log_14.04_16.04.zip

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

Title:
Printing job in 16.04 is slower than in 14.04

Status in cups package in Ubuntu:
Incomplete

Bug description:
Ubuntu 16.04LTS
OS Version： 16.04.5
CUPS Version： 2.1.3
Ghostscript Version： 9.25 （2018-09-13）

Printing job in 16.04 is slower than in 14.04

We(RICOH printer driver developer) are report a problem from our printer
users:
I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds).

But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I
print the same file with the same driver is slow(326 Seconds).

I figure out that all the print jobs is much slower on Ubuntu 16.04.

I view the "CUPS Error Log", it shows that there are three points
which maybe the reasons that makes the print job slowly.

FIRST:

By counting the time from "Starting renderer" to "renderer exited with status
0", we figure out that 16.04 spend more time than 14.04 on "renderer" process.
So we assuming that："renderer" is one of the key process that makes the print
job slowly.

"Starting renderer with command: \"printf \'\\033%%-12345X@PJL
JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\ @PJL
EOJ\\012\\033%%-12345X\'\""
.
renderer exited with status 0"

SECOND:

On 16.04, a print job outputs lots of logs as below:
"[Job xxx] Removing document files."

This step(“Removing document files”)does not exsit on 14.04.

The phenomenon that print jobs slower in 16.04 is more obvious when printing
many jobs in the same time.

THIRD
We tried drivers form other company(HP,Brother…), the printings also slow
down in Ubuntu 16.04 than 14.04.

Our question is:
1. Do you have any plan to improve the performance of printing on Ubuntu
16.04?
2. Do you have any workaround before this problems fixed?

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

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

[Desktop-packages] [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

2019-01-04 Thread Linaori

Any update on this issue? It's 2 months later and my fresh ubuntu 18.10
installation is failing on this. Whenever I close the app on a specific
page, it never wants to go back. Imagine a new user using Ubuntu for the
first time, this leaves a _very_ bad impression

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

Title:
  [SRU] Click on the back icon in gnome-software doesn't work

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Cosmic:
  Fix Released

Bug description:
  [Test Case]

  1. Open gnome-software
  2. Press Ctrl+F and type "firefox" or any string that will return results
  3. Click any result in the list (snap package or deb, already installed or 
not, it doesn't matter)
  4. Observe that a new page is open showing details about the application
  5. Close gnome-software
  6. Open gnome-software again
  7. Observe that the application is open on the last open page (details view 
about the application)
  8. Click the back button (top-left corner)

  Expected result: the application goes back to the list of search
  results (or perhaps to the home screen)

  Current result: nothing happens

  Please note that the upstream fix reverts a new behaviour and as a
  result, when opening again gnome-software at step 6, the application
  opens on the home screen instead of resuming the last open page. This
  is consistent with how gnome-software behaves in bionic. So after
  applying the patch, steps 7 and 8 can be folded into one single step:
  "Observe that the application is open on the home screen".

  
  [Regression Potential]

  Low. This is a cherry-pick of a self-contained trivial upstream commit that 
is already released in gnome-software 3.30.3 
(https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774).
  As noted above, it does change the behaviour of re-opening the application 
after closing it, but it reverts it to the behaviour it had in bionic, so I 
don't think it should be considered a regression.

  Re-opening the application after closing it in a number of different
  situations should be thoroughly exercised to make sure that this
  doesn't introduce any functional regression.

  
  [Original Description]

  Searched for Chromium, installed Chromium (snap version), clicked Launched 
and used chromium.
  Went back to gnome-software and clicked the back button. Nothing happened. 
Restarted gnome-software and clicked the back button. Nothing happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu3 [modified: 
usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini]
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 11:22:16 2018
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu3
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181016)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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

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

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

2019-01-04 Thread Launchpad Bug Tracker

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

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

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

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Crashed when opening the notifications

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 18:10:51 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1362 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_cancellable_make_pollfd () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_socket_condition_timed_wait () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_input_stream_read () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (14 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1630176] Re: Ubuntu version reported wrong in system settings

2019-01-04 Thread ruru

I am experienceing this on 18.10 (unity-control-center reports 18.04)

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

Title:
  Ubuntu version reported wrong in system settings

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

Bug description:
  https://help.ubuntu.com/community/CheckingYourUbuntuVersion describes
  two ways of getting your current Ubuntu version: via system settings,
  and via terminal. For me, those two methods give me a different
  version (14.04 vs 16.04, see attached screenshot). I upgraded my pre-
  installed trusty to xenial, so the version printed on terminal is
  correct. That means that the system settings displays the wrong
  version.

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

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

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

2019-01-04 Thread Launchpad Bug Tracker

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

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

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

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Crash when I log in after resume from suspend.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  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.10-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 25 08:02:52 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1409 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_cancellable_make_pollfd () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_socket_condition_timed_wait () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_input_stream_read () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (61 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

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

2019-01-04 Thread Benjamin Schmid

@vanvugt Seeing this VERY regularly in cosmic, too. Just came back here
to re-check the status of this long-term annoying issue.

The fact is, that gnome shell provides me a VERY poor UX experience:

Logged out for the session more than 10mins? Type your password and go
get take a coffee, because it literally takes 1-2 minutes until the
session finally crashes and restarts. Before my PC it literally
unusable. Sometimes I also switch to the login screen and re-login into
my running session to somehow provoke the crash to get it usable.

Ah – and by the way: On some occassions lockscreen does not work and
expose the clickable (!) left sidebar. In this case I only can unlock
via the login-screen way to crash the session.

Also commonly in normal operation the left sidebar looks strangely
sized. Then I need to type "r" to restart the shell to resume normal
operation.

Feels really like an old, nearly dying device …

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

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

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

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

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

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

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

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

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

--

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

2019-01-04 Thread Benjamin Schmid

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

Saw this new stacktrace at g_cancellable_make_pollfd() right now, too.
For me this occurred while I was hammering quickly in the lockscreen
until it chocked, locked and finally crashed.

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Crash when I log in after resume from suspend.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  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.10-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 25 08:02:52 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1409 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_cancellable_make_pollfd () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_socket_condition_timed_wait () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_input_stream_read () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (61 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.

2019-01-04 Thread Vladyslav Drok

Hey gouri, here is the info you requested:

automatically lock the session - when the screensaver is activated
delay locking after screensaver for - 5 seconds
lock screen when system is going to sleep - checked

marked the bug as affecting me

as I said I'm using archlinux, it's just the place I found with someone
hitting this issue, here are some package and kernel versions if this is
of any help:

local/xfdesktop 4.12.4-2 (xfce4)
A desktop manager for Xfce
local/xfwm4 4.12.5-1 (xfce4)
Xfce window manager
local/xfce4-session 4.12.1-8 (xfce4)
A session manager for Xfce
local/light-locker 1.8.0-2
A simple session locker for LightDM
local/lightdm 1:1.28.0-1
A lightweight display manager
local/lightdm-gtk-greeter 1:2.0.6-1
GTK+ greeter for LightDM
local/lightdm-gtk-greeter-settings 1.2.2-3
Settings editor for the LightDM GTK+ Greeter
local/gtk-xfce-engine 2.10.1-2 (xfce4)
Xfce Gtk+-2.0 engine and themes
local/gtk2 2.24.32-1
GObject-based multi-platform GUI toolkit (legacy)
local/gtk3 3.24.1+8+g220f77d8c1-1
GObject-based multi-platform GUI toolkit

Linux carbon 4.19.8-arch1-1-ARCH #1 SMP PREEMPT Sat Dec 8 13:49:11 UTC
2018 x86_64 GNU/Linux

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

Title:
  Unlocking existing session often requires several attempts.

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  # Context

  * Computer with several X sessions opened.
  * Users switching from one opened session to another.
  * Lightdm opens new greeter, wait for typing password.
  * User types password.
  * Password is accepted.
  * System closes the current greeter (screen gets black for an instant).

  # Expected

  * User gets back to their already opened session.

  # Observed

  * System immediately opens another greeter.
  * User has to type password again.

  # Reproducible

  * Not always. At times, often, at other times, rare.

  # Additional information

  Users switch session via 
  dm-tool switch-to-user $OTHERUSER
  but I guess bug appears with other means (like menu item like "lock screen", 
etc).

  # Information requested

  lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  LC_ALL=C apt-cache policy lightdm

  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:14:52 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2018-05-25 (18 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.lightdm: [modified]
  mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830

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

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

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

2019-01-04 Thread amano

Benjamin, out of interest: Do you see the crash with both sessions? X
and waylan?

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

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

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

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

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

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

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

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

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

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

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

2019-01-04 Thread amano

Wayland of course. Just suggesting that switching to Wayland might fix
your problem.

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

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

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

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

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

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

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

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

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

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

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

2019-01-04 Thread Kyle Weber

Mine does EVERYTHING EXACTLY as you just mentioned.

Sent from my iPhone

> On Jan 4, 2019, at 3:25 AM, Benjamin Schmid <1748...@bugs.launchpad.net> 
> wrote:
> 
> @vanvugt Seeing this VERY regularly in cosmic, too. Just came back here
> to re-check the status of this long-term annoying issue.
> 
> The fact is, that gnome shell provides me a VERY poor UX experience:
> 
> Logged out for the session more than 10mins? Type your password and go
> get take a coffee, because it literally takes 1-2 minutes until the
> session finally crashes and restarts. Before my PC it literally
> unusable. Sometimes I also switch to the login screen and re-login into
> my running session to somehow provoke the crash to get it usable.
> 
> Ah – and by the way: On some occassions lockscreen does not work and
> expose the clickable (!) left sidebar. In this case I only can unlock
> via the login-screen way to crash the session.
> 
> Also commonly in normal operation the left sidebar looks strangely
> sized. Then I need to type "r" to restart the shell to resume normal
> operation.
> 
> Feels really like an old, nearly dying device …
> 
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (1755163).
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Invalid
> Status in mutter package in Ubuntu:
>  Fix Released
> Status in gnome-shell source package in Bionic:
>  Invalid
> Status in mutter source package in Bionic:
>  Fix Released
> 
> Bug description:
>  [Impact]
> 
>  * Xwayland is failing frequently (not crashing), which triggers a
>  crash in gnome-shell because gnome-shell doesn't know how to survive
>  after Xwayland has reset itself.
> 
>  * The frequent gnome-shell crashes create frequent problem reports and
>  annoying dialogs for users, after they log in to an apparently working
>  gnome-shell.
> 
>  * This affects Xorg sessions too, because the gdm login screen itself
>  is a Wayland session. And Xorg users will see the problem dialog after
>  they have logged into a Xorg session.
> 
>  * The fix simply converts the crash into a silent exit (as decided by
>  Gnome upstream). This avoids the mountain of crash reports and
>  annoying error dialogs at least. It does not fix the root causes that
>  remain in Xwayland, but this is considered acceptable because there
>  really isn't a bug in gnome-shell here other than it doesn't know how
>  to survive without a connection to Xwayland.
> 
>  * For users of Xorg sessions, like bionic default, this is a full fix
>  as Xorg users will never get an Xwayland instance after logging in.
>  And hence the Xwayland bugs are irrelevant.
> 
>  [Test Case]
> 
>  * Just install bionic, use it lightly and reboot a few times.
> 
>  * Observe crash files are left in /var/crash and problem report
>  dialogs after logging in.
> 
>  [Regression Potential]
> 
>  Medium. The fix does not really change the structure of the existing
>  error handling, only changes it from a core dump into a silent exit.
>  For Xorg users this should be invisible as the affected login screen
>  restarts automatically.
> 
>  [Other Info]
> 
>  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
> 1748450 and bug 1556601. All three should be considered the same crash for 
> the sake of this SRU. Just don't mark them as duplicates of each other
>  because they are all still collecting duplicates of their own.
> 
>  -
> 
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/l

[Desktop-packages] [Bug 887331] Re: file-roller cannot open filetypes with derived mimetypes (e.g. epub and ods files)

2019-01-04 Thread Nicolas Göddel

This bug is annoying. Please fix it. I am using 18.04 LTS and often need
to open ODT files.

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

Title:
  file-roller cannot open filetypes with derived mimetypes (e.g. epub
  and ods files)

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Given three files A, B and C, where A is a zip file (a.zip), B is an
  ePub file (b.epub) and C is an ODF Spreadsheet file (c.ods) ...

  All files have "Open With > Archive Manager" as a menu option in
  nautilus.

  This is likely due to the shared-mime-info database having the ePub
  and ODS mimetypes as .

  File A will open successfully, while files B and C report "Could not
  open 'A'" / "Archive type not supported". However, renaming B and C so
  they have a .zip extension will cause the files to be opened
  correctly.

  This is likely due to file-roller checking the filetype to load by
  extension, not magic. This is indeed the case as giving a text file a
  .zip extension causes file-roller to report "An error occurred while
  loading the archive" (End-of-central-directory signature not found.
  Either this file is not a zipfile, or it constitutes one disk of a
  multi-part archive.  In the latter case the central directory and
  zipfile comment will be found on the last disk(s) of this archive.)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: file-roller 3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: 5434425585a31b50d9fa7c3153a37fe1
  CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
  Date: Mon Nov  7 21:12:54 2011
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: file-roller
  UpgradeStatus: Upgraded to oneiric on 2011-09-24 (44 days ago)

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

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

1 2 >

1 - 100 of 158 matches

Mail list logo