Bug 1931123 - [abrt] nextcloud-client: _dbus_warn_check_failed(): nextcloud killed by SIGABRT
Summary: [abrt] nextcloud-client: _dbus_warn_check_failed(): nextcloud killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nextcloud-client
Version: 33
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f0cf5e183167a8db82ca63b4adb...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-20 20:00 UTC by Francisco de la Peña
Modified: 2021-11-30 19:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 19:06:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (57.32 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: core_backtrace (14.47 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: cpuinfo (2.59 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: dso_list (10.58 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: environ (1.40 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: limits (1.29 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: maps (63.98 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: mountinfo (2.62 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: open_fds (549 bytes, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: proc_pid_status (1.34 KB, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details
File: var_log_messages (800 bytes, text/plain)
2021-02-20 20:00 UTC, Francisco de la Peña
no flags Details

Description Francisco de la Peña 2021-02-20 20:00:43 UTC
Version-Release number of selected component:
nextcloud-client-3.1.1-1.fc33

Additional info:
reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app-gnome-com.nextcloud.desktopclient.nextcloud-3901.scope
cmdline:        /usr/bin/nextcloud --background
crash_function: _dbus_warn_check_failed
executable:     /usr/bin/nextcloud
journald_cursor: s=3100642413764ffb9559e7d823ce9343;i=1a8000;b=fbe00ceb48e74405971b1825bf0c921a;m=76ee94c;t=5bbc903b247ce;x=8b994cdbc3a1c99d
kernel:         5.10.16-200.fc33.x86_64
rootdir:        /
runlevel:       unknown
type:           CCpp
uid:            1000

Comment 1 Francisco de la Peña 2021-02-20 20:00:46 UTC
Created attachment 1758450 [details]
File: backtrace

Comment 2 Francisco de la Peña 2021-02-20 20:00:47 UTC
Created attachment 1758451 [details]
File: core_backtrace

Comment 3 Francisco de la Peña 2021-02-20 20:00:49 UTC
Created attachment 1758452 [details]
File: cpuinfo

Comment 4 Francisco de la Peña 2021-02-20 20:00:50 UTC
Created attachment 1758453 [details]
File: dso_list

Comment 5 Francisco de la Peña 2021-02-20 20:00:51 UTC
Created attachment 1758454 [details]
File: environ

Comment 6 Francisco de la Peña 2021-02-20 20:00:52 UTC
Created attachment 1758455 [details]
File: limits

Comment 7 Francisco de la Peña 2021-02-20 20:00:53 UTC
Created attachment 1758456 [details]
File: maps

Comment 8 Francisco de la Peña 2021-02-20 20:00:54 UTC
Created attachment 1758457 [details]
File: mountinfo

Comment 9 Francisco de la Peña 2021-02-20 20:00:55 UTC
Created attachment 1758458 [details]
File: open_fds

Comment 10 Francisco de la Peña 2021-02-20 20:00:56 UTC
Created attachment 1758459 [details]
File: proc_pid_status

Comment 11 Francisco de la Peña 2021-02-20 20:00:57 UTC
Created attachment 1758460 [details]
File: var_log_messages

Comment 12 Fedora Admin user for bugzilla script actions 2021-08-20 00:07:51 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 13 Ben Cotton 2021-11-04 13:46:57 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Ben Cotton 2021-11-04 14:16:27 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Ben Cotton 2021-11-04 15:14:04 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Ben Cotton 2021-11-30 19:06:05 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.