Bug 1015847

Thank you for the bug report. Unfortunately, we need more information to properly fix this problem because this behaviour could have several reasons. If you have time and can still reproduce the bug, please read https://fedoraproject.org/wiki/Bugs_and_feature_requests?rd=BugsAndFeatureRequests#Graphical_User_Interfaces and add a screenshot or a video along those lines to this bug report. Thank you.

thank you jakub by answer me , here is the information about the problem , i include the video and the journal log. i hope that this be helpful
oh excuse my english i'm from chile and excuse my report i newbie in fedora 

Description of problem:

1.- report button isn't working when  this is clicked
2.- this error appear with reported bugs
3.- this error appear with no reported bugs


Step to reproduce:

1.- report button isn't working
2.- if i run gnome-abrt as root , abrt work fine

Additional info:

here is the video with the error 
http://youtu.be/acLlZAPTZLA

journalctl -l | grep -i gnome-abrt

oct 07 20:33:32 localhost.localdomain polkitd[434]: Operator of unix-session:1 successfully authenticated as unix-user:psyqueatoog to gain TEMPORARY authorization for action org.freedesktop.problems.getall for system-bus-name::1.91 [/usr/bin/python /usr/bin/gnome-abrt] (owned by unix-user:psyqueatoog)
[root@localhost psyqueatoog]#

Thank you for the reply. The video is excellent! But I am still not sure what is the root cause of this bug. Could you please run "gnome-abrt -v" as a non-root user, select a problematic crash, click Report button and submit the output here.

thank you for the reply jakub i made your instruction in this steps as non root

1.- gnome-abrt -v
2.- launch abrt correctly
3.- i  select  unetbootin problem crash ( no reported and as example)
3.- the bug is report with all files ( backtrace,cgroup, environ ... ) here : https://bugzilla.redhat.com/show_bug.cgi?id=1017335

the video with the instruction is here :
http://youtu.be/Jhx6E2wlsN4

and the terminal output is :
this output appear when i click the bugzilla link 
(process:2606): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

this output appear when i click other error
DEBUG:root:[Errno 10] No hay ningún proceso hijo
DEBUG:root:DBusProblemSource : Notify
DEBUG:root:DirectoryProblemSource : Notify
DEBUG:root:MultipleSources : Notify
DEBUG:root:DBusProblemSource : Notify

i hope the info be helpfull

Hi Carlos, thank you for the logs. It seems that Report button worked fine for the unetbootin crash. If you have time and still want to help us, please re-run this scenario but this time select a crash for which Report button does not work.

The problem with Glib-CRITICAL warning has already been reported and it is a bug in Gtk3. Hence, I am sorry but we cannot do much about that. Anyway it seems that the Bugzilla bug link was opened correctly, thus everything is OK.

Hi jakub thank for the patience , again repeated the error with report button this is not working 

step to reproduce:

1.- gnome-abrt -v
2.- I  choose an option in where the report button is not  working
3.- and the terminal output is here:

the video with the error:
http://youtu.be/GT6vwDYrHJ4

terminal output:
Can't open file '/var/tmp/abrt/ccpp-2013-10-10-04:22:32-1983/type': Permiso denegado
Can't open file '/var/tmp/abrt/ccpp-2013-10-10-04:22:32-1983/type': Permiso denegado
Can't open file '/var/tmp/abrt/ccpp-2013-10-10-04:22:32-1983/type': Permiso denegado

'/var/tmp/abrt/ccpp-2013-10-10-04:22:32-1983' is not a problem directory
DEBUG:root:[Errno 10] No hay ningún proceso hijo
DEBUG:root:DBusProblemSource : Notify
DEBUG:root:DirectoryProblemSource : Notify
DEBUG:root:MultipleSources : Notify
DEBUG:root:DBusProblemSource : Notify
DEBUG:root:[Errno 10] No hay ningún proceso hijo
DEBUG:root:DBusProblemSource : Notify
DEBUG:root:DirectoryProblemSource : Notify
DEBUG:root:MultipleSources : Notify
DEBUG:root:DBusProblemSource : Notify

Thank you for the quick reply. Please run the following command as root user and submit the output here:

$ ls -al /var/tmp/abrt/ccpp-2013-10-10-04:22:32-1983

And it would also be good to run the same command for the option where Report button fails. You can easily get the directory path by right mouse click on the option in the list and select "Copy problem's id to Clipboard".

Then go to terminal and type:

$ ls -al <Shif+Ins or "righ click and Paste">

terminal output:

[root@localhost psyqueatoog]# ls -al /var/tmp/abrt/ccpp-2013-10-10-04:22:32-1983
total 27684
drwxrwx---. 2 psyqueatoog abrt     4096 oct 10 07:27 .
drwxr-xr-x. 6 abrt        abrt     4096 oct 10 07:21 ..
-rw-rw----. 1 psyqueatoog abrt        5 oct 10 04:22 abrt_version
-rw-rw----. 1 psyqueatoog abrt        4 oct 10 04:22 analyzer
-rw-rw----. 1 psyqueatoog abrt        6 oct 10 04:22 architecture
-rw-rw----. 1 psyqueatoog abrt      159 oct 10 04:22 cgroup
-rw-rw----. 1 psyqueatoog abrt       32 oct 10 04:22 cmdline
-rw-rw----. 1 psyqueatoog abrt       16 oct 10 04:22 component
-rw-rw----. 1 psyqueatoog abrt     3768 oct 10 05:15 core_backtrace
-rw-rw----. 1 psyqueatoog abrt 79876096 oct 10 04:22 coredump
-rw-rw----. 1 psyqueatoog abrt        1 oct 10 04:22 count
-rw-rw----. 1 psyqueatoog abrt    17477 oct 10 04:22 dso_list
-rw-rw----. 1 psyqueatoog abrt     1320 oct 10 04:22 environ
-rw-rw----. 1 psyqueatoog abrt       18 oct 10 04:22 executable
-rw-rw----. 1 psyqueatoog abrt       82 oct 10 04:22 exploitable
-rw-rw----. 1 psyqueatoog abrt       21 oct 10 04:22 hostname
-rw-rw----. 1 psyqueatoog abrt       22 oct 10 04:22 kernel
-rw-rw----. 1 psyqueatoog abrt       10 oct 10 04:22 last_occurrence
-rw-rw----. 1 psyqueatoog abrt     1323 oct 10 04:22 limits
-rw-rw----. 1 psyqueatoog abrt    75899 oct 10 04:22 maps
-rw-rw----. 1 psyqueatoog abrt     1389 oct 10 04:22 open_fds
-rw-rw----. 1 psyqueatoog abrt      281 oct 10 04:22 os_info
-rw-rw----. 1 psyqueatoog abrt       24 oct 10 04:22 os_release
-rw-rw----. 1 psyqueatoog abrt       30 oct 10 04:22 package
-rw-rw----. 1 psyqueatoog abrt        4 oct 10 04:22 pid
-rw-rw----. 1 psyqueatoog abrt        6 oct 10 04:22 pkg_arch
-rw-rw----. 1 psyqueatoog abrt        1 oct 10 04:22 pkg_epoch
-rw-rw----. 1 psyqueatoog abrt       16 oct 10 04:22 pkg_name
-rw-rw----. 1 psyqueatoog abrt        6 oct 10 04:22 pkg_release
-rw-rw----. 1 psyqueatoog abrt        6 oct 10 04:22 pkg_version
-rw-rw----. 1 psyqueatoog abrt      933 oct 10 04:22 proc_pid_status
-rw-rw----. 1 psyqueatoog abrt       17 oct 10 04:22 pwd
-rw-rw----. 1 psyqueatoog abrt       60 oct 10 04:22 reason
-rw-rw----. 1 psyqueatoog abrt        4 oct 10 04:22 runlevel
-rw-rw----. 1 psyqueatoog abrt       10 oct 10 04:22 time
-rw-r-----. 1 root        root        4 oct 10 05:15 type
-rw-rw----. 1 psyqueatoog abrt        4 oct 10 04:22 uid
-rw-rw----. 1 psyqueatoog abrt       12 oct 10 04:22 username
-rw-rw----. 1 psyqueatoog abrt       40 oct 10 04:22 uuid


soory but i don stand much the second instruction , but i run 

[root@localhost psyqueatoog]# ls -al /usr/bin/gnome-tweak-tool
-rwxr-xr-x. 1 root root 3044 sep 25 05:19 /usr/bin/gnome-tweak-tool
[root@localhost psyqueatoog]#

(In reply to Carlos Morel-Riquelme from comment #8)
Excellent!

Could you please run:

$ chown psyqueatoog:abrt /var/tmp/abrt/ccpp-2013-10-10-04:22:32-1983/type

as root user and retest Report button again.

thank for the reply jakub

i run as root:

[root@localhost psyqueatoog]# chown psyqueatoog:abrt /var/tmp/abrt/ccpp-2013-10-10-04:22:32-1983/type
[root@localhost psyqueatoog]# 

no terminal output:

later as normal user run:

gnome-abrt -v :

the first time fedora require the password the root pass ( fine )
and later click the report button and work fine
later the root password is not require

here the video :
http://youtu.be/v5iGpSMTENw

Thank you for your great cooperation! Now, I am going to write a patch which will correct access rights for all crash directories and their files.

(In reply to Jakub Filak from comment #11)
> Thank you for your great cooperation! Now, I am going to write a patch which
> will correct access rights for all crash directories and their files.

thank you jakub for the patience , and i will send report error :)

Fixed upstream:

commit b55e961e567b37fb1e28cda0ef85ed5dda820b70
Author: Jakub Filak <jfilak>
Date:   Fri Oct 11 13:20:56 2013 +0200

    spec: fix file access rights for type and core_bactrace

gnome-abrt-0.3.3-1.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20

Package gnome-abrt-0.3.3-2.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.3-2.fc20 abrt-2.1.9-1.fc20 libreport-2.1.9-1.fc20 satyr-0.11-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-2.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20
then log in and leave karma (feedback).

gnome-abrt-0.3.3-2.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.