Complete Hang of 1.0.5 on Mountain Lion
Forum rules
Talk about Keka here. For bugs go to Issues.
Talk about Keka here. For bugs go to Issues.
-
- Keka & Me
- Posts: 6
- Joined: Fri Nov 04, 2016 6:36 pm
Complete Hang of 1.0.5 on Mountain Lion
So after waiting....Oh, a little over 3 years...for an update, the first thing that greets me upon using Keka to decompress some Zip files (from Finder on an external HFS+ HDD) is a hang and a crash. Of course, Keka is ever so kind to infinitely spam my notification center first.
You wanna try taking things a little more seriously?
EDIT: Moar info- exact OS is Mountain Lion 10.8.5 Build 12F2560. Behavior is triggered upon encountering a corrupt file (and let me just say, your old handling of queued files was also a hell of a lot better). Will post spindump as soon as aONe can verify it's safe to do so on a public forum.
You wanna try taking things a little more seriously?
EDIT: Moar info- exact OS is Mountain Lion 10.8.5 Build 12F2560. Behavior is triggered upon encountering a corrupt file (and let me just say, your old handling of queued files was also a hell of a lot better). Will post spindump as soon as aONe can verify it's safe to do so on a public forum.
- aone
- Mr. Keka
- Posts: 333
- Joined: Sun Feb 26, 2012 8:42 pm
- Contact:
Re: Complete Hang of 1.0.5 on Mountain Lion
Sure, please attach the hang log. As I understand, the hang is while using the new queue functionality (3 or more files dropped at once)?
Thanks for all your feedback!
Thanks for all your feedback!
aone ~
-
- Keka & Me
- Posts: 6
- Joined: Fri Nov 04, 2016 6:36 pm
Re: Complete Hang of 1.0.5 on Mountain Lion
Well, I _would_ post a spindump, but you've disabled attachments and the character limit is 60,000.
Correct. In this case, I am attempting to unzip 207 individual zip files. Old Keka would show me in-depth info10 files at a time, decompressing and showing progress all the while. If any corrupt file was encountered, it would finish unzipping what it could and then notify me of the problem. New Keka just hangs, and honestly doesn't show shit compared to the old dialog even when working correctly.As I understand, the hang is while using the new queue functionality (3 or more files dropped at once)?
- aone
- Mr. Keka
- Posts: 333
- Joined: Sun Feb 26, 2012 8:42 pm
- Contact:
Re: Complete Hang of 1.0.5 on Mountain Lion
Ok now I get your problem. I'll add a command to disable the new queue functionality and use the old one instead.
Also I can think of a "group notification" so if you drop 207 files to extract, only one notification shows at the end of the 207 files. I can get why you don't like to have 207 notifications.
I've enabled attachment, sorry for this one. "Newly registered users group" was causing the issue.
Thanks for your feedback!
Also I can think of a "group notification" so if you drop 207 files to extract, only one notification shows at the end of the 207 files. I can get why you don't like to have 207 notifications.
I've enabled attachment, sorry for this one. "Newly registered users group" was causing the issue.
Thanks for your feedback!
aone ~
-
- Keka & Me
- Posts: 6
- Joined: Fri Nov 04, 2016 6:36 pm
Re: Complete Hang of 1.0.5 on Mountain Lion
Still can't upload. The extension ".spin" is not allowed.
- aone
- Mr. Keka
- Posts: 333
- Joined: Sun Feb 26, 2012 8:42 pm
- Contact:
-
- Keka & Me
- Posts: 6
- Joined: Fri Nov 04, 2016 6:36 pm
Re: Complete Hang of 1.0.5 on Mountain Lion
There ya go.
You do not have the required permissions to view the files attached to this post.
-
- Keka & Me
- Posts: 6
- Joined: Fri Nov 04, 2016 6:36 pm
Re: Complete Hang of 1.0.5 on Mountain Lion
Still encountering the same bug with 1.0.6.
- aone
- Mr. Keka
- Posts: 333
- Joined: Sun Feb 26, 2012 8:42 pm
- Contact:
Re: Complete Hang of 1.0.5 on Mountain Lion
Try this on the Terminal:
Then open Keka. Old queue system will be uses instead.
Code: Select all
defaults write com.aone.keka ForceOldQueue -bool TRUE
aone ~
-
- Keka & Me
- Posts: 6
- Joined: Fri Nov 04, 2016 6:36 pm
Re: Complete Hang of 1.0.5 on Mountain Lion
Dude, if the new behavior causes a hang and a crash then it makes no sense whatsoever to keep it. At least offer a fuckin' checkbox or something so I don't have to go digging in the terminal just to make the App function.
Have a little pride in your work.
Have a little pride in your work.
