New Iron-Version: 29.0.1600.1 Stable for Linux

Iron Forum for english speaking people

Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby Azrael5 » Thu Oct 17, 2013 12:41 pm

Embedded PDF reader in IRON: SOLUTION

Chrome use an embedded plugin to read PDF... to make able SRWARE IRON to run PDF:

Download CHROME DEB and unpack it, find libpdf.so file and copy it in /usr/share/iron folder, so that you get PDF READER working in SRWARE IRON.
Jetway pt88bspro-ec|Pentium 4 670|OCZ Platinum DDR400 4x1GB|Sapphire HD3850 AGP|Physx Ageia|Xonar d2X|Dexxa ps/2|Logitech Z-5500|Asus VB175T|Lubuntu/Xp
Azrael5
 
Posts: 60
Joined: Tue Feb 21, 2012 10:24 am


Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby faucon50 » Mon Oct 21, 2013 9:35 am

Hi,

If you let Iron idle more then ~ 30 min, see the result:

Code: Select all
 Watchdog[3862]: segfault at 0 ip 00007ff83ae57e3e sp 00007ff82cbedf00 error 6 in iron[7ff83741e000+5d6c000]
10-21 08:39 kernel: [ 9813.840592] INFO: task Watchdog:3862 blocked for more than 120 seconds.
10-21 08:39 kernel: [ 9813.840601] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:39 kernel: [ 9813.840607] Watchdog        D 0000000000000002     0  3862   3831 0x00000000
10-21 08:39 kernel: [ 9813.840617]  ffff880101827af8 0000000000000082 ffffffff81c15440 ffff880127a99740
10-21 08:39 kernel: [ 9813.840628]  ffff880101827fd8 ffff880101827fd8 ffff880101827fd8 0000000000013ec0
10-21 08:39 kernel: [ 9813.840636]  ffff880129b3ae80 ffff880102cd8000 ffff880101827ae8 7fffffffffffffff
10-21 08:39 kernel: [ 9813.840644] Call Trace:
10-21 08:39 kernel: [ 9813.840660]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:39 kernel: [ 9813.840671]  [<ffffffff816f15c5>] schedule_timeout+0x1e5/0x250
10-21 08:39 kernel: [ 9813.840681]  [<ffffffff8108f9f6>] ? ttwu_do_activate.constprop.84+0x66/0x70
10-21 08:39 kernel: [ 9813.840688]  [<ffffffff8108fad6>] ? ttwu_queue+0xd6/0xf0
10-21 08:39 kernel: [ 9813.840696]  [<ffffffff816f2c9f>] wait_for_common+0xdf/0x180
10-21 08:39 kernel: [ 9813.840704]  [<ffffffff81092150>] ? try_to_wake_up+0x200/0x200
10-21 08:39 kernel: [ 9813.840711]  [<ffffffff816f2e1d>] wait_for_completion+0x1d/0x20
10-21 08:39 kernel: [ 9813.840719]  [<ffffffff811f703b>] coredump_wait+0x1bb/0x230
10-21 08:39 kernel: [ 9813.840728]  [<ffffffff8131353b>] ? apparmor_cred_prepare+0x3b/0x60
10-21 08:39 kernel: [ 9813.840735]  [<ffffffff811f78af>] do_coredump+0xff/0x500
10-21 08:39 kernel: [ 9813.840743]  [<ffffffff811847a2>] ? kmem_cache_free+0x42/0x160
10-21 08:39 kernel: [ 9813.840752]  [<ffffffff8106d901>] ? dequeue_signal+0x41/0x180
10-21 08:39 kernel: [ 9813.840760]  [<ffffffff810701e3>] get_signal_to_deliver+0x223/0x490
10-21 08:39 kernel: [ 9813.840770]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:39 kernel: [ 9813.840777]  [<ffffffff816db971>] ? printk+0x61/0x63
10-21 08:39 kernel: [ 9813.840786]  [<ffffffff8119b7b0>] ? vfs_write+0x110/0x180
10-21 08:39 kernel: [ 9813.840795]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:39 kernel: [ 9813.840803]  [<ffffffff816f447c>] retint_signal+0x48/0x8c
10-21 08:39 kernel: [ 9813.840810] INFO: task Chrome_ChildIOT:3863 blocked for more than 120 seconds.
10-21 08:39 kernel: [ 9813.840813] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:39 kernel: [ 9813.840817] Chrome_ChildIOT D 0000000000000003     0  3863   3831 0x00000000
10-21 08:39 kernel: [ 9813.840824]  ffff880102dc5cd8 0000000000000082 0000000000000000 ffffffffffffffe0
10-21 08:39 kernel: [ 9813.840832]  ffff880102dc5fd8 ffff880102dc5fd8 ffff880102dc5fd8 0000000000013ec0
10-21 08:39 kernel: [ 9813.840840]  ffff880129b3c5c0 ffff880102cdae80 ffff880126289680 ffff880126289680
10-21 08:39 kernel: [ 9813.840847] Call Trace:
10-21 08:39 kernel: [ 9813.840855]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:39 kernel: [ 9813.840864]  [<ffffffff8105fc05>] exit_mm+0x85/0x130
10-21 08:39 kernel: [ 9813.840872]  [<ffffffff8105fe13>] do_exit+0x163/0x480
10-21 08:39 kernel: [ 9813.840879]  [<ffffffff8106d66b>] ? __dequeue_signal+0x6b/0xb0
10-21 08:39 kernel: [ 9813.840887]  [<ffffffff810601c4>] do_group_exit+0x44/0xa0
10-21 08:39 kernel: [ 9813.840895]  [<ffffffff810701ee>] get_signal_to_deliver+0x22e/0x490
10-21 08:39 kernel: [ 9813.840903]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:39 kernel: [ 9813.840912]  [<ffffffff8119b7b0>] ? vfs_write+0x110/0x180
10-21 08:39 kernel: [ 9813.840920]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:39 kernel: [ 9813.840927]  [<ffffffff816fce9a>] int_signal+0x12/0x17
10-21 08:39 kernel: [ 9813.840934] INFO: task SGI_video_sync:3940 blocked for more than 120 seconds.
10-21 08:39 kernel: [ 9813.840937] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:39 kernel: [ 9813.840941] SGI_video_sync  D 0000000000000001     0  3940   3831 0x00000000
10-21 08:39 kernel: [ 9813.840947]  ffff8800c66cdcd8 0000000000000082 0000000000000000 ffffffffffffffe0
10-21 08:39 kernel: [ 9813.840955]  ffff8800c66cdfd8 ffff8800c66cdfd8 ffff8800c66cdfd8 0000000000013ec0
10-21 08:39 kernel: [ 9813.840962]  ffff880129b39740 ffff8800c77c45c0 ffff880126289680 ffff880126289680
10-21 08:39 kernel: [ 9813.840969] Call Trace:
10-21 08:39 kernel: [ 9813.840976]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:39 kernel: [ 9813.840984]  [<ffffffff8105fc05>] exit_mm+0x85/0x130
10-21 08:39 kernel: [ 9813.840992]  [<ffffffff8105fe13>] do_exit+0x163/0x480
10-21 08:39 kernel: [ 9813.840999]  [<ffffffff8106d66b>] ? __dequeue_signal+0x6b/0xb0
10-21 08:39 kernel: [ 9813.841008]  [<ffffffff810601c4>] do_group_exit+0x44/0xa0
10-21 08:39 kernel: [ 9813.841015]  [<ffffffff810701ee>] get_signal_to_deliver+0x22e/0x490
10-21 08:39 kernel: [ 9813.841023]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:39 kernel: [ 9813.841031]  [<ffffffff810bb13c>] ? do_futex+0x7c/0x1b0
10-21 08:39 kernel: [ 9813.841038]  [<ffffffff810bb3b7>] ? sys_futex+0x147/0x1a0
10-21 08:39 kernel: [ 9813.841046]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:39 kernel: [ 9813.841053]  [<ffffffff816fce9a>] int_signal+0x12/0x17
10-21 08:41 kernel: [ 9933.494817] INFO: task Watchdog:3862 blocked for more than 120 seconds.
10-21 08:41 kernel: [ 9933.494827] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:41 kernel: [ 9933.494832] Watchdog        D 0000000000000002     0  3862   3831 0x00000000
10-21 08:41 kernel: [ 9933.494842]  ffff880101827af8 0000000000000082 ffffffff81c15440 ffff880127a99740
10-21 08:41 kernel: [ 9933.494853]  ffff880101827fd8 ffff880101827fd8 ffff880101827fd8 0000000000013ec0
10-21 08:41 kernel: [ 9933.494861]  ffff880129b3ae80 ffff880102cd8000 ffff880101827ae8 7fffffffffffffff
10-21 08:41 kernel: [ 9933.494869] Call Trace:
10-21 08:41 kernel: [ 9933.494885]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:41 kernel: [ 9933.494896]  [<ffffffff816f15c5>] schedule_timeout+0x1e5/0x250
10-21 08:41 kernel: [ 9933.494906]  [<ffffffff8108f9f6>] ? ttwu_do_activate.constprop.84+0x66/0x70
10-21 08:41 kernel: [ 9933.494913]  [<ffffffff8108fad6>] ? ttwu_queue+0xd6/0xf0
10-21 08:41 kernel: [ 9933.494921]  [<ffffffff816f2c9f>] wait_for_common+0xdf/0x180
10-21 08:41 kernel: [ 9933.494929]  [<ffffffff81092150>] ? try_to_wake_up+0x200/0x200
10-21 08:41 kernel: [ 9933.494936]  [<ffffffff816f2e1d>] wait_for_completion+0x1d/0x20
10-21 08:41 kernel: [ 9933.494944]  [<ffffffff811f703b>] coredump_wait+0x1bb/0x230
10-21 08:41 kernel: [ 9933.494953]  [<ffffffff8131353b>] ? apparmor_cred_prepare+0x3b/0x60
10-21 08:41 kernel: [ 9933.494961]  [<ffffffff811f78af>] do_coredump+0xff/0x500
10-21 08:41 kernel: [ 9933.494969]  [<ffffffff811847a2>] ? kmem_cache_free+0x42/0x160
10-21 08:41 kernel: [ 9933.494977]  [<ffffffff8106d901>] ? dequeue_signal+0x41/0x180
10-21 08:41 kernel: [ 9933.494985]  [<ffffffff810701e3>] get_signal_to_deliver+0x223/0x490
10-21 08:41 kernel: [ 9933.494995]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:41 kernel: [ 9933.495003]  [<ffffffff816db971>] ? printk+0x61/0x63
10-21 08:41 kernel: [ 9933.495012]  [<ffffffff8119b7b0>] ? vfs_write+0x110/0x180
10-21 08:41 kernel: [ 9933.495020]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:41 kernel: [ 9933.495028]  [<ffffffff816f447c>] retint_signal+0x48/0x8c
10-21 08:41 kernel: [ 9933.495034] INFO: task Chrome_ChildIOT:3863 blocked for more than 120 seconds.
10-21 08:41 kernel: [ 9933.495038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:41 kernel: [ 9933.495041] Chrome_ChildIOT D 0000000000000003     0  3863   3831 0x00000000
10-21 08:41 kernel: [ 9933.495048]  ffff880102dc5cd8 0000000000000082 0000000000000000 ffffffffffffffe0
10-21 08:41 kernel: [ 9933.495056]  ffff880102dc5fd8 ffff880102dc5fd8 ffff880102dc5fd8 0000000000013ec0
10-21 08:41 kernel: [ 9933.495064]  ffff880129b3c5c0 ffff880102cdae80 ffff880126289680 ffff880126289680
10-21 08:41 kernel: [ 9933.495071] Call Trace:
10-21 08:41 kernel: [ 9933.495079]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:41 kernel: [ 9933.495088]  [<ffffffff8105fc05>] exit_mm+0x85/0x130
10-21 08:41 kernel: [ 9933.495096]  [<ffffffff8105fe13>] do_exit+0x163/0x480
10-21 08:41 kernel: [ 9933.495103]  [<ffffffff8106d66b>] ? __dequeue_signal+0x6b/0xb0
10-21 08:41 kernel: [ 9933.495112]  [<ffffffff810601c4>] do_group_exit+0x44/0xa0
10-21 08:41 kernel: [ 9933.495119]  [<ffffffff810701ee>] get_signal_to_deliver+0x22e/0x490
10-21 08:41 kernel: [ 9933.495128]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:41 kernel: [ 9933.495136]  [<ffffffff8119b7b0>] ? vfs_write+0x110/0x180
10-21 08:41 kernel: [ 9933.495144]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:41 kernel: [ 9933.495152]  [<ffffffff816fce9a>] int_signal+0x12/0x17
10-21 08:41 kernel: [ 9933.495158] INFO: task SGI_video_sync:3940 blocked for more than 120 seconds.
10-21 08:41 kernel: [ 9933.495161] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:41 kernel: [ 9933.495165] SGI_video_sync  D 0000000000000001     0  3940   3831 0x00000000
10-21 08:41 kernel: [ 9933.495171]  ffff8800c66cdcd8 0000000000000082 0000000000000000 ffffffffffffffe0
10-21 08:41 kernel: [ 9933.495179]  ffff8800c66cdfd8 ffff8800c66cdfd8 ffff8800c66cdfd8 0000000000013ec0
10-21 08:41 kernel: [ 9933.495186]  ffff880129b39740 ffff8800c77c45c0 ffff880126289680 ffff880126289680
10-21 08:41 kernel: [ 9933.495193] Call Trace:
10-21 08:41 kernel: [ 9933.495201]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:41 kernel: [ 9933.495208]  [<ffffffff8105fc05>] exit_mm+0x85/0x130
10-21 08:41 kernel: [ 9933.495217]  [<ffffffff8105fe13>] do_exit+0x163/0x480
10-21 08:41 kernel: [ 9933.495223]  [<ffffffff8106d66b>] ? __dequeue_signal+0x6b/0xb0
10-21 08:41 kernel: [ 9933.495231]  [<ffffffff810601c4>] do_group_exit+0x44/0xa0
10-21 08:41 kernel: [ 9933.495239]  [<ffffffff810701ee>] get_signal_to_deliver+0x22e/0x490
10-21 08:41 kernel: [ 9933.495247]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:41 kernel: [ 9933.495255]  [<ffffffff810bb13c>] ? do_futex+0x7c/0x1b0
10-21 08:41 kernel: [ 9933.495261]  [<ffffffff810bb3b7>] ? sys_futex+0x147/0x1a0
10-21 08:41 kernel: [ 9933.495269]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:41 kernel: [ 9933.495276]  [<ffffffff816fce9a>] int_signal+0x12/0x17
10-21 08:43 kernel: [10053.149164] INFO: task Watchdog:3862 blocked for more than 120 seconds.
10-21 08:43 kernel: [10053.149173] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:43 kernel: [10053.149178] Watchdog        D 0000000000000002     0  3862   3831 0x00000000
10-21 08:43 kernel: [10053.149189]  ffff880101827af8 0000000000000082 ffffffff81c15440 ffff880127a99740
10-21 08:43 kernel: [10053.149200]  ffff880101827fd8 ffff880101827fd8 ffff880101827fd8 0000000000013ec0
10-21 08:43 kernel: [10053.149208]  ffff880129b3ae80 ffff880102cd8000 ffff880101827ae8 7fffffffffffffff
10-21 08:43 kernel: [10053.149216] Call Trace:
10-21 08:43 kernel: [10053.149232]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:43 kernel: [10053.149244]  [<ffffffff816f15c5>] schedule_timeout+0x1e5/0x250
10-21 08:43 kernel: [10053.149254]  [<ffffffff8108f9f6>] ? ttwu_do_activate.constprop.84+0x66/0x70
10-21 08:43 kernel: [10053.149262]  [<ffffffff8108fad6>] ? ttwu_queue+0xd6/0xf0
10-21 08:43 kernel: [10053.149269]  [<ffffffff816f2c9f>] wait_for_common+0xdf/0x180
10-21 08:43 kernel: [10053.149277]  [<ffffffff81092150>] ? try_to_wake_up+0x200/0x200
10-21 08:43 kernel: [10053.149284]  [<ffffffff816f2e1d>] wait_for_completion+0x1d/0x20
10-21 08:43 kernel: [10053.149293]  [<ffffffff811f703b>] coredump_wait+0x1bb/0x230
10-21 08:43 kernel: [10053.149301]  [<ffffffff8131353b>] ? apparmor_cred_prepare+0x3b/0x60
10-21 08:43 kernel: [10053.149309]  [<ffffffff811f78af>] do_coredump+0xff/0x500
10-21 08:43 kernel: [10053.149317]  [<ffffffff811847a2>] ? kmem_cache_free+0x42/0x160
10-21 08:43 kernel: [10053.149325]  [<ffffffff8106d901>] ? dequeue_signal+0x41/0x180
10-21 08:43 kernel: [10053.149333]  [<ffffffff810701e3>] get_signal_to_deliver+0x223/0x490
10-21 08:43 kernel: [10053.149343]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:43 kernel: [10053.149351]  [<ffffffff816db971>] ? printk+0x61/0x63
10-21 08:43 kernel: [10053.149361]  [<ffffffff8119b7b0>] ? vfs_write+0x110/0x180
10-21 08:43 kernel: [10053.149369]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:43 kernel: [10053.149377]  [<ffffffff816f447c>] retint_signal+0x48/0x8c
10-21 08:43 kernel: [10053.149384] INFO: task Chrome_ChildIOT:3863 blocked for more than 120 seconds.
10-21 08:43 kernel: [10053.149387] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:43 kernel: [10053.149391] Chrome_ChildIOT D 0000000000000003     0  3863   3831 0x00000000
10-21 08:43 kernel: [10053.149399]  ffff880102dc5cd8 0000000000000082 0000000000000000 ffffffffffffffe0
10-21 08:43 kernel: [10053.149406]  ffff880102dc5fd8 ffff880102dc5fd8 ffff880102dc5fd8 0000000000013ec0
10-21 08:43 kernel: [10053.149414]  ffff880129b3c5c0 ffff880102cdae80 ffff880126289680 ffff880126289680
10-21 08:43 kernel: [10053.149421] Call Trace:
10-21 08:43 kernel: [10053.149429]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:43 kernel: [10053.149438]  [<ffffffff8105fc05>] exit_mm+0x85/0x130
10-21 08:43 kernel: [10053.149447]  [<ffffffff8105fe13>] do_exit+0x163/0x480
10-21 08:43 kernel: [10053.149454]  [<ffffffff8106d66b>] ? __dequeue_signal+0x6b/0xb0
10-21 08:43 kernel: [10053.149462]  [<ffffffff810601c4>] do_group_exit+0x44/0xa0
10-21 08:43 kernel: [10053.149470]  [<ffffffff810701ee>] get_signal_to_deliver+0x22e/0x490
10-21 08:43 kernel: [10053.149478]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:43 kernel: [10053.149487]  [<ffffffff8119b7b0>] ? vfs_write+0x110/0x180
10-21 08:43 kernel: [10053.149495]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:43 kernel: [10053.149502]  [<ffffffff816fce9a>] int_signal+0x12/0x17
10-21 08:43 kernel: [10053.149509] INFO: task SGI_video_sync:3940 blocked for more than 120 seconds.
10-21 08:43 kernel: [10053.149512] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:43 kernel: [10053.149516] SGI_video_sync  D 0000000000000001     0  3940   3831 0x00000000
10-21 08:43 kernel: [10053.149522]  ffff8800c66cdcd8 0000000000000082 0000000000000000 ffffffffffffffe0
10-21 08:43 kernel: [10053.149530]  ffff8800c66cdfd8 ffff8800c66cdfd8 ffff8800c66cdfd8 0000000000013ec0
10-21 08:43 kernel: [10053.149537]  ffff880129b39740 ffff8800c77c45c0 ffff880126289680 ffff880126289680
10-21 08:43 kernel: [10053.149544] Call Trace:
10-21 08:43 kernel: [10053.149551]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:43 kernel: [10053.149559]  [<ffffffff8105fc05>] exit_mm+0x85/0x130
10-21 08:43 kernel: [10053.149567]  [<ffffffff8105fe13>] do_exit+0x163/0x480
10-21 08:43 kernel: [10053.149574]  [<ffffffff8106d66b>] ? __dequeue_signal+0x6b/0xb0
10-21 08:43 kernel: [10053.149582]  [<ffffffff810601c4>] do_group_exit+0x44/0xa0
10-21 08:43 kernel: [10053.149590]  [<ffffffff810701ee>] get_signal_to_deliver+0x22e/0x490
10-21 08:43 kernel: [10053.149598]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:43 kernel: [10053.149606]  [<ffffffff810bb13c>] ? do_futex+0x7c/0x1b0
10-21 08:43 kernel: [10053.149613]  [<ffffffff810bb3b7>] ? sys_futex+0x147/0x1a0
10-21 08:43 kernel: [10053.149621]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:43 kernel: [10053.149628]  [<ffffffff816fce9a>] int_signal+0x12/0x17
10-21 08:45 kernel: [10172.803417] INFO: task Watchdog:3862 blocked for more than 120 seconds.
10-21 08:45 kernel: [10172.803426] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
10-21 08:45 kernel: [10172.803432] Watchdog        D 0000000000000002     0  3862   3831 0x00000000
10-21 08:45 kernel: [10172.803441]  ffff880101827af8 0000000000000082 ffffffff81c15440 ffff880127a99740
10-21 08:45 kernel: [10172.803452]  ffff880101827fd8 ffff880101827fd8 ffff880101827fd8 0000000000013ec0
10-21 08:45 kernel: [10172.803461]  ffff880129b3ae80 ffff880102cd8000 ffff880101827ae8 7fffffffffffffff
10-21 08:45 kernel: [10172.803469] Call Trace:
10-21 08:45 kernel: [10172.803485]  [<ffffffff816f2e49>] schedule+0x29/0x70
10-21 08:45 kernel: [10172.803496]  [<ffffffff816f15c5>] schedule_timeout+0x1e5/0x250
10-21 08:45 kernel: [10172.803506]  [<ffffffff8108f9f6>] ? ttwu_do_activate.constprop.84+0x66/0x70
10-21 08:45 kernel: [10172.803514]  [<ffffffff8108fad6>] ? ttwu_queue+0xd6/0xf0
10-21 08:45 kernel: [10172.803521]  [<ffffffff816f2c9f>] wait_for_common+0xdf/0x180
10-21 08:45 kernel: [10172.803529]  [<ffffffff81092150>] ? try_to_wake_up+0x200/0x200
10-21 08:45 kernel: [10172.803536]  [<ffffffff816f2e1d>] wait_for_completion+0x1d/0x20
10-21 08:45 kernel: [10172.803545]  [<ffffffff811f703b>] coredump_wait+0x1bb/0x230
10-21 08:45 kernel: [10172.803553]  [<ffffffff8131353b>] ? apparmor_cred_prepare+0x3b/0x60
10-21 08:45 kernel: [10172.803561]  [<ffffffff811f78af>] do_coredump+0xff/0x500
10-21 08:45 kernel: [10172.803569]  [<ffffffff811847a2>] ? kmem_cache_free+0x42/0x160
10-21 08:45 kernel: [10172.803578]  [<ffffffff8106d901>] ? dequeue_signal+0x41/0x180
10-21 08:45 kernel: [10172.803586]  [<ffffffff810701e3>] get_signal_to_deliver+0x223/0x490
10-21 08:45 kernel: [10172.803596]  [<ffffffff81014be9>] do_signal+0x29/0x130
10-21 08:45 kernel: [10172.803604]  [<ffffffff816db971>] ? printk+0x61/0x63
10-21 08:45 kernel: [10172.803613]  [<ffffffff8119b7b0>] ? vfs_write+0x110/0x180
10-21 08:45 kernel: [10172.803621]  [<ffffffff81014d70>] do_notify_resume+0x80/0xc0
10-21 08:45 kernel: [10172.803629]  [<ffffffff816f447c>] retint_signal+0x48/0x8c


In about:gpu

Log Messages
[3839:3839:1021/055814:ERROR:sandbox_linux.cc(130)] : InitializeSandbox() called with multiple threads in process gpu-process
[3839:3862:1021/083701:ERROR:gpu_watchdog_thread.cc(209)] : The GPU process hung. Terminating after 10000 ms.
GpuProcessHostUIShim:
[1268:1268:1021/093827:ERROR:sandbox_linux.cc(130)] : InitializeSandbox() called with multiple threads in process gpu-process

GPU: AMD RADEON HD 7750
Xubuntu 12.04 LTS
faucon50
 
Posts: 38
Joined: Thu Dec 08, 2011 5:35 pm


Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby logos88 » Fri Nov 01, 2013 1:14 pm

Azrael5 wrote:Embedded PDF reader in IRON: SOLUTION

Chrome use an embedded plugin to read PDF... to make able SRWARE IRON to run PDF:

Download CHROME DEB and unpack it, find libpdf.so file and copy it in /usr/share/iron folder, so that you get PDF READER working in SRWARE IRON.


If you want an embedder pdf reader, an easier and more open solution it's to install the firefox pdf reader (based on html5) in iron. You only have to install the extension "PDF Viewer" from the chrome web store:

https://chrome.google.com/webstore/deta ... cbdfmadadm
logos88
 
Posts: 4
Joined: Fri Nov 01, 2013 1:09 pm


Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby logos88 » Fri Nov 01, 2013 1:20 pm

When I run iron from terminal it gives me some errors. I use Archlinux (x64)

Code: Select all
LaunchProcess: failed to execvp:
/opt/iron/nacl_helper_bootstrap
[2198:2198:1101/121040:ERROR:nacl_fork_delegate_linux.cc(101)] Bad NaCl helper startup ack (0 bytes)
[2196:2196:1101/121041:ERROR:nacl_browser.cc(264)] Failed to open NaCl IRT file "/opt/iron/nacl_irt_x86_64.nexe": -4
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
[2392:2610:1101/122052:ERROR:platform_thread_linux.cc(99)] Failed to set nice value of thread to -10
[2196:2212:1101/122052:ERROR:object_proxy.cc(539)] Failed to call method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path= /org/freedesktop/PowerManagement/Inhibit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PowerManagement was not provided by any .service files
[2196:2212:1101/122052:ERROR:power_save_blocker_x11.cc(254)] No response to Inhibit() request!
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
[2196:2212:1101/122151:ERROR:object_proxy.cc(539)] Failed to call method: org.freedesktop.PowerManagement.Inhibit.UnInhibit: object_path= /org/freedesktop/PowerManagement/Inhibit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PowerManagement was not provided by any .service files
[2196:2212:1101/122151:ERROR:power_save_blocker_x11.cc(290)] No response to Uninhibit() request!
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
[3090:3122:1101/125203:ERROR:platform_thread_linux.cc(99)] Failed to set nice value of thread to -10
[2196:2212:1101/125203:ERROR:object_proxy.cc(539)] Failed to call method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path= /org/freedesktop/PowerManagement/Inhibit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PowerManagement was not provided by any .service files
[2196:2212:1101/125203:ERROR:power_save_blocker_x11.cc(254)] No response to Inhibit() request!
[2196:2212:1101/125204:ERROR:object_proxy.cc(539)] Failed to call method: org.freedesktop.PowerManagement.Inhibit.UnInhibit: object_path= /org/freedesktop/PowerManagement/Inhibit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PowerManagement was not provided by any .service files
[2196:2212:1101/125204:ERROR:power_save_blocker_x11.cc(290)] No response to Uninhibit() request!
[3090:3124:1101/125206:ERROR:platform_thread_linux.cc(99)] Failed to set nice value of thread to -10
[2196:2212:1101/125206:ERROR:object_proxy.cc(539)] Failed to call method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path= /org/freedesktop/PowerManagement/Inhibit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PowerManagement was not provided by any .service files
[2196:2212:1101/125206:ERROR:power_save_blocker_x11.cc(254)] No response to Inhibit() request!
[2196:2212:1101/125207:ERROR:object_proxy.cc(539)] Failed to call method: org.freedesktop.PowerManagement.Inhibit.UnInhibit: object_path= /org/freedesktop/PowerManagement/Inhibit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PowerManagement was not provided by any .service files
[2196:2212:1101/125207:ERROR:power_save_blocker_x11.cc(290)] No response to Uninhibit() request!
[3237:3256:1101/125823:ERROR:platform_thread_linux.cc(99)] Failed to set nice value of thread to -10
logos88
 
Posts: 4
Joined: Fri Nov 01, 2013 1:09 pm


Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby Azrael5 » Fri Nov 01, 2013 3:13 pm

logos88 wrote:
Azrael5 wrote:Embedded PDF reader in IRON: SOLUTION

Chrome use an embedded plugin to read PDF... to make able SRWARE IRON to run PDF:

Download CHROME DEB and unpack it, find libpdf.so file and copy it in /usr/share/iron folder, so that you get PDF READER working in SRWARE IRON.


If you want an embedder pdf reader, an easier and more open solution it's to install the firefox pdf reader (based on html5) in iron. You only have to install the extension "PDF Viewer" from the chrome web store:

https://chrome.google.com/webstore/deta ... cbdfmadadm


Place a file in a folder is easier, dont you?
Jetway pt88bspro-ec|Pentium 4 670|OCZ Platinum DDR400 4x1GB|Sapphire HD3850 AGP|Physx Ageia|Xonar d2X|Dexxa ps/2|Logitech Z-5500|Asus VB175T|Lubuntu/Xp
Azrael5
 
Posts: 60
Joined: Tue Feb 21, 2012 10:24 am


Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby logos88 » Wed Nov 06, 2013 6:49 pm

When will the linux version updated to the 30? It has been almost a month since the windows version was updated!!!
logos88
 
Posts: 4
Joined: Fri Nov 01, 2013 1:09 pm


Iron 29.0.1600.1 Linux x86_64 RPM fails transaction check

Postby mjg » Fri Nov 15, 2013 6:42 am

The 64-bit RPM fails to install with yum on Fedora 19:
Code: Select all
$ sudo yum localinstall iron64.rpm
Loaded plugins: changelog, fastestmirror, keys, langpacks, remove-with-leaves, rpm-warm-cache, show-leaves, upgrade-helper
Examining iron64.rpm: iron64-29.0.1600-2.x86_64
Marking iron64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package iron64.x86_64 0:29.0.1600-2 will be installed
--> Processing Dependency: libc.so.6 for package: iron64-29.0.1600-2.x86_64
Loading mirror speeds from cached hostfile
 * fedora: mirror.symnds.com
 * updates: mirror.symnds.com
--> Processing Dependency: libc.so.6(GLIBC_2.0) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.1.3) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.2) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.3) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libc.so.6(GLIBC_2.4) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libm.so.6 for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libm.so.6(GLIBC_2.0) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libm.so.6(GLIBC_2.1) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libpthread.so.0 for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libpthread.so.0(GLIBC_2.0) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libpthread.so.0(GLIBC_2.1) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libpthread.so.0(GLIBC_2.2) for package: iron64-29.0.1600-2.x86_64
--> Processing Dependency: libpthread.so.0(GLIBC_2.3.2) for package: iron64-29.0.1600-2.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-19.fc19 will be installed
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-19.fc19.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.17-19.fc19.i686
--> Running transaction check
---> Package nss-softokn-freebl.i686 0:3.15.2-2.fc19 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================================================================================================
 Package                                     Arch                            Version                                  Repository                        Size
=============================================================================================================================================================
Installing:
 iron64                                      x86_64                          29.0.1600-2                              /iron64                          160 M
Installing for dependencies:
 glibc                                       i686                            2.17-19.fc19                             updates                          4.2 M
 nss-softokn-freebl                          i686                            3.15.2-2.fc19                            updates                          176 k

Transaction Summary
=============================================================================================================================================================
Install  1 Package (+2 Dependent packages)

Total size: 164 M
Installed size: 174 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test


Transaction check error:
  file / from install of iron64-29.0.1600-2.x86_64 conflicts with file from package filesystem-3.2-13.fc19.x86_64
  file /usr from install of iron64-29.0.1600-2.x86_64 conflicts with file from package filesystem-3.2-13.fc19.x86_64
  file /usr/share from install of iron64-29.0.1600-2.x86_64 conflicts with file from package filesystem-3.2-13.fc19.x86_64
  file /usr/share/applications from install of iron64-29.0.1600-2.x86_64 conflicts with file from package filesystem-3.2-13.fc19.x86_64
  file /usr/share/pixmaps from install of iron64-29.0.1600-2.x86_64 conflicts with file from package filesystem-3.2-13.fc19.x86_64
  file /usr from install of iron64-29.0.1600-2.x86_64 conflicts with file from package jdk-2000:1.6.0_45-fcs.x86_64
  file /usr/share/applications from install of iron64-29.0.1600-2.x86_64 conflicts with file from package st-0.4.1-1.fc19.x86_64

Error Summary
-------------
mjg
 
Posts: 1
Joined: Fri Nov 15, 2013 6:35 am


Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby blodsugare » Wed Nov 20, 2013 2:24 pm

I always used Iron in Windows but in Ubuntu 12.04 (32bit) it just won't start.
blodsugare
 
Posts: 9
Joined: Thu Apr 18, 2013 9:38 am


Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby blodsugare » Wed Nov 20, 2013 2:56 pm

Hooray! it works thanks to this code:
32bit version
Code: Select all
sudo ln -s /lib/i386-linux-gnu/libudev.so.0.13.0 /lib/i386-linux-gnu/libudev.so.1
blodsugare
 
Posts: 9
Joined: Thu Apr 18, 2013 9:38 am


Re: New Iron-Version: 29.0.1600.1 Stable for Linux

Postby kbnn » Fri Nov 29, 2013 4:22 pm

Hello, I'm having the same issue as mjg, but also with 32-bit package.
kbnn
 
Posts: 1
Joined: Fri Nov 29, 2013 4:17 pm


PreviousNext

Return to SRWare Iron Support (English)

Who is online

Users browsing this forum: No registered users and 15 guests