Porting bunsen-pepperflash to Arch Linux

DeepDayze · 2017-06-26 20:16:27

Head_on_a_Stick wrote:

Hah! I've actually managed to get a proper package built in my openSUSE Build Repository 8)
https://software.opensuse.org//download … epperflash
Instructions:
Add this stanza to the end of /etc/pacman.conf:
[home_Head_on_a_Stick_Arch_Arch_Extra]
SigLevel = Never
Server = http://download.opensuse.org/repositories/home:/Head_on_a_Stick:/Arch/Arch_Extra/$arch
Then perform a full system update (read the news page first!) and install the package:
# pacman -Syu bunsen-pepperflash
Any further updates can then be pulled in with the usual `pacman -Syu`

Nice now I may go try Arch again!

Döbbie03 · 2017-06-26 22:48:16

Head_on_a_Stick wrote:

Hah! I've actually managed to get a proper package built in my openSUSE Build Repository 8)
https://software.opensuse.org//download … epperflash
Instructions:
Add this stanza to the end of /etc/pacman.conf:
[home_Head_on_a_Stick_Arch_Arch_Extra]
SigLevel = Never
Server = http://download.opensuse.org/repositories/home:/Head_on_a_Stick:/Arch/Arch_Extra/$arch
Then perform a full system update (read the news page first!) and install the package:
# pacman -Syu bunsen-pepperflash
Any further updates can then be pulled in with the usual `pacman -Syu`

Trying as we speak.

Head_on_a_Stick · 2017-06-28 18:17:04

I don't know if anyone has tried the package yet but the .timer unit doesn't seem to be working for me (yet):

Jun 28 18:24:56 Xanadu systemd[1]: Starting Check Adobe for pepperflash upgrade....
Jun 28 18:26:37 Xanadu systemd[1]: ^[[0;1;39mbunsen-pepperflash.service: Control process exited, code=killed status=15
Jun 28 18:26:37 Xanadu systemd[1]: Stopped Check Adobe for pepperflash upgrade..
Jun 28 18:26:37 Xanadu systemd[1]: ^[[0;1;39mbunsen-pepperflash.service: Unit entered failed state.
Jun 28 18:26:37 Xanadu systemd[1]: bunsen-pepperflash.service: Triggering OnFailure= dependencies.
Jun 28 18:26:37 Xanadu systemd[1]: bunsen-pepperflash.service: Failed to enqueue OnFailure= job: Resource deadlock avoided
Jun 28 18:26:37 Xanadu systemd[1]: ^[[0;1;39mbunsen-pepperflash.service: Failed with result 'signal'.

I have no idea what that means but it looks like the notification system doesn't work either

I've removed the ExecStartPre `sleep` command and the Nice directive from bunsen-pepperflash.service and it seems to work now:

Jun 28 18:37:14 Xanadu systemd[1]: Starting Check Adobe for pepperflash upgrade....
Jun 28 18:37:14 Xanadu update-bunsen-pepperflash[1126]: Checking Flash version available from Adobe...
Jun 28 18:37:15 Xanadu update-bunsen-pepperflash[1126]: Upstream version: 26.0.0.131
Jun 28 18:37:15 Xanadu update-bunsen-pepperflash[1126]: Installed version: 26.0.0.131

I'll change the unit file in the package for v0.1-6 anyway.

It's strange because the unit file works fine in Debian, I will have to hit the changelogs...

johnraff · 2017-06-30 05:22:57

^Different versions of systemd?
I was also thinking we should throw in a network-is-up dependency in the bunsen-pepperflash.service file.

Does the notification service work if you trigger it directly?
Have you ported the recommended bunsen-utilities package (for the notify-broadcast service)? Notification won't work without it.

Head_on_a_Stick · 2017-06-30 06:46:58

johnraff wrote:

I was also thinking we should throw in a network-is-up dependency in the bunsen-pepperflash.service file.

Yes, I had another failure yesterday, I think this was caused by the network not being up:

Jun 29 21:36:40 Xanadu systemd[1]: Starting Check Adobe for pepperflash upgrade....
Jun 29 21:36:40 Xanadu update-bunsen-pepperflash[285]: Checking Flash version available from Adobe...
Jun 29 21:36:40 Xanadu update-bunsen-pepperflash[285]: URLError: Bad URL or certs path?
Jun 29 21:36:40 Xanadu update-bunsen-pepperflash[285]: <urlopen error [Errno -2] Name or service not known>
Jun 29 21:36:40 Xanadu update-bunsen-pepperflash[285]: /usr/bin/update-bunsen-pepperflash error: /usr/lib/bunsen/pepperflash/get-adobe-flashver.py returned an error.
Jun 29 21:36:40 Xanadu systemd[1]: ^[[0;1;39mbunsen-pepperflash.service: Main process exited, code=exited, status=1/FAILURE
Jun 29 21:36:40 Xanadu systemd[1]: Failed to start Check Adobe for pepperflash upgrade..
Jun 29 21:36:40 Xanadu systemd[1]: ^[[0;1;39mbunsen-pepperflash.service: Unit entered failed state.
Jun 29 21:36:40 Xanadu systemd[1]: bunsen-pepperflash.service: Triggering OnFailure= dependencies.
Jun 29 21:36:40 Xanadu systemd[1]: ^[[0;1;39mbunsen-pepperflash.service: Failed with result 'exit-code'.

I've since added the ExecStartPre=/bin/sleep 600 line back in and it worked this morning:

Jun 30 07:17:36 Xanadu systemd[1]: Starting Check Adobe for pepperflash upgrade....
Jun 30 07:27:36 Xanadu update-bunsen-pepperflash[1127]: Checking Flash version available from Adobe...
Jun 30 07:27:39 Xanadu update-bunsen-pepperflash[1127]: Upstream version: 26.0.0.131
Jun 30 07:27:39 Xanadu update-bunsen-pepperflash[1127]: Installed version: 26.0.0.131
Jun 30 07:27:39 Xanadu systemd[1]: Started Check Adobe for pepperflash upgrade..

But yes, a check for the network would be more robust.

johnraff wrote:

Does the notification service work if you trigger it directly?

No it does not.

No error messages and silence in the journal but no popup either.

Jun 30 07:37:26 Xanadu sudo[1204]: ^[[0;1;39m   empty : TTY=pts/1 ; PWD=/home/empty ; USER=root ; COMMAND=/usr/bin/bl-notify-broadcast hello
Jun 30 07:37:26 Xanadu sudo[1204]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 30 07:37:26 Xanadu sudo[1211]: ^[[0;1;39m    root : TTY=pts/1 ; PWD=/home/empty ; USER=empty ; ENV=DISPLAY=:0 ; COMMAND=/usr/bin/notify-send hello
Jun 30 07:37:26 Xanadu sudo[1211]: pam_unix(sudo:session): session opened for user empty by (uid=0)
Jun 30 07:37:26 Xanadu sudo[1211]: pam_unix(sudo:session): session closed for user empty
Jun 30 07:37:26 Xanadu sudo[1204]: pam_unix(sudo:session): session closed for user root

Using `notify-send hello` works as expected.

This is a GNOME desktop btw.

johnraff wrote:

Have you ported the recommended bunsen-utilities package (for the notify-broadcast service)? Notification won't work without it.

I have included bl-notify-broadcast (installed to /usr/bin/bl-notify-broadcast with 0755 permissions) and bl-notify-failure@.service (/usr/lib/systemd/system/bl-notify-failure@.service, 0644) in the package, is that enough?

Head_on_a_Stick · 2017-06-30 07:00:04

Hmmm...

The pepper-flash AUR package has been moved to [Extra]

https://www.archlinux.org/packages/extr … per-flash/

I may have to reconsider this project, I only started it because I don't like AUR helpers.

johnraff · 2017-06-30 08:18:29

Head_on_a_Stick wrote:

I have included bl-notify-broadcast (installed to /usr/bin/bl-notify-broadcast with 0755 permissions) and bl-notify-failure@.service (/usr/lib/systemd/system/bl-notify-failure@.service, 0644) in the package, is that enough?

That should be enough. Debian's --with systemd in debian/rules might be doing something extra: check a compiled .deb to see what's been put in DEBIAN/postinst.

Using `notify-send hello` works as expected.

But how about 'sudo notify-broadcast hello'?

Last edited by johnraff (2017-06-30 08:20:55)

Head_on_a_Stick · 2017-06-30 20:36:58

johnraff wrote:

what's been put in DEBIAN/postinst

Just some lines to enable the .timer (I have a less rigorous version in my bunsen-pepperflash.install), good idea though, thanks.

how about 'sudo notify-broadcast hello'?

(I presume that you mean `sudo bl-notify-broadcast hello`)

I tried that to no effect, see the journal snippet in post #25

johnraff · 2017-07-01 07:16:26

how about 'sudo notify-broadcast hello'?
(I presume that you mean `sudo bl-notify-broadcast hello`)

Yes, sorry.

I tried that to no effect

Well, that should work too, independently of systemd's services.
Does 'sudo bash -x /usr/bin/bl-notify-broadcast hello' show anything helpful? (NB in Debian it's installed to /usr/sbin because it's not for normal users.)

Head_on_a_Stick · 2017-07-01 15:12:23

johnraff wrote:

Does 'sudo bash -x /usr/bin/bl-notify-broadcast hello' show anything helpful?

Looks like it just shows that the script runs correctly:

empty@Xanadu:~ $ sudo bash -x /usr/bin/bl-notify-broadcast hello
[sudo] password for empty: 
+ HELP='Call notify-send for all current X users.
Passed arguments are sent on as-is.
This script must be run as root.'
+ required_commands=(notify-send)
+ missing_commands=
+ for i in "${required_commands[@]}"
+ hash notify-send
+ [[ -n '' ]]
+ case $1 in
++ id -u
+ [[ 0 -eq 0 ]]
+ declare -A disps usrs
+ usrs=()
+ disps=()
++ users
+ for i in $(users)
+ [[ empty = root ]]
+ usrs[$i]=1
+ for u in "${!usrs[@]}"
++ ps e -u empty
++ sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p'
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for i in $(ps e -u "$u" | sed -rn 's/.* DISPLAY=(:[0-9]*).*/\1/p')
+ disps[$i]=empty
+ for d in "${!disps[@]}"
+ sudo -u empty DISPLAY=:0 notify-send hello
+ exit
empty@Xanadu:~ $

I think the problem here is the notification system in my Arch box

Plain old `notify-send hello` works but only in GNOME, it doesn't produce anything if I run pure Openbox instead.

Thanks for your help, I will look into this further when I have a moment (I can't stand loose ends).

However, I think I will be discontinuing this project now because the PPAPI plugin has become available from the official Arch repositories and so can be `Syu`d along with everything else.

johnraff · 2017-07-02 08:20:33

Have you got libnotify-bin installed? Maybe Gnome provides something else with the same functionality, lacking in a plain OB setup.

Head_on_a_Stick · 2017-07-02 14:08:40

johnraff wrote:

Have you got libnotify-bin installed?

I have libnotify installed (the Arch equivalent I think, they tend to group their packages together more than Debain).

The actual bunsen-pepperflash.{timer,service} unit files do seem to be running well now so that's good.

I have edited the following unit files and will try the new configuration with a hobbled (`chmod -x`) /usr/bin/update-bunsen-pepperflash and see if that works:

empty@Xanadu:~ $ systemctl cat --no-pager bunsen-pepperflash.service bl-notify-failure@.service                                                                                                                                              
# /usr/lib/systemd/system/bunsen-pepperflash.service
[Unit]
Description=Check Adobe for pepperflash upgrade.
OnFailure=bl-notify-failure@%n.service

[Service]
Type=oneshot
ExecStartPre=/usr/bin/sleep 600
ExecStart=/usr/bin/update-bunsen-pepperflash --upgrade
Nice=5

# /usr/lib/systemd/system/bl-notify-failure@.service
[Unit]
Description=Send failure notification

[Service]
Type=notify
ExecStart=/usr/bin/bl-notify-broadcast "Service Failed" "%I" --icon=dialog-error --expire-time=30000
empty@Xanadu:~ $

Although `bl-notify-broadcast` won't produce any pop-ups in my GNOME desktop I am hoping that it will at least run successfully with this configuration.

johnraff · 2017-07-03 03:26:31

Head_on_a_Stick wrote:

`bl-notify-broadcast` won't produce any pop-ups in my GNOME desktop

Hmm... I don't like loose ends either...

Head_on_a_Stick · 2017-07-03 06:17:56

^ I will test bl-notify-broadcast in my stretch GNOME system tonight and see if the desktop is the problem.

johnraff · 2017-07-03 09:22:00

Thanks!

Head_on_a_Stick · 2017-07-04 19:56:21

(Sorry for the delay, I only have limited access to the Debian laptop)

Update: for stretch, `notify-send` works in GNOME but not in pure openbox but `bl-notify-broadcast` works fine for both desktops.

I am now totally confused.

johnraff · 2017-07-05 00:12:43

^Hmm... what could it be? That's an Arch system of course?
So it seems to be saying that (without Gnome) notify-send works for root, but not for a normal user.

Head_on_a_Stick · 2017-07-05 06:14:24

johnraff wrote:

That's an Arch system of course?

No, that's my Debian stretch system.

It usually runs GNOME but I have pekwm/lxpanel as well.

I just installed openbox, set "openbox-session" to x-window-manager and ran `startx` (no ~/.xinitrc was present) to test stuff.

Don't know why `notify-send` won't work there but `bl-notify-broadcast` does; this also worked:

sudo -u $USER DISPLAY=:0 notify-send Hello

Anyway, I will check the Arch journal again tonight and keep on digging.

johnraff · 2017-07-05 06:36:19

'notify-send hello' works OK in my helium-dev VM, so it's not a Stretch permissions change.

Head_on_a_Stick · 2017-07-05 21:22:17

^ `notify-send hello` works in my Helium-dev system as well but not my pure stretch openbox desktop.

Slight progress in Arch: the notification system seems to be working as far as systemd is concerned:

Still no actual on-screen notification but since the ExecStart command itself doesn't work in my desktop that's not really surprising.

EDIT: no, I was looking at the wrong logs, it's still b0rked...

empty@Xanadu:~ $ journalctl -u bl-notify-failure --no-pager                                                                                                                                                                                  
-- Logs begin at Sat 2017-01-28 22:28:42 GMT, end at Wed 2017-07-05 22:25:37 BST. --
Jul 05 18:24:01 Xanadu systemd[1]: Starting Send failure notification...
Jul 05 18:24:01 Xanadu sudo[8263]:     root : TTY=unknown ; PWD=/ ; USER=empty ; ENV=DISPLAY=:0 ; COMMAND=/usr/sbin/notify-send Service Failed  --icon=dialog-error --expire-time=30000
Jul 05 18:24:01 Xanadu sudo[8263]: pam_unix(sudo:session): session opened for user empty by (uid=0)
Jul 05 18:24:01 Xanadu sudo[8263]: pam_unix(sudo:session): session closed for user empty
Jul 05 18:24:01 Xanadu systemd[1]: Failed to start Send failure notification.
Jul 05 18:24:01 Xanadu systemd[1]: bl-notify-failure.service: Unit entered failed state.
Jul 05 18:24:01 Xanadu systemd[1]: bl-notify-failure.service: Failed with result 'protocol'.
empty@Xanadu:~ $

Last edited by Head_on_a_Stick (2017-07-05 21:29:25)

#21 2017-06-26 20:16:27

Re: Porting bunsen-pepperflash to Arch Linux

#22 2017-06-26 22:48:16

Re: Porting bunsen-pepperflash to Arch Linux

#23 2017-06-28 18:17:04

Re: Porting bunsen-pepperflash to Arch Linux

#24 2017-06-30 05:22:57

Re: Porting bunsen-pepperflash to Arch Linux

#25 2017-06-30 06:46:58

Re: Porting bunsen-pepperflash to Arch Linux

#26 2017-06-30 07:00:04

Re: Porting bunsen-pepperflash to Arch Linux

#27 2017-06-30 08:18:29

Re: Porting bunsen-pepperflash to Arch Linux

#28 2017-06-30 20:36:58

Re: Porting bunsen-pepperflash to Arch Linux

#29 2017-07-01 07:16:26

Re: Porting bunsen-pepperflash to Arch Linux

#30 2017-07-01 15:12:23

Re: Porting bunsen-pepperflash to Arch Linux

#31 2017-07-02 08:20:33

Re: Porting bunsen-pepperflash to Arch Linux

#32 2017-07-02 14:08:40

Re: Porting bunsen-pepperflash to Arch Linux

#33 2017-07-03 03:26:31

Re: Porting bunsen-pepperflash to Arch Linux

#34 2017-07-03 06:17:56

Re: Porting bunsen-pepperflash to Arch Linux

#35 2017-07-03 09:22:00

Re: Porting bunsen-pepperflash to Arch Linux

#36 2017-07-04 19:56:21

Re: Porting bunsen-pepperflash to Arch Linux

#37 2017-07-05 00:12:43

Re: Porting bunsen-pepperflash to Arch Linux

#38 2017-07-05 06:14:24

Re: Porting bunsen-pepperflash to Arch Linux

#39 2017-07-05 06:36:19

Re: Porting bunsen-pepperflash to Arch Linux

#40 2017-07-05 21:22:17

Re: Porting bunsen-pepperflash to Arch Linux

Board footer