After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757707 - Error 500 on reporting a bug
Error 500 on reporting a bug
Status: RESOLVED DUPLICATE of bug 744491
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-11-06 19:44 UTC by bob_hepple
Modified: 2015-11-09 11:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description bob_hepple 2015-11-06 19:44:52 UTC 
Error 500 on reporting a bug
Comment 1 André Klapper 2015-11-06 22:58:02 UTC 
Thanks but not enough info to reproduce
Comment 2 bob_hepple 2015-11-07 02:01:47 UTC 
I was doubtful that submitting this one would work aat all having failed for me repeatedly as below ( and it was 4am ) so here are more details - it's strange that I can submit bugs for bugzilla itself but not for gtk+!!!!

https://bugzilla.gnome.org/enter_bug.cgi?product=gtk%2B
Product=gtk+
Component: Widget: GtkTreeView
Version: 3.16x
Severity: Major
OS: Linux
Summary: gtk_tree_store_reorder  is not callable from python
Description: This is in the most recent gtk3 for fedora 22: gtk3-3.16.7-1.fc22.x86_64

Running this from python:

from gi.repository import Gtk
tree_store = Gtk.TreeStore()
tree_store.reorder

... results in the error:

Traceback (most recent call last):

+ Trace 235684

  • File "e", line 3 in <module> 
    list_store.reorder
AttributeError: 'TreeStore' object has no attribute 'reorder' 


The gtk2 equivalent works fine:

import gtk
import gobject

tree_store = gtk.TreeStore(gobject.TYPE_STRING)
tree_store.reorder




Response is:
https://static.gnome.org/error-500/500.html

OOPS...You have just hit an error 500, all the ways to report the issue are available here, but before doing so please check the status page for possible planned outages or maintenances.
Comment 3 bob_hepple 2015-11-07 02:02:55 UTC 
BTW, the status page said 'all good'
Comment 4 bob_hepple 2015-11-09 03:30:19 UTC 
I managed to post my bug today using chrome on fedora-21

Looks like it may be a chrome on f-22 problem????
Comment 5 André Klapper 2015-11-09 11:56:34 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 744491 ***