Theme HighContrast seems to work
See:
https://bugzilla.novell.com/post_bug.cgi
bug 867253
On Thu, Mar 6, 2014 at 2:30 PM, Bill Nottingham wrote:
> Christian Stimming (christ...@cstimming.de) said:
> > Am Donnerstag, 6. März 2014, 12:33:58 schrieb John Ralls:
> > > On Mar 6, 2014, at 12:23 PM,
Bug 867253 submitted to opensuse
https://bugzilla.novell.com/post_bug.cgi
On Thu, Mar 6, 2014 at 12:33 PM, John Ralls wrote:
>
> On Mar 6, 2014, at 12:23 PM, Ted Creedon wrote:
>
> > Looks like the GTK/Oxygen theme is broken, changed thmres & seems to
> work OK
> >
> > How do i report this,
Christian Stimming (christ...@cstimming.de) said:
> Am Donnerstag, 6. März 2014, 12:33:58 schrieb John Ralls:
> > On Mar 6, 2014, at 12:23 PM, Ted Creedon wrote:
> > > Looks like the GTK/Oxygen theme is broken, changed thmres & seems to work
> > > OK
> > >
> > > How do i report this, & to who?
>
Am Donnerstag, 6. März 2014, 12:33:58 schrieb John Ralls:
> On Mar 6, 2014, at 12:23 PM, Ted Creedon wrote:
> > Looks like the GTK/Oxygen theme is broken, changed thmres & seems to work
> > OK
> >
> > How do i report this, & to who?
>
> I’d start with SuSE and let them figure out if it’s an upst
On Mar 6, 2014, at 12:23 PM, Ted Creedon wrote:
> Looks like the GTK/Oxygen theme is broken, changed thmres & seems to work OK
>
> How do i report this, & to who?
I’d start with SuSE and let them figure out if it’s an upstream problem or if
it’s their fault. Since Bill Nottingham reported tha
Looks like the GTK/Oxygen theme is broken, changed thmres & seems to work OK
How do i report this, & to who?
tedc
On Wed, Mar 5, 2014 at 2:41 AM, Ted Creedon wrote:
>
> FYI I had to blind type "bt full" into gdb after gnucash is running to
> capture the trace, before the bug freezes the scre
FYI I had to blind type "bt full" into gdb after gnucash is running to
capture the trace, before the bug freezes the screen..
tedc
On Wed, Mar 5, 2014 at 2:14 AM, Geert Janssens wrote:
> On Tuesday 04 March 2014 15:56:15 John Ralls wrote:
>
> > On Mar 4, 2014, at 3:11 PM, Ted Creedon wrote:
>
On Tuesday 04 March 2014 15:56:15 John Ralls wrote:
> On Mar 4, 2014, at 3:11 PM, Ted Creedon wrote:
> > Crash back trace - gnucash froze up but nothing else - yet -
>
> [Long, detailed backtrace elided].
>
> OK. It’s Gtk and Oxygen almost all the way down, and it’s crashing
> trying to draw som
On Mar 4, 2014, at 3:11 PM, Ted Creedon wrote:
> Crash back trace - gnucash froze up but nothing else - yet -
>
[Long, detailed backtrace elided].
OK. It’s Gtk and Oxygen almost all the way down, and it’s crashing trying to
draw something. I don’t think that there’s anything we can do to help
On Mar 4, 2014, at 10:21 AM, Ted Creedon wrote:
> Another fault, looks like troubleshooting will be difficult
>
> Seems too be related to focusing on the menu bar. Moving the mouse over it
> causes a crash
>
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> The program no long
I'll keep trying to get my taxes & a backtrace done
Would running under Gnome help?
ted
On Mon, Mar 3, 2014 at 8:52 PM, Bill Nottingham wrote:
> John Ralls (jra...@ceridwen.us) said:
> > Yeah, I dunno what Oxygen::MenuStateData::menuItemIsActive is except that
> > it doesn't have anything to
Another fault, looks like troubleshooting will be difficult
Seems too be related to focusing on the menu bar. Moving the mouse over it
causes a crash
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) bt full
No stack.
On Tue, Mar 4, 2014 at 9:13
John Ralls (jra...@ceridwen.us) said:
> Yeah, I dunno what Oxygen::MenuStateData::menuItemIsActive is except that
> it doesn't have anything to do with GnuCash, Gtk+, or GLib. You need to
> explain your environment in detail and why we should support it, otherwise
> you're totally on your own.
I
Just a vanilla SuSE 13.1 x64 Linux system.
Gnucash has run fine on Suse for years.
I have 2 other 13.1's I'll try them
tedc
On Mon, Mar 3, 2014 at 7:46 PM, John Ralls wrote:
>
> On Mar 3, 2014, at 5:30 PM, Ted Creedon wrote:
>
> > Another crash, output from gdb (bt not possible)
> >
> > gdb
On Mar 3, 2014, at 5:30 PM, Ted Creedon wrote:
> Another crash, output from gdb (bt not possible)
>
> gdb) run^M(gdb) run^M(gdb) run
> Starting program: /usr/local/bin/gnucash
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> [New Th
On Mar 3, 2014, at 4:12 PM, Ted Creedon wrote:
> do I need a pointer to the sources for
>
> libgobject-2_0-0 - General-Purpose Utility Library -- Object-Oriented
> Framework for C?
>
Libgobject, libgio, and libglib are all parts of glib.
Regards,
John Ralls
> On Mon, Mar 3, 2014 at 3:47 PM
Another crash, output from gdb (bt not possible)
gdb) run^M(gdb) run^M(gdb) run
Starting program: /usr/local/bin/gnucash
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe21e8700 (LWP 6203)]
[New Thread 0x7fffe19e7700 (LWP
Noticed this on startup:
Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0
Try: zypper install -C
"debuginfo(build-id)=a3f8edc19f47fd2290dbbf3d05670ed13ba6a93c"
Traceback (most recent call last):
File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py",
line 9, in
On Mar 3, 2014, at 3:30 PM, Ted Creedon wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x7fffef356cac in g_type_check_instance_is_a () from
> /usr/lib64/libgobject-2.0.so.0
>
>
> can't do a bt because the fault freezes the X Screen
>
> had to ssh in from another box & kil
Program received signal SIGSEGV, Segmentation fault.
0x7fffef356cac in g_type_check_instance_is_a () from
/usr/lib64/libgobject-2.0.so.0
can't do a bt because the fault freezes the X Screen
had to ssh in from another box & kill -TERM gdb
Should I do a debug build?
Tedc
20 matches
Mail list logo
