Bug #1725714 “nautilus crashed with SIGABRT in g_assertion_messa...” : Bugs : nautilus package : Ubuntu

Revision history for this message

Greg Wilson (g-wilson) wrote on 2017-10-21:

#1

Dependencies.txt Edit (9.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (947 bytes, text/plain; charset="utf-8")
HookError_source_nautilus.txt Edit (792 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (138.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (95.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (791 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (7.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (14.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-21:

#2

StacktraceTop:
g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x561b5f99884b "../src/nautilus-files-view.c", line=line@entry=8353, func=func@entry=0x561b5f999ee8 <__func__.68147> "load_directory", message=message@entry=0x561b62145c50 "assertion failed: (NAUTILUS_IS_DIRECTORY (directory))") at ../../../../glib/gtestutils.c:2436
g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x561b5f99884b "../src/nautilus-files-view.c", line=line@entry=8353, func=func@entry=0x561b5f999ee8 <__func__.68147> "load_directory", expr=expr@entry=0x561b5f98c000 "NAUTILUS_IS_DIRECTORY (directory)") at ../../../../glib/gtestutils.c:2459
load_directory (view=0x561b6293a6b0, directory=directory@entry=0x0) at ../src/nautilus-files-view.c:8353
nautilus_files_view_set_location (view=0x561b6293a6b0, location=<optimized out>) at ../src/nautilus-files-view.c:3474
set_search_query_internal (files_view=0x561b6293a6b0, query=0x561b6267ed20, base_model=0x0) at ../src/nautilus-files-view.c:9290

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-21: Stacktrace.txt

#3

Stacktrace.txt Edit (26.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-21: StacktraceSource.txt

#4

StacktraceSource.txt Edit (16.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-21: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (36.2 KiB, text/plain)

Changed in nautilus (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2017-10-23: Re: nautilus crashed with SIGABRT in g_assertion_message()

#6

Download full text (20.7 KiB)

Responses

information_little.png This page is part of the Bug Squad’s KnowledgeBase - pages with information about how to triage bugs.
These standard responses along with other amazing scripts are also available as a Firefox extension in a PPA at:

https://launchpad.net/~gm-dev-launchpad/+archive/ppa

When you update one of these responses, you should also update the response used by the Firefox extension. These responses can be found in the bazaar branch lp:ubuntu-bugcontrol-tools in the file gm-xml-files/bugsquad-replies.xml. To check out a branch, use

bzr branch lp:ubuntu-bugcontrol-tools

Only members of bug-control can commit to this branch. But you can submit a merge proposal, Brian Murray will review/merge it (see this email message), and they can be used when replying to a bug report if merged.

Contents

    Not described well
    Missing Steps to Recreate Bug
    Missing Apport Information
    Package or domain specific questions
        Debugging Kernel General
        Debugging Sound Problems
        Debugging ACPI
        Debugging Removable Devices
        Debugging Printing problems
        Debugging Hardware Detection
        Debugging USB Storage
        Debugging Xorg in general
        Freeze during boot or shutdown screen
        Debugging Plymouth
        Debugging Live Installation
        Debugging A Distribution Upgrade
        Debugging GNOME Power Manager
        Debugging Network Manager
        Debugging Firefox
            Firefox crash report that fails retrace
        Debugging Samba
        Debugging Openldap
        Debugging ffmpeg (mostly libavcodec and libavformat bugs)
        Debugging SCIM related issues
    Incomplete bugs without a response from submitter
    Bugs without a package
    Bugs resolved after update or config change
    Needing testing in the development release
    Missing a crash report or having a .crash attachment
    A duplicate
    About an obsolete version of the software for reporter's release
    Missing a back trace
    Unusable stack trace after retracing
    Need valgrind log
    A bug that should be handled upstream
    Old untouched bugs
    Packages not provided by Ubuntu
    Fixed in Development release while still existing in a previous release
    Reported by someone not respecting the Code of Conduct
    A support request
    Not reported in English
    Suspected bad ISO download
    A suggestion for changing default applications or preferences
    About an incorrect translation
    Incomplete Package Request
    Triage Successful
    Triage Unsuccessful: Back to New/Incomplete Status
    Release has reached End of Life (EOL)
    Patch attachment not flagged as a patch
    Attachment incorrectly flagged as a patch
    Package installation failure
    Security Bugs
    Added Bugwatch
    Hanging Application or Daemon
    User Incorrectly Subscribing a team to a Bug
    Links

Not described well

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend....

Responses

information_little.png This page is part of the Bug Squad’s KnowledgeBase - pages with information about how to triage bugs.
These standard responses along with other amazing scripts are also available as a Firefox extension in a PPA at:

https://launchpad.net/~gm-dev-launchpad/+archive/ppa

When you update one of these responses, you should also update the response used by the Firefox extension. These responses can be found in the bazaar branch lp:ubuntu-bugcontrol-tools in the file gm-xml-files/bugsquad-replies.xml. To check out a branch, use

bzr branch lp:ubuntu-bugcontrol-tools

Only members of bug-control can commit to this branch. But you can submit a merge proposal, Brian Murray will review/merge it (see this email message), and they can be used when replying to a bug report if merged.

Contents

Not described well
    Missing Steps to Recreate Bug
    Missing Apport Information
    Package or domain specific questions
        Debugging Kernel General
        Debugging Sound Problems
        Debugging ACPI
        Debugging Removable Devices
        Debugging Printing problems
        Debugging Hardware Detection
        Debugging USB Storage
        Debugging Xorg in general
        Freeze during boot or shutdown screen
        Debugging Plymouth
        Debugging Live Installation
        Debugging A Distribution Upgrade
        Debugging GNOME Power Manager
        Debugging Network Manager
        Debugging Firefox
            Firefox crash report that fails retrace
        Debugging Samba
        Debugging Openldap
        Debugging ffmpeg (mostly libavcodec and libavformat bugs)
        Debugging SCIM related issues
    Incomplete bugs without a response from submitter
    Bugs without a package
    Bugs resolved after update or config change
    Needing testing in the development release
    Missing a crash report or having a .crash attachment
    A duplicate
    About an obsolete version of the software for reporter's release
    Missing a back trace
    Unusable stack trace after retracing
    Need valgrind log
    A bug that should be handled upstream
    Old untouched bugs
    Packages not provided by Ubuntu
    Fixed in Development release while still existing in a previous release
    Reported by someone not respecting the Code of Conduct
    A support request
    Not reported in English
    Suspected bad ISO download
    A suggestion for changing default applications or preferences
    About an incorrect translation
    Incomplete Package Request
    Triage Successful
    Triage Unsuccessful: Back to New/Incomplete Status
    Release has reached End of Life (EOL)
    Patch attachment not flagged as a patch
    Attachment incorrectly flagged as a patch
    Package installation failure
    Security Bugs
    Added Bugwatch
    Hanging Application or Daemon
    User Incorrectly Subscribing a team to a Bug
    Links

Not described well

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

Missing Steps to Recreate Bug

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Missing Apport Information

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Package or domain specific questions

The following packages or type of bugs require the specific debugging information:

Debugging Kernel General

Pleas also see the Ubuntu Kernel Teams specific responses for linux (Ubuntu) kernel bugs.

Debugging Sound Problems

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.

This information can be gathered for you automatically by using the following command only once:
apport-collect -p alsa-base BUGNUMBER

where BUGNUMBER is the number of the bug you've reported.

Debugging ACPI

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

Debugging Removable Devices

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please include the information requested at https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments.

Debugging Printing problems

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please include the information requested at https://wiki.ubuntu.com/DebuggingPrintingProblems as separate attachments.

Debugging Hardware Detection

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

Debugging USB Storage

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please include the information requested at https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments.

Debugging Xorg in general

Thank you for taking the time to report this bug and helping to make Ubuntu better. In order to attach necessary information for debugging this as an Xorg problem please run the following command only once:
apport-collect BUGNUMBER

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thanks in advance.

Freeze during boot or shutdown screen

Thanks for your bug report and for your contribution to Ubuntu. In order to determine if this issue is plymouth related, please boot your computer with plymouth disabled and then shutdown to see if you can reproduce the issue. To disable plymouth for a single boot, follow these steps:

1. Hold Right-Shift during Grub boot delay to access the boot menu.
2. Select your actual Ubuntu boot line and press "e" to edit it.
3. Select the "linux" line and at the end of the line, remove "splash" and "quiet".
5. Type "F10" to boot the custom boot line.

Debugging Plymouth

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please run the following command only once via a terminal:
apport-collect BUGNUMBER

which will attach necessary information for debugging this as a plymouth problem. Thanks in advance.

Debugging Live Installation

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your description didn't include enough information.

Please execute the following command 'ubuntu-bug ubiquity' as it will gather detailed information regarding your installation. Thanks in advance.

Debugging A Distribution Upgrade

DebuggingUpdateManager

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance.

Debugging GNOME Power Manager

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please run the following command only once in a terminal:
apport-collect BUGNUMBER

You might also want to take a look at the debugging instructions located at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager and submit any other logs related to your problem. Thanks in advance.

Apport will add the output of the upstream script "gnome-power-bugreport.sh" and "devkit-power --dump." "gnome-power-bugreport.sh" also includes the output of devkit-power --dump.

Debugging Network Manager

If a network-manager bug report is about not being able to connect the title or summary should be in the format: [CHIPSET] cannot connect to (ENCRYPT_METHOD) where the CHIPSET is the wireless driver used and ENCRYPT_METHOD is the encryption method used by your wireless network.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your bug report didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingNetworkManager. If you have trouble, do not hesitate to ask for more assistance. Thanks in advance.

Debugging Firefox

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs? Also, please answer these questions:
Is this crash reproducible? If so, which are the steps that lead to it?
Which flash package do you have installed?
Which Java package do you have installed?
Which Firefox extensions do you have installed?

This will greatly aid us in tracking down your problem.

Firefox crash report that fails retrace

Firefox bug triaging policy is to close (set to "invalid") crash reports from apport that fail retracing.

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report didn't yield the required information. Please go ahead and submit a new crash report if it crashes again with the latest available version of the package. Thanks in advance for your cooperation and understanding.

Debugging Samba

Please see the debugging Samba article for debugging and stock replies.

Debugging Openldap

Please see the debugging openldap article for debugging and stock replies.

Debugging ffmpeg (mostly libavcodec and libavformat bugs)

Thank you for taking the time to report this bug and helping to make Ubuntu better. You have reported a crash that actually happened in the libavcodec or libavformat library. In order to be able to actually fix this bug, we must be able to:

1. Reproduce it;
2. Check if it happens with the latest version; and
3. Understand where it actually crashes.

You can help with the first point by attaching an example file to this bug report. Please note that a proper attachment is preferred over a link to some remote site. Remote sites that are password protected or otherwise restricted (services like rapidshare.com) are absolutely not acceptable. If your file is too large, try to reproduce with the first few MB only. See http://ffmpeg.org/bugreports.html section "Submitting Sample Media" for guidelines.

Please also make sure that your file crashes with the commandline application ffplay from the ffmpeg package. If the crash does not happen with that tool, the bug does not belong to the ffmpeg package, but to some higher-level package like libxine1-ffmpeg or gstreamer0.10-ffmpeg (depending on what player has been used).

Debugging SCIM related issues

Thank you for taking the time to report this bug and helping to make Ubuntu better. In order to determine the cause of this issue, we would need some additional information.

Please post or attach the following:
1. the output of 'dpkg -l | grep scim'
2. the output of 'im-switch -l'
3. the files '/etc/scim/config', '/etc/scim/global' and '~/.scim/config'

Additionally, please answer the following questions:
1. Is this bug reproducible (always/sometimes/no)?
2. If you can reproduce the bug, what are the steps to do so?
3. Which desktop environment are you using? (Gnome/KDE3/KDE4)
4. If you remove '~/.scim/config', '~/.scim/global' and restart your X session by logging out and in again, does this bug still appear?
5. If you reinstall the 'scim', 'libscim8c2a', 'scim-bridge-agent' and 'scim-bridge-client-{gtk|qt4}' packages, followed by the procedure described in 4., does the bug still appear?

Incomplete bugs without a response from submitter

Some bugs are never responded to by the submitter (also called "original poster", or "OP"). These bugs will be automatically expired by Launchpad in 60 days, counted from the day it was set incomplete. There is no need to act on them (and, actually, changing the bug will restart the expiry period). Note that this applies for the Ubuntu project (i.e., those bug tasks that have "(Ubuntu)" in their name). Other projects may, or may not, have automatic incomplete bug expiration set.

Bugs without a package

Sometimes bugs will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a placeholder.

Warning /!\ If you use this response, you must assign a package. If you do not know what package to assign, please leave the bug alone, and ask for help.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in PKGNAME.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Bugs resolved after update or config change

Occasionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to 'Invalid' since we don't know the root cause. When closing the bug report it is a good idea to take an opportunity to let the reporter know how to manage bug statuses.

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Needing testing in the development release

A lot of bug reports need testing in the development release of Ubuntu. This is something that most anyone can do by downloading the Desktop ISO, booting from it and testing their particular bug.

Before using this, please check "rmadison <package>" to see if the package version has changed between when the bug was reported and the current development release. If it has not changed, there is no need to ask. If it has changed, check the changelog (via aptitude changelog $PKGNAME) to see if this issue has been specifically addressed.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

Missing a crash report or having a .crash attachment

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

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

Now 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'.

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. Thanks in advance for your cooperation and understanding.

A duplicate

When making a bug report a duplicate of another it is important to communicate to the reporter that any discussion regarding the bug should take place in the master bug. Keep in mind that NUMBER is a placeholder and should be the number of the master bug report.

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

About an obsolete version of the software for reporter's release

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, according to this report, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. Thanks in advance.

Missing a back trace

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Unusable stack trace after retracing

This is an alternative to the previous response, if there is a good chance that another retrace will work better (e.g. outdated package versions). Please close the bug as invalid with this comment:

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

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

Need valgrind log

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

A bug that should be handled upstream

If you are sure the reported bug is not caused by the packaging for Ubuntu, it should usually be sent upstream by someone affected by the bug. If appropriate, replace GNOME with the organization behind the software (see https://wiki.ubuntu.com/Bugs/Upstream/ for available organizations):

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

information type:

Private → Public

Sebastien Bacher (seb128) on 2017-10-31

summary:

nautilus crashed with SIGABRT in g_assertion_message()
+ (NAUTILUS_IS_DIRECTORY (directory))

Revision history for this message

Ads20000 (ads20000) wrote on 2018-03-14:

#7

See above, but I'm not able to reproduce this bug (I don't think the description is that poorly worded). Do you still have this on updated Ubuntu 17.10 Greg?

Changed in nautilus (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-05-13:

#8

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

Changed in nautilus (Ubuntu):
status:	Incomplete → Expired

Ubuntu
nautilus package

nautilus crashed with SIGABRT in g_assertion_message() (NAUTILUS_IS_DIRECTORY (directory))

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntunautilus package

nautilus crashed with SIGABRT in g_assertion_message() (NAUTILUS_IS_DIRECTORY (directory))

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
nautilus package