2016-05-20 GnuCash IRC logs
01:11:59 *** Mechtilde has joined #gnucash
01:54:22 *** Mechtilde has quit IRC
02:55:27 *** uXuss has quit IRC
02:59:42 *** uXuss has joined #gnucash
03:07:24 *** nomeata has joined #gnucash
03:50:33 *** fabior has joined #gnucash
03:54:24 *** fabior has quit IRC
03:55:26 *** fabior has joined #gnucash
04:05:34 *** andy has quit IRC
04:39:36 *** fell has joined #gnucash
05:25:30 *** fabior has quit IRC
05:28:28 *** bertbob has quit IRC
05:42:29 *** bertbob has joined #gnucash
07:14:04 *** Jimraehl1 has left #gnucash
07:18:36 *** Unhammer has quit IRC
07:20:18 *** Unhammer has joined #gnucash
07:21:01 *** Jimraehl1 has joined #gnucash
07:42:03 <Unhammer> is there a simple way to select every single account in the "Transaction report" or "Account summary report", without having to expand all children manually?
07:42:26 <Unhammer> ("Select all" doesn't.)
07:47:49 *** Unhammer has quit IRC
07:55:48 *** Unhammer has joined #gnucash
08:04:58 *** Unhammer has quit IRC
08:08:17 *** Unhammer has joined #gnucash
08:09:55 *** fell_ has joined #gnucash
08:11:43 *** fell has quit IRC
08:29:13 *** filip has joined #gnucash
08:35:56 *** filip has quit IRC
08:39:36 *** bertbob has quit IRC
08:42:05 <mikee> nhammer: Mine does. What version of GnuCash and have you selected "Levels of Subaccounts" ?
08:42:18 <mikee> nhammer: I mean
08:43:03 <mikee> h weird, losing the first char of the name!
08:46:14 *** andy has joined #gnucash
08:49:12 *** mlncn has joined #gnucash
08:51:35 <Unhammer> hey
08:51:37 <Unhammer> that is weird
08:52:03 <Unhammer> mikee, it selects subaccounts even without you having to click the little arrow to "expand" them?
08:53:10 <Unhammer> for me it does not, on 2.6.12
08:54:03 *** bertbob has joined #gnucash
08:54:39 *** minot has joined #gnucash
08:55:40 <Unhammer> sorry, meant 2.6.6 (note to self: don't check versions in terminals that are ssh-ing into another computer)
08:56:02 <Unhammer> ok so there's a newer one on newer buntus, guess I should upgrade and test again :)
08:57:15 *** bertbob has quit IRC
08:59:50 <warlord> Unhammer: I believe "Select All" then "Select Children" will do what you want.
09:00:23 <Unhammer> hm, maybe I was doing it in the wrong order
09:12:31 *** warlord has quit IRC
09:12:46 *** bertbob has joined #gnucash
09:13:15 *** warlord has joined #gnucash
09:16:11 *** bertbob has quit IRC
09:17:34 *** ChanServ sets mode: +qo warlord warlord
09:22:00 <warlord> Unhammer: could be
09:30:39 <warlord> @tell gjanssens Yes, I saw it; I plan to respond today -- been a bit busy the past couple days and barely handling work email, let alone personal email. :(
09:30:39 <gncbot> warlord: The operation succeeded.
09:31:29 *** bertbob has joined #gnucash
09:34:45 *** bertbob has quit IRC
09:35:16 *** minot has quit IRC
09:50:23 *** bertbob has joined #gnucash
09:53:41 *** bertbob has quit IRC
10:04:31 *** fabior has joined #gnucash
10:09:08 *** bertbob has joined #gnucash
10:12:24 *** bertbob has quit IRC
10:14:26 *** fabior has quit IRC
10:27:56 *** bertbob has joined #gnucash
10:31:04 *** bertbob has quit IRC
10:46:11 *** bertbob has joined #gnucash
10:54:27 *** nomeata has quit IRC
11:07:22 *** fabior has joined #gnucash
11:11:28 *** fabior has quit IRC
11:17:15 *** minot has joined #gnucash
11:29:35 <warlord> jralls: from one issue to another.. Right now I think the vm server network link is having issues. I see about 5-10% packet loss to/from the vm host and all the guests, whereas I dont see that loss to/from any other hosts on my network (crossing my uplink)
11:42:40 <warlord> I think the vmhost is definitely due for a hardware refresh...
11:53:07 *** Mechtilde has joined #gnucash
12:54:43 *** Nytram has joined #gnucash
12:55:24 *** jimvideo has joined #gnucash
13:00:35 *** bertbob has quit IRC
13:02:41 *** jose11 has joined #gnucash
13:03:21 *** jose11 has left #gnucash
13:07:25 <jralls> warlord: I expect you've already changed the wire. The ethernet port is on the mainboard, right?
13:09:03 <jralls> warlord: I suppose it might also be a bad port on your hub/switch. Can you put a sniffer on the network?
13:16:33 *** bertbob has joined #gnucash
13:19:47 *** bertbob has quit IRC
13:35:37 *** bertbob has joined #gnucash
13:36:45 <warlord> jralls: I don't recall if it's on the mainboard or not. I'd have to go check. It's unlikely a bad port on the switch, but I can swap it to another to see. I'm not seeing any loss anywhere else on my network, only to/from the vm host/guest systems
13:37:42 <warlord> It does look like the failure started suddenly about 4 1/2 weeks ago.
13:38:53 *** bertbob has quit IRC
13:39:07 <jralls> warlord: So mid-April, after the performance started going south, and not related to the recent reboot. Interesting. Do you see the packet loss with ping?
13:41:38 <warlord> Yes. ping. mtr..
13:41:52 <warlord> But only to/from the vm host or a vm guest.
13:42:02 <warlord> Other systems on my network appear to be unaffected.
13:42:52 <warlord> I've got a cool image from mrtg that shows the ping and packet-loss... with it starting mid "week 16"
13:43:17 <warlord> Let me try something. Biab.
13:43:27 <jralls> Right. Do you have a laptop with WireShark? Can you set a monitor port on the SWITCH?
13:46:03 <warlord> I just swapped cables and ports to see if it has any effect. The eth port on vmhost is on the mobo
13:47:26 <jralls> And?
13:48:01 <warlord> So far it seems to have helped.
13:48:09 <warlord> No packet loss observed.
13:48:25 <warlord> So, unclear if it's a bad port or bad cable. But I can worry about that later.
13:54:08 *** bertbob has joined #gnucash
13:55:33 *** f8x2n3 has joined #gnucash
13:57:30 *** bertbob has quit IRC
14:13:41 *** bertbob has joined #gnucash
14:23:12 *** f8x2n3 has quit IRC
14:24:43 *** f8x2n3 has joined #gnucash
14:25:29 <warlord> After 2300 packets, still 0.0% loss.
14:35:49 *** Mechtilde has quit IRC
14:36:44 <jralls> Sounds like that was the problem. Try the old port to see whether it was the cable or the port... and hope for the cable.
14:37:31 <warlord> Yeah, that'll be my next test.. At some point. "If it ain't broke"... ;)
14:37:52 <warlord> (honestly, it means I'd have to trace the cable, which is more than the 20-seconds it took to run a new one)
14:39:17 <jralls> Ah, a bit of a rat's nest, eh? Get some cable markers and sometime when you have a free 1/2 hour apply them. Makes life much easier.
14:45:55 <warlord> It's not that bad. And it started out fairly nice.
14:48:44 *** mlncn has quit IRC
14:55:52 <jralls> warlord: Do you have an ubuntu 1404 machine/VM handy? Master is failing make check on travis, but it works OK for me on Debian jessie.
14:59:52 *** bozonius has joined #gnucash
15:00:35 <warlord> Nope, I dont have any DebUnutu systems around. Sorry.
15:00:40 <warlord> I could spin one up.
15:00:50 <warlord> (but it'd be a bit)
15:01:27 <jralls> Prolly easier for me to do it, since I'll have to debug the problem after.
15:02:01 <warlord> ok
16:50:40 *** koen has joined #gnucash
16:52:15 <koen> Looking for some help on finding out why my Gnucash 2.6.12 (Linux) rather crashes than opens my file... I can open it in read-only mode, save it under a different name, but when opening it again, I get the same crash.
16:55:07 <f8x2n3> If you run GnuCash from the terminal, it might print something userful there when it crashes. From there, someone who knows more than I can maybe help you.
16:58:13 <koen> Sure, I put the full details in http://pastebin.com/KkkAQeRE
16:58:53 <koen> The short version is: *** Error in `gnucash': free(): invalid pointer: 0x0000560410113020 ***
16:59:34 <koen> Note that opening other files work fine. I tried removing the .backup and .log files which didn't change anything.
17:00:59 <jralls> koen: Probably https://bugzilla.gnome.org/show_bug.cgi?id=764871
17:04:03 <koen> Thanks for the link. If I understand it correctly, it's caused by some problematic scheduled transaction (is SX the abbreviation for that?). Would it make sense to try to open it read only, remove the transaction templates, save it and re-open?
17:07:10 <koen> Just tried it: Seems to solve the problem. Now I have to find out which one is causing the problems and recreate it.
17:11:30 <koen> Surprisingly, it was the one that I most recently added that somehow resulted in this error.
18:00:30 *** minot has quit IRC
18:03:49 *** andy has quit IRC
18:04:34 *** andy has joined #gnucash
18:18:32 *** koen has quit IRC
18:22:57 *** Nytram has quit IRC
18:29:19 *** f8x2n3 has quit IRC
19:28:11 *** bertbob has quit IRC
19:43:13 *** bertbob has joined #gnucash
19:46:19 *** bertbob has quit IRC
19:58:58 *** minot has joined #gnucash
20:01:23 *** bertbob has joined #gnucash
20:01:51 *** minot has quit IRC
21:08:24 *** minot has joined #gnucash
21:13:43 *** jimvideo has quit IRC
22:54:15 *** minot has quit IRC