Page 103 of 107 FirstFirst ... 35393101102103104105 ... LastLast
Results 1,021 to 1,030 of 1069

Thread: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

  1. #1021
    Join Date
    Apr 2012
    Beans
    46

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    how many controls connects when you connect it with usb?
    Cos here I get two controls connected with only 1 control connected and one constantly pops and dissapears for a while but the other one stays up and the only way to properly test if its working or not is in tux racer or neverball by just pressing the middle ps3 button when ingame

    If it works in those games then you should be able to play ubuntu based applications games like nexuiz by rebinding some of the keys to the "gamepad"

    this is how my system reacts to pulling out the usb cable and putting it back into the controler or the other way around by pulling out the usb of the computer and back in

    http://tinypic.com/view.php?pic=2w4loy1&s=6

    to play with it after you let it connect thru the bluetooth just go into game profiles and choose an option for tux or neverball by what buttons to be accesible on the sixaxis, if the sixaxis works in tux racer or neverball you pretty much have acess to the whole sixaxis and afterwards you can probably keybind it to work in games like yellowblod goes to war or nexuiz and perhaps even other games

    solution: the gamepad might be conneted without sixaxis noticing it if you get the bluetooth pop, try tux racer or neverball to see if its a bug withing qtsixa or something else

    the bluetooth acessing spams a bit and you might get more then 1 message
    Last edited by Smakone; May 2nd, 2012 at 05:32 PM.

  2. #1022
    Join Date
    May 2012
    Beans
    2

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Quote Originally Posted by Smakone View Post
    how many controls connects when you connect it with usb?
    Cos here I get two controls connected with only 1 control connected and one constantly pops and dissapears for a while but the other one stays up and the only way to properly test if its working or not is in tux racer or neverball by just pressing the middle ps3 button when ingame
    When connecting in USB, i only get one device and it's rock solid. If i push the "PS" button, it doesnt try to connect. If i disconnect the usb cable, the controler disapears from QtSixA and when i press the "PS" button, it tries to connect. I see it appear/disappear in QtSixA, it even has time to read the properties displayed in the "Bluetooth" frame (Address, signal quality, battery status). However, it doesnt stay long enough to be usable and then i get the "grant" popup (same as your screenshot, but less swedish, heh). The grant popup comes up about 9 times and it doesnt care if i check the "always grant" box. After the 9th time, the controler gives up and stops trying to connect, so now i see 0 controlers in QtSixA.

    I never get to a point where the controler is actually usable, while using bluetooth. (I tried with neverball).
    Last edited by nlz242; May 3rd, 2012 at 03:34 AM.

  3. #1023
    Join Date
    Apr 2012
    Beans
    46

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Update

    Handed in my computer to a computer company

    The Sixaxis now works in ubuntu as a mouse and I can play texas hold em with it

    Using the gnome profile and I can rebind keys to other functions but the mouse steering seems locket to the axises, using axis 1 as mouse and axis 2 as scroll

    The "Gamepad" also works wireless

    Perhaps this could be integrated with further layers, I have to use the terminal to start the Gamepad In order to acess it wireless

  4. #1024
    Join Date
    May 2012
    Beans
    2

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    I'm having problems with sixad. i go to pair my ps3 controller and it rumbles and the LEDs light up but then fails and i get this in the terminal.


    andy@andy-Presario-CQ56-Notebook-PC:~$ sixad --start
    sixad-bin[15782]: started
    sixad-bin[15782]: sixad started, press the PS button now
    sixad-bin[15782]: Server mode active, will start search now
    sixad-bin[15782]: One event received
    sixad-bin[15782]: Will initiate Sixaxis now
    sixad-bin[15782]: One event proccessed
    sixad-sixaxis[15784]: started
    sixad-sixaxis[15784]: Connected 'PLAYSTATION(R)3 Controller (60:38:0E:C4:A0:15)' [Battery 00]
    sixad-sixaxis[15784]: Bad Sixaxis buffer (out of battery?), disconneting now...
    sixad-sixaxis[15784]: Read loop was broken on the Sixaxis process
    sixad-sixaxis[15784]: Closing uinput...
    sixad-sixaxis[15784]: uinput_close()::ioctl(UI_DEV_DESTROY) - success!
    sixad-sixaxis[15784]: uinput_close()::close(fd) - success!
    sixad-sixaxis[15784]: Done

    I have no idea what to do or what the problem is. thank you for any help

  5. #1025
    Join Date
    Apr 2012
    Beans
    46

    Smile Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Are you sure that the battery is loaded.

    Cos thats how the sixaxis reacts on Sony playstation when the battery is depleted

    The terminal also says that the battery status on your gamepad is 0 of 0

    Supposed t be 0 of 5

  6. #1026
    Join Date
    May 2012
    Beans
    2

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    yes the battery is in and has a full charge. it works fine on my ps3 and the ps3 says its charged. i have tried both of my controllers and i get the same message for both. thank you for the fast response

  7. #1027
    Join Date
    May 2012
    Beans
    1

    Lightbulb Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Quote Originally Posted by nlz242 View Post
    I recently installed Ubuntu 12.04 (Precise Pangolin) and i am having a hard time getting my PS3 controler to work.

    I was using 11.10 before + the package from the PPA and it was working fine, so i know my hardware isn't the cause. For testing purposes i have re installed 11.10 and tested again, with succes.

    Ive tried installing using 2 differents methods. After i upgraded my old 11.10 to 12.04, i noticed there were no Precise Pangolin packages in the PPA so i grabbed the source and built it.
    The other method i tried was installing the Oneiric Ocelot .deb files directly (sixad first, then qtsixa).

    I can pair my device without any issues.
    Once paired, i run "sudo sixad --stop" then "sudo sixad --start", then i open up qtsixa (just to see what is happening) and after that i push my "PS" button.
    On my fresh install + .deb, i get constant connects/disconnects in the UI and a popup that asks if i want to grant acces to the bluetooth device. I check the "Always grant acces" box then i click "grant" but the popups comes back for the whole duration of the controler's connection process. Once the controler gives up, i stop getting the popups. My terminal with "sixad --start" doesn't detect the controler.

    On my upgraded install, i get constant connects/disconnects in the UI.
    My terminal with "sixad --start" doesn't detect the controler. (No popups on this one).

    Any idea? I can provide more documentation (logs, screenshots, etc), just tell me what you need.

    Thanks in advance and also thank you for making sixad and supporting it, i used it alot in me previous HTPC setups.
    Hi there,

    I've got the same problem here...

    This is what my Hcidump gave me.... atleast till i broke it, cuase it will repeat it like 6 or 7 times before the sixasses gives up.

    Code:
    HCI sniffer - Bluetooth packet analyzer ver 2.2
    device: hci0 snap_len: 1028 filter: 0xffffffff
    > HCI Event: Connect Request (0x04) plen 10
        bdaddr 00:1B:FB:33:A3:47 class 0x000508 type ACL
    < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
        bdaddr 00:1B:FB:33:A3:47 role 0x00
        Role: Master
    > HCI Event: Command Status (0x0f) plen 4
        Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
    > HCI Event: Role Change (0x12) plen 8
        status 0x00 bdaddr 00:1B:FB:33:A3:47 role 0x00
        Role: Master
    > HCI Event: Connect Complete (0x03) plen 11
        status 0x00 handle 11 bdaddr 00:1B:FB:33:A3:47 type ACL encrypt 0x00
    < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
        handle 11
    > HCI Event: Command Status (0x0f) plen 4
        Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
    > HCI Event: Read Remote Supported Features (0x0b) plen 11
        status 0x00 handle 11
        Features: 0xfc 0x07 0x82 0x7e 0x08 0x18 0x00 0x80
    < HCI Command: Remote Name Request (0x01|0x0019) plen 10
        bdaddr 00:1B:FB:33:A3:47 mode 2 clkoffset 0x0000
    > HCI Event: Command Status (0x0f) plen 4
        Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Connect req: psm 17 scid 0x02f5
    < ACL data: handle 11 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0040 scid 0x02f5 result 1 status 0
          Connection pending - No futher information available
    < ACL data: handle 11 flags 0x00 dlen 10
        L2CAP(s): Info req: type 2
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > ACL data: handle 11 flags 0x02 dlen 16
        L2CAP(s): Info rsp: type 2 result 0
          Extended feature mask 0x0000
    < ACL data: handle 11 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0040 scid 0x02f5 result 0 status 0
          Connection successful
    < ACL data: handle 11 flags 0x00 dlen 12
        L2CAP(s): Config req: dcid 0x02f5 flags 0x00 clen 0
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > HCI Event: Remote Name Req Complete (0x07) plen 255
        status 0x00 bdaddr 00:1B:FB:33:A3:47 name 'PLAYSTATION(R)3 Controller'
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
    < ACL data: handle 11 flags 0x00 dlen 18
        L2CAP(s): Config rsp: scid 0x02f5 flags 0x00 result 0 clen 4
          MTU 672 
    > ACL data: handle 11 flags 0x02 dlen 14
        L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
          Success
    < ACL data: handle 11 flags 0x00 dlen 5
        L2CAP(d): cid 0x02f5 len 1 [psm 17]
          HIDP: Control: Virtual cable unplug
    < ACL data: handle 11 flags 0x00 dlen 12
        L2CAP(s): Disconn req: dcid 0x02f5 scid 0x0040
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 1
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Connect req: psm 19 scid 0x02f6
    < ACL data: handle 11 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0041 scid 0x02f6 result 1 status 2
          Connection pending - Authorization pending
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Disconn rsp: dcid 0x02f5 scid 0x0040
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 1
    < ACL data: handle 11 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0041 scid 0x02f6 result 0 status 0
          Connection successful
    < ACL data: handle 11 flags 0x00 dlen 12
        L2CAP(s): Config req: dcid 0x02f6 flags 0x00 clen 0
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > ACL data: handle 11 flags 0x02 dlen 36
        L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 24
          QoS 0x02 (Guaranteed) 
    < ACL data: handle 11 flags 0x00 dlen 18
        L2CAP(s): Config rsp: scid 0x02f6 flags 0x00 result 0 clen 4
          MTU 672 
    > ACL data: handle 11 flags 0x02 dlen 14
        L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
          Success
    < ACL data: handle 11 flags 0x00 dlen 12
        L2CAP(s): Disconn req: dcid 0x02f6 scid 0x0041
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Disconn rsp: dcid 0x02f6 scid 0x0041
    < HCI Command: Disconnect (0x01|0x0006) plen 3
        handle 11 reason 0x13
        Reason: Remote User Terminated Connection
    > HCI Event: Command Status (0x0f) plen 4
        Disconnect (0x01|0x0006) status 0x00 ncmd 1
    > HCI Event: Disconn Complete (0x05) plen 4
        status 0x00 handle 11 reason 0x16
        Reason: Connection Terminated by Local Host
    > HCI Event: Connect Request (0x04) plen 10
        bdaddr 00:1B:FB:33:A3:47 class 0x000508 type ACL
    < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
        bdaddr 00:1B:FB:33:A3:47 role 0x00
        Role: Master
    > HCI Event: Command Status (0x0f) plen 4
        Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
    > HCI Event: Role Change (0x12) plen 8
        status 0x00 bdaddr 00:1B:FB:33:A3:47 role 0x00
        Role: Master
    > HCI Event: Connect Complete (0x03) plen 11
        status 0x00 handle 12 bdaddr 00:1B:FB:33:A3:47 type ACL encrypt 0x00
    < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
        handle 12
    > HCI Event: Command Status (0x0f) plen 4
        Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
    > HCI Event: Read Remote Supported Features (0x0b) plen 11
        status 0x00 handle 12
        Features: 0xfc 0x07 0x82 0x7e 0x08 0x18 0x00 0x80
    < HCI Command: Remote Name Request (0x01|0x0019) plen 10
        bdaddr 00:1B:FB:33:A3:47 mode 2 clkoffset 0x0000
    > HCI Event: Command Status (0x0f) plen 4
        Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
    > ACL data: handle 12 flags 0x02 dlen 12
        L2CAP(s): Connect req: psm 17 scid 0x02f7
    < ACL data: handle 12 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0040 scid 0x02f7 result 1 status 0
          Connection pending - No futher information available
    < ACL data: handle 12 flags 0x00 dlen 10
        L2CAP(s): Info req: type 2
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 12 packets 2
    > ACL data: handle 12 flags 0x02 dlen 16
        L2CAP(s): Info rsp: type 2 result 0
          Extended feature mask 0x0000
    < ACL data: handle 12 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0040 scid 0x02f7 result 0 status 0
          Connection successful
    < ACL data: handle 12 flags 0x00 dlen 12
        L2CAP(s): Config req: dcid 0x02f7 flags 0x00 clen 0
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 12 packets 2
    > HCI Event: Remote Name Req Complete (0x07) plen 255
        status 0x00 bdaddr 00:1B:FB:33:A3:47 name 'PLAYSTATION(R)3 Controller'
    > ACL data: handle 12 flags 0x02 dlen 12
        L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
    < ACL data: handle 12 flags 0x00 dlen 18
        L2CAP(s): Config rsp: scid 0x02f7 flags 0x00 result 0 clen 4
          MTU 672 
    > ACL data: handle 12 flags 0x02 dlen 14
        L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
          Success
    < ACL data: handle 12 flags 0x00 dlen 5
        L2CAP(d): cid 0x02f7 len 1 [psm 17]
          HIDP: Control: Virtual cable unplug
    < ACL data: handle 12 flags 0x00 dlen 12
        L2CAP(s): Disconn req: dcid 0x02f7 scid 0x0040
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 12 packets 2
    > ACL data: handle 12 flags 0x02 dlen 12
        L2CAP(s): Connect req: psm 19 scid 0x02f8
    < ACL data: handle 12 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0041 scid 0x02f8 result 1 status 2
          Connection pending - Authorization pending
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 12 packets 2
    > ACL data: handle 12 flags 0x02 dlen 12
        L2CAP(s): Disconn rsp: dcid 0x02f7 scid 0x0040
    < ACL data: handle 12 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0041 scid 0x02f8 result 3 status 0
          Connection refused - security block
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 12 packets 1
    > HCI Event: Disconn Complete (0x05) plen 4
        status 0x00 handle 12 reason 0x13
        Reason: Remote User Terminated Connection
    > HCI Event: Connect Request (0x04) plen 10
        bdaddr 00:1B:FB:33:A3:47 class 0x000508 type ACL
    < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
        bdaddr 00:1B:FB:33:A3:47 role 0x00
        Role: Master
    > HCI Event: Command Status (0x0f) plen 4
        Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
    > HCI Event: Role Change (0x12) plen 8
        status 0x00 bdaddr 00:1B:FB:33:A3:47 role 0x00
        Role: Master
    > HCI Event: Connect Complete (0x03) plen 11
        status 0x00 handle 11 bdaddr 00:1B:FB:33:A3:47 type ACL encrypt 0x00
    < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
        handle 11
    > HCI Event: Command Status (0x0f) plen 4
        Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
    > HCI Event: Read Remote Supported Features (0x0b) plen 11
        status 0x00 handle 11
        Features: 0xfc 0x07 0x82 0x7e 0x08 0x18 0x00 0x80
    < HCI Command: Remote Name Request (0x01|0x0019) plen 10
        bdaddr 00:1B:FB:33:A3:47 mode 2 clkoffset 0x0000
    > HCI Event: Command Status (0x0f) plen 4
        Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Connect req: psm 17 scid 0x02f9
    < ACL data: handle 11 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0040 scid 0x02f9 result 1 status 0
          Connection pending - No futher information available
    < ACL data: handle 11 flags 0x00 dlen 10
        L2CAP(s): Info req: type 2
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > ACL data: handle 11 flags 0x02 dlen 16
        L2CAP(s): Info rsp: type 2 result 0
          Extended feature mask 0x0000
    < ACL data: handle 11 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0040 scid 0x02f9 result 0 status 0
          Connection successful
    < ACL data: handle 11 flags 0x00 dlen 12
        L2CAP(s): Config req: dcid 0x02f9 flags 0x00 clen 0
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > HCI Event: Remote Name Req Complete (0x07) plen 255
        status 0x00 bdaddr 00:1B:FB:33:A3:47 name 'PLAYSTATION(R)3 Controller'
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
    < ACL data: handle 11 flags 0x00 dlen 18
        L2CAP(s): Config rsp: scid 0x02f9 flags 0x00 result 0 clen 4
          MTU 672 
    > ACL data: handle 11 flags 0x02 dlen 14
        L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
          Success
    < ACL data: handle 11 flags 0x00 dlen 5
        L2CAP(d): cid 0x02f9 len 1 [psm 17]
          HIDP: Control: Virtual cable unplug
    < ACL data: handle 11 flags 0x00 dlen 12
        L2CAP(s): Disconn req: dcid 0x02f9 scid 0x0040
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 1
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Disconn rsp: dcid 0x02f9 scid 0x0040
    > ACL data: handle 11 flags 0x02 dlen 12
        L2CAP(s): Connect req: psm 19 scid 0x02fa
    < ACL data: handle 11 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0040 scid 0x02fa result 1 status 2
          Connection pending - Authorization pending
    < ACL data: handle 11 flags 0x00 dlen 16
        L2CAP(s): Connect rsp: dcid 0x0040 scid 0x02fa result 3 status 0
          Connection refused - security block
    > HCI Event: Number of Completed Packets (0x13) plen 5
        handle 11 packets 2
    > HCI Event: Disconn Complete (0x05) plen 4
        status 0x00 handle 11 reason 0x13
        Reason: Remote User Terminated Connection
    Any idea's ??

    Keep on trying offcourse

  8. #1028
    Join Date
    Apr 2012
    Beans
    46

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Might be abit simple but if you havent paired the sixaxis with the computers bluetooth thru a usb cable and qtsixas interface menu /pair device etc

    The bluetooth will keep popping and the "gamepad" will blink but never connect. Once its paired you can just start it with terminal

    Might be 2 easy but sometimes the simplest solutions are the best

    altho if you havent missed this part you need another solution

  9. #1029
    Join Date
    Nov 2011
    Beans
    10

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    rannaf@crying atm :/

    with QtSixA i cannot connect the controller i recognizes it with usb (but cannot move mouse or anyting, if it is suppose to work that way i dont know)

    after pairing and force connect and stuff i unplugg and press ps button and it blinks for a while and brings up the adress of the controller but constantly "connects/disconnects" and is not usable and i cannot recive the battery status

    so here's what happens when i try to start PS3 controller manually

    rannaf@bt:~$ sudo sixpair
    Current Bluetooth master: 00:19:7e:e1:fe:ca
    Setting master bd_addr to 00:19:7e:e1:fe:ca
    rannaf@bt:~$ sixad --start
    sixad-bin[20177]: started
    sixad-bin[20177]: Can't open HIDP control socket

    Assuming that his is the main problem that QtSixA does not work

    My little pee that's suppose to be a brain does not figure out how to fix this and google did not help me much

    im using QtSixA 1.5.1

  10. #1030
    Join Date
    Sep 2006
    Beans
    26
    Distro
    Xubuntu 12.10 Quantal Quetzal

    Re: HOW-TO: Connect Sixaxis to Ubuntu trough bluetooth mode

    Finding these sites got mine working.
    Don't forget rfkill, it is possible that your bluetooth is simply off.

    http://wiki.xbmc.org/index.php?title..._PS3_BD_Remote
    http://kitlaan.twinaxis.com/projects/bluez-ps3remote/

    -Orbital

Page 103 of 107 FirstFirst ... 35393101102103104105 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •