Page 2 of 2
Re: Version 1.7.0 - Barrier Breaker Bugs
Posted: Thu Jan 22, 2015 4:31 am
by Rog66
Plugin Source - USB Drive fails after a period
Am finding that after a period Tor (once I manually installed it ) stops working and have narrowed it down to the USB drive being used as the plugin source becoming "read only". If I swap the plugin source back to ROOT and the back to the USB drive it starts working again. Have tried 2 different usb drives and it does the same on both.
Re: Version 1.7.0 - Barrier Breaker Bugs
Posted: Thu Jan 29, 2015 10:02 pm
by Lantis
Issue 7 - Minidlna not scanning
reproduced this issue. Pressing "rescan media" causes the screen to dim and "apply settings" briefly (1 second or less) and then nothing happens. DLNA status screen doesn't show that scanning is occurring. Log file only shows the following every time "rescan media" is pressed:
Code: Select all
[2015/01/30 12:57:51] minidlna.c:939: error: MiniDLNA is already running. EXITING.
**EDIT**
Had some free time so i did some digging. I believe the issue lies within this section of code:
Code: Select all
function rescanMedia()
{
var Commands = [];
Commands.push("/etc/init.d/minidlna stop");
Commands.push("kill -9 $(pidof minidlnad)");
Commands.push("rm -f $(uci get minidlna.config.db_dir)/files.db");
Commands.push("/etc/init.d/minidlna start");
setControlsEnabled(false, true, UI.WaitSettings);
var param = getParameterDefinition("commands", Commands.join("\n")) + "&" + getParameterDefinition("hash", document.cookie.replace(/^.*hash=/,"").replace(/[\t ;]+.*$/, ""));
var stateChangeFunction = function(req)
{
if(req.readyState == 4)
{
setControlsEnabled(true);
}
}
runAjax("POST", "utility/run_commands.sh", param, stateChangeFunction);
}
of the minidlna.js file.
by running the 4 commands manually (using "top" to find the PID of minidlna) the process restarted without a problem and media scanning began automatically.
i believe the line:
Code: Select all
Commands.push("kill -9 $(pidof minidlnad)");
should read:
Code: Select all
Commands.push("kill -9 $(pidof minidlna)");
Re: Version 1.7.0 - Barrier Breaker Bugs
Posted: Wed Feb 11, 2015 1:25 pm
by bouwew
Bugreport on my 1.7.x build on WDR 4900 V1:
No graphs are shown:
- Bandwidth usage
- Bandwidth distribution
- QoS distribution (QoS is enabled)
Connected host page - Host with active connections: table is going outside the frame border on the Gargoyle theme. For the Dark theme it's OK.
And I'm seeing this message in the log:
Code: Select all
Wed Feb 11 18:16:56 2015 kern.warn kernel: [16392.836134] _exception: 2 callbacks suppressed (now and then)
Wed Feb 11 18:16:56 2015 kern.info kernel: [16392.840607] bw_get[1322]: unhandled signal 11 at 00000000 nip 480712b0 lr 48019380 code 30001 (many times)
Probably this happens when I have a page open with a graph that's not displaying.
Re: Version 1.7.0 - Barrier Breaker Bugs
Posted: Wed Feb 11, 2015 2:06 pm
by tapper
Hi wen trying to look at Web Usage
the Recent Web Searches
table is not shoing up. I am using firefox 38 not working in IE ether.
Re: Version 1.7.0 - Barrier Breaker Bugs
Posted: Wed Feb 11, 2015 5:04 pm
by Lantis
bouwew wrote:Bugreport on my 1.7.x build on WDR 4900 V1:
No graphs are shown:
- Bandwidth usage
- Bandwidth distribution
- QoS distribution (QoS is enabled)
.
When I've had problems with no graphs showing, a reboot fixed it.
Specifically, restarting the firewall fixes it.
Try: /use/lib/gargoyle/restart_firewall.sh
Re: Version 1.7.0 - Barrier Breaker Bugs
Posted: Thu Feb 12, 2015 5:30 am
by bouwew
Lantis, thanks for your suggestion!
Tried it, but it doesn't work, graphs don't show any trace, and I keep getting the errors as show before in the log when I select a page showing a graph.
Probably some ar71xx kernel patches need to be applied to the mpc85xx kernel while building. Will look into it.
Re: Version 1.7.0 - Barrier Breaker Bugs
Posted: Fri Feb 20, 2015 12:08 pm
by eramseth
When you guys say fix applied, do you mean to the main download or to the experimental/monthly/unofficial builds?
Re: Version 1.7.0 - Barrier Breaker Bugs
Posted: Fri Feb 20, 2015 6:26 pm
by Lantis
The official 1.7.0 on the website still has these bugs. You can compile your own build that is more up to date, or you can use Spy's builds which are more up to date (although his current one is missing some minor patches).