public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5906] New: frysk-gnome ui doesn't start up
Date: Mon, 10 Mar 2008 15:04:00 -0000 [thread overview]
Message-ID: <20080310150315.5906.mark@klomp.org> (raw)
Fails on in both the frysk-gnome rpm on fedora 8 and git trunk.
> Exception in thread "main" java.lang.NullPointerException
> at frysk.gui.Gui.setupCoreLogging(frysk)
> at frysk.gui.Gui.gui(frysk)
> at frysk.bindir.frysk.main(frysk)
Andrew, could you take a look at how this needs to be rewritten to use
your new rsl framework? It was broken by the following git commit
b69a9d32535ea10a98fb4f67ef0778073654ea58 (reverting that makes the gui
start up again) which unfortunately seems to have made it into the rpm.
The problem is that the "frysk" logger is only added to the LogManager
in the static initializer of the EventLogger class, which got moved
around in that commit, and now it seems to never be instantiated, so the
logger is never added which causes the getLogger call in
Gui.setupCoreLogging() to return null.
--
Summary: frysk-gnome ui doesn't start up
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: mark at klomp dot org
CC: cagney at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=5906
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-03-10 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 15:04 mark at klomp dot org [this message]
2008-03-11 1:07 ` [Bug general/5906] " cagney at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080310150315.5906.mark@klomp.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).