Package Details: phpstorm 2022.1.1b221.5591.58-1

Git Clone URL: (read-only, click to copy)
Package Base: phpstorm
Description: Lightweight and Smart PHP IDE
Upstream URL:
Keywords: development ide php
Licenses: custom:jetbrains
Submitter: None
Maintainer: freswa
Last Packager: freswa
Votes: 216
Popularity: 1.87
First Submitted: 2011-01-22 19:28 (UTC)
Last Updated: 2022-05-13 22:38 (UTC)

Dependencies (6)

Required by (0)

Sources (3)

Latest Comments

mantiiicore commented on 2021-12-16 20:07 (UTC)

If you've encountered this exception: "Failed to prepare transaction: Failed to generate phpstorm-jre information"

try to delete the temperory folder at /var/tmp/pamac-build-[your-username]/phpstorm-jre and rebuild the package once again

ColiZei commented on 2021-12-05 19:51 (UTC)

I got the same problem as Zelf. I installed phpstorm and jre 2021.2.3b212.5457.49-1 successfully. Now if i want to update to 2021.3b213.5744.279-1 it fails with: "Failed to prepare transaction: Failed to generate phpstorm-jre information".

Reinstall does not work as well.

I'm using Manjaro Gnome.

Any help? Thanks!

Zelf commented on 2021-10-22 03:59 (UTC) (edited on 2021-10-22 04:00 (UTC) by Zelf)

Cannot install phpstorm-jre 2021.2.3b212.5457.49-1

Getting this message:

Preparing... Cloning phpstorm build files... Generating phpstorm-jre information... Failed to prepare transaction: Failed to generate phpstorm-jre information

Tried cleaning packages and deleting previously installed and reinstalling, but now cannot install and phpstorm still relies on this.

kekek commented on 2021-10-20 07:10 (UTC)


P31314 commented on 2021-10-20 07:07 (UTC) (edited on 2021-10-20 07:13 (UTC) by P31314)

I try to run phpstorm on sway

So far, I installed phpstorm and phpstorm-jre I could register and the splash screen shows, but then I just get a gray square that's about it. Does someone have an Idea?


solved it, thank y'all ;D

francma commented on 2021-07-30 13:09 (UTC)

After update from 2021.1 to 2021.2 I needed to start PhpStorm like this:

PHPSTORM_VM_OPTIONS=.config/JetBrains/PhpStorm2021.1/phpstorm64.vmoptions phpstorm

It seems that 2021.2 starts with empty phpstorm64.vmoptions and since version 2021.1 it is required to add --illegal-access=permit to be able to run PhpStorm with OpenJDK. This is needed only for the first start to let PhpStorm import phpstorm64.vmoptions from previous version.

Akholic commented on 2021-07-30 00:25 (UTC)

After the latest update (2021.2b212.4746.100-1) the program won't boot up correctly. The splash screen is missing and the UI seems to be broken (missing UI elements and styling). I have the phpstorm-jre package installed and rolling back previous version removes the problem.

angauber commented on 2021-07-11 11:04 (UTC)

I had to install phpstorm-jre, phpstorm would just crash without it

bcremer commented on 2020-12-03 15:45 (UTC)

Here is the PKGBUILD patch for 2020.3:

navarroaxel commented on 2020-07-30 11:25 (UTC)

The says that the package version "should be the same as the version released by the author". I think you should use 2020.2 without the build number.

freswa commented on 2020-05-18 21:48 (UTC)

This is a split package, also containing phpstorm-jre, which provides the JetBrains Runtime. That's why the dependency on JRE is optional.

RoestVrijStaal commented on 2020-05-18 13:05 (UTC) (edited on 2020-05-18 13:07 (UTC) by RoestVrijStaal)

According to the Installation Guide the Java dependencies aren't needed anymore for the phpstorm-package

You do not need to install Java to run PhpStorm, because JetBrains Runtime is bundled with the IDE (based on JRE 11).

Please correct me if I'm wrong.

freswa commented on 2020-05-04 16:30 (UTC)

I'll return to hardcoded builds with the next release.

hgn commented on 2020-05-04 14:45 (UTC) (edited on 2020-05-04 14:45 (UTC) by hgn)

The pkgver procedure will fail if there is more than 1 directory under src As would be the case when updating. It will add PhpStorm at the end of the version from the cut -f2

DaFeliX commented on 2020-04-30 06:23 (UTC)

Users using i3wm having issues with no caret in the editor after switching from other applications:

  1. Press Help | Edit Custom VM Options... (".vmoptions" file will open)
  2. Add to a new line
  3. Restart IDE

Also see

freswa commented on 2020-03-29 23:38 (UTC)

Will be fixed with the next version.

timschumi commented on 2020-03-29 14:54 (UTC)

Icon is currently broken for whatever reason, XFCE doesn't appear to add any suffix when searching using a full path.

Since the icon is available in /usr/share/pixmaps/, please consider just using Icon=phpstorm instead of the full path.

jwundrak commented on 2020-03-22 00:56 (UTC) (edited on 2020-03-22 00:56 (UTC) by jwundrak)

the icon update not works for me here in gnome3. If I do



it works, cause it is fetching from /usr/share/pixmaps

Could you please update this (and also for datagrip?)

Pierre commented on 2020-03-04 19:53 (UTC) (edited on 2020-03-04 19:55 (UTC) by Pierre)

In order to display the icon in e.g. KDE's application menu remove the filename ending of the icon in jetbrains-phpstorm.desktop:



fikrimi commented on 2019-11-13 13:33 (UTC) (edited on 2019-11-13 13:37 (UTC) by fikrimi)

If your problem is that Phpstorm has indeed build number directory inside their Phpstorm-2019.X.X.tar.gz then ksemmler solution seems better

freswa commented on 2019-11-05 23:26 (UTC)

@CReimer Sorry, for ignoring your comment. Overlooked it in my Inbox between several harassments. You're right. Jetbrains sometimes changes buildnumbers after a release and that's why it's included in the pkgver as builds with the same pkgver should have the same content.

CReimer commented on 2019-11-04 22:21 (UTC)

I figured out why he's using these weird version numbers. Apparently Jetbrains manipulates tarballs after release sometimes. They even state a build version on their download page:

Would have been nice if @freswa would have just clarified that here. Instead of ignoring comments.

pzlds commented on 2019-09-26 09:23 (UTC) (edited on 2019-09-26 09:30 (UTC) by pzlds)

What are those bullshit version numbers? The version is 2019.2.3, nothing else. Also, that mechanism to find the build ID is horrible.

Also, removing all contributors mentioned in the PKGBUILD isn't necessarily the nicest thing to do. f4e051ce04ee

I get that you have a huge-ass ego with that E-Mail of yours and you want to plaster it on as many packages as possible, but removing the attributions of other contributors should never be done.

CReimer commented on 2019-09-14 20:30 (UTC)

What's going on with the version number? Last time I checked the latest version was 2019.2.2. (

puzzle commented on 2019-09-14 05:38 (UTC)

@ksemmler thinks

fikrimi commented on 2019-09-14 01:54 (UTC)

I genuinely concern that build number that make you need to add custom pkgver() . Why dont just remove it and back to 2019.2.2 ?

ksemmler commented on 2019-09-13 20:42 (UTC)

For everyone having issues with this pkgbuild, i have modified it and it worked fine on my end:

freswa commented on 2019-09-13 19:22 (UTC)

There is no officially supported AUR helper. The build is fine with makepkg. Please report issues related to AUR helpers upstream.

uzvermode commented on 2019-09-13 18:33 (UTC) (edited on 2019-09-13 18:34 (UTC) by uzvermode)

Using trizen getting this error:

==> Validating source files with sha512sums... PhpStorm-2019.2.2.tar.gz ... Passed jetbrains-phpstorm.desktop ... Passed ==> Extracting sources... -> Extracting PhpStorm-2019.2.2.tar.gz with bsdtar ==> Starting pkgver()... ==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace. ==> ERROR: pkgver() generated an invalid version: 2019.2.2bcoder/phpstorm/src/PhpStorm :: Unable to build phpstorm - makepkg exited with code: 12

val08 commented on 2019-09-13 17:51 (UTC)

ERROR: Error loading ''

freswa commented on 2019-09-13 16:13 (UTC)

Sorry for screwing this up. It should work again for everyone.

Spider.007 commented on 2019-09-13 13:38 (UTC)

please fix your pkgver() - it fails when building from within a path that contains a dash.

Instead of find|tail you can use:

find ${srcdir} -mindepth 1 -maxdepth 1 -type d -printf %P

andoni commented on 2019-09-13 13:17 (UTC)


There seems to be a problem with the PKGBUILD file, it fails when the build path contains "-" caracter.

To fix this I added "-exec basename {} \;" to the find command inside pkgver(). Do not know if it is the best option, but works.


pkgver() { - echo ${pkgver%b}b$(find ${srcdir} -maxdepth 1 -type d | tail -1 | cut -d "-" -f2) + echo ${pkgver%b}b$(find "${srcdir}" -maxdepth 1 -type d -exec basename {} \; | tail -1 | cut -d "-" -f2) }

fikrimi commented on 2019-09-13 11:45 (UTC)


changing to yay doesnt seems as a solution for me. to be direct, I think we should stick with the release name without build number for this package, the PhpStorm release for stable version has been kept like it before (2019.2.1, 2019.2.2).

mlamm commented on 2019-09-13 11:14 (UTC) (edited on 2019-09-13 11:16 (UTC) by mlamm)

I am unable to install this since the latest update:

==> Making package: phpstorm 2019.2.2b192.6603.42-1 (Fri 13 Sep 2019 13:05:53 CEST)

-> Downloading PhpStorm-2019.2.2.tar.gz...


==> Starting package_phpstorm()...

rsync: change_dir "/tmp/yaourt-tmp-mlamm/aur-phpstorm/src/PhpStorm-tmp" failed: No such file or directory (2)

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1189) [sender=3.1.3]

==> ERROR: A failure occurred in package_phpstorm().

obelix1502 commented on 2019-09-13 10:49 (UTC)


I had the same error with trizen, so I've used yay and with it, no error more.

I've asked the question on:

For the, there was an error of double quotes with ${srcdir}, I've tried to resove it in editing the PKBUILD with trizen (the first time), but there was an error 1 yet...

fikrimi commented on 2019-09-13 02:59 (UTC)

I got this error on 2019.2.2b192.6603.42 ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.

Rulatir commented on 2019-07-25 13:30 (UTC) (edited on 2019-07-25 13:30 (UTC) by Rulatir)

Note to maintainer: I just tried to package 2019.2 for myself, and ran into issues when building the phpstorm-jre package. It would appear that the directory in the package was renamed from jre64 to jbr aka "JetBrains Runtime". I changed the path in the package method, and the phpstorm-jre package built, albeit with file conflicts with the phpstorm package: when I tried to install both, pacman told me that both packages contain this jbr directory.

HOWEVER just upgrading phpstorm seems to be fine - it works. Perhaps the phpstorm-jre package won't be needed anymore?

vrlord commented on 2019-07-23 14:08 (UTC)

Working good on manjaro, only detail is the icon on taskbar not showings as it expected, the desktop entry is this:

[Desktop Entry] Version=1.0 Type=Application Name=PhpStorm Icon=/opt/phpstorm/bin/phpstorm.png Exec="/otp/phpstorm/bin/" %f Comment=The Drive to Develop Categories=Development;IDE; Terminal=false StartupWMClass=jetbrains-phpstorm

also, Datagrip has the same issue (it gets confusing to get many apps with the same icon).

Any Ideas?

Zauberfisch commented on 2019-05-18 11:26 (UTC)

The Error message "JDK classes seem to be not on PhpStorm classpath. Please ensure you run the IDE on JDK rather than JRE." means that phpstorm is missing a dependency. Either you install and possibly reference your own install of java, or simply install the phpstorm-jre package:

bcremer commented on 2019-03-28 13:08 (UTC) (edited on 2019-03-28 13:08 (UTC) by bcremer)

Updated values for PHPStorm 2019.1:

pkgver=2019.1 _pkgver=191.6183.95 sha512=bcbd7df142c755ab63a9c2c47705e3e09b8de50b81026fe385605e61c4e7cac2d9df332ed8d3156953f65f3334ac595859865d5a3575f41dee91759cbc4ba4cf

makaay commented on 2019-03-19 14:04 (UTC) (edited on 2019-03-20 00:41 (UTC) by makaay)

I have the same problem on arch xfce4. "JDK classes seem to be not on PhpStorm classpath. Please ensure you run the IDE on JDK rather than JRE." How can I solve?

hkirsman commented on 2019-02-01 12:18 (UTC)

Hm, I installed yesterday (or was it couple of days ago) PhpStorm in Manjaro xfce environment and it worked. Today I tried it in Manjaro Cinnamon and I get: JKD classes seem to be not on PhpStorm classpath. Please ensure you run in the IDE on JRK rather than JRE.

What could be the case?

freswa commented on 2019-01-12 18:35 (UTC)

Will be included in the next release. Thanks!

AngryUbuntuNerd commented on 2019-01-12 18:33 (UTC)

Could you add optional dependency "java-openjfx" which is required for example for rendering of Markdown files?

xuanwo commented on 2018-11-14 02:42 (UTC) (edited on 2018-11-14 02:49 (UTC) by xuanwo)

The -Didea.jre.check=true in the /usr/bin/phpstorm may lead to phpstorm without phpstorm-jre failed to start, this can be fixed by remove them.

And I found goland do not have this options, maybe we cloud remove it directly.

Related diff can be seen here:

anemo commented on 2018-09-07 20:22 (UTC) (edited on 2018-09-07 20:22 (UTC) by anemo)

2018.2.2 is released

z0iberg commented on 2018-07-30 06:49 (UTC)

If you have some problem with updating package, you should change source link to${pkgver}.tar.gz

MazeChaZer commented on 2018-05-30 08:54 (UTC)

PKGBUILD: s/webstorm-jre/phpstorm-jre

j_heimbach commented on 2018-03-29 14:59 (UTC)

Patch for 2018.1

thrimbor commented on 2018-03-17 17:15 (UTC)

Patch to get the latest version:

friday13 commented on 2018-02-13 03:32 (UTC)

:: Proceed with installation? [Y/n] u ==> WARNING: Your packages are saved in /tmp/yaourt-tmp-

psqenr commented on 2017-12-13 15:09 (UTC) (edited on 2017-12-13 15:10 (UTC) by psqenr)


I had the error: "rsync: change_dir /tmp/phpstorm/src/PhpStorm-173.3727.138" failed: No such file or directory (2)".

I fixed it changing the version number _pkgver in PKGBUILD to "173.3942.32".

Hope it helps!

skeblow commented on 2017-08-04 07:57 (UTC) (edited on 2017-08-04 07:57 (UTC) by skeblow)

@caotic: sorry about late response... fixed it with manual downloading snapshot and running makepkg and pacman -U phpsorm* commands

francoism90 commented on 2017-08-01 07:22 (UTC) (edited on 2017-08-01 10:12 (UTC) by francoism90)

Why has the webstorm-jre added as optdep? Edit: thanks for the fix :)

Pierre commented on 2017-07-21 15:33 (UTC)

There is an optdep to webstorm-jre but the PKGBUILD builds phpstorm-jre.

francoism90 commented on 2017-07-20 17:23 (UTC)

@hernandev: For KDE users it seems to be stable, I don't recommend clearing your pac* cache before upstream fix this.

hernandev commented on 2017-07-20 11:48 (UTC)

NOTICE: Gnome Users, DO NOT Upgrade yet, there is a serious bug you can check on this issue: If you don't use Navigate to File or Navigate do Code, it will not matter to you. Previous versions works very well.

caotic commented on 2017-07-11 17:24 (UTC)

@skeblow: Where you able to fix it? I am experiencing the same problem.

freswa commented on 2017-06-20 21:43 (UTC)

Will be an optdepend with the next release

andrew67 commented on 2017-06-20 04:07 (UTC)

Can gnome-keyring be added as an optional dependency? Saving credentials for deployment will silently fail on 2017.x if it's not installed.

flavius commented on 2017-05-22 17:24 (UTC)

@skeblow: problem confirmed.

skeblow commented on 2017-04-21 07:14 (UTC)

can anyone confirm problem with [php/web]storm-jre "duplicate target"? thanks

pots1012 commented on 2017-03-24 13:58 (UTC)

@frederik I guess I missed that. That worked. Thanks.

Rulatir commented on 2017-03-24 13:33 (UTC) (edited on 2017-03-24 13:33 (UTC) by Rulatir)

@frederik Yeah figured it out but I thought that it was a "fix" package and that I still upgrade phpstorm with the regular phpstorm package.

freswa commented on 2017-03-24 13:31 (UTC)

@pots1012 You should read messages when they pop up. Delete ~/.PhpStorm2017.1 and try again. @Rulatir: Pls install phpstorm-jre.

pots1012 commented on 2017-03-24 13:15 (UTC)

I lost all my PHPStorm preference settings (including keymap) with this upgrade. Do we think this is just an inherent PHPStorm upgrade problem or is there a way this can be helped by a change to the PKGBUILD?

andoni commented on 2017-03-23 20:43 (UTC)

@Case_Of: I updated PhpStorm with that changes to PKGBUILD, and it worked fine. So I think no more changes are needed

commented on 2017-03-23 17:26 (UTC)

@andoni: Is there not more deep changes to do in the PKGBUILD?

andoni commented on 2017-03-23 16:39 (UTC)

New version of PHPStorm 2017.1 +pkgver=2017.1 +_pkgver=171.3780.104 +sha512sums=('38d9b49ab60c5e315c4891ec4f0c261028ba7e5012effc174a8e044ed4a6d4052fbde6913815c7dd97b4fcd08852a55b4819bda77a4a8ff476141216a3ef57ee'

kelzax commented on 2017-03-14 23:50 (UTC)

@frederik Thank you

freswa commented on 2017-03-14 23:43 (UTC)

The -jre package contains the jre for phpstorm. It's a split package so anyone who like to use his own jre may not install the jre package.

kelzax commented on 2017-03-14 23:40 (UTC)

I am confused. Is phpstorm-jre a dependency of this package, or a separate repository of the full application with a JRE built in? - Also, thanks for doing this. The Jetbrains download takes forever.

freswa commented on 2017-02-28 08:59 (UTC)

@marcvanged: pls install phpstorm-jre

marcvangend commented on 2017-02-27 14:08 (UTC)

Since my update today, font rendering looked different, and it was not an improvement. The characters were thin and the anti aliasing caused reddish and greenish edges on the left/right site of the characters. Things looked better after I changed the antialias setting (under 'appearance & behavior > appearance') to "grayscale", but I think it is not exactly how it used to be. Can this be caused by the split of the package? Is there something else I can try to improve font rendering?

freswa commented on 2017-02-24 21:11 (UTC)

cogux, you also got a message about two new optdepends ;-)

cogux commented on 2017-02-24 17:16 (UTC)

frederik, after update i got a message: ERROR: Cannot start Phpstorm: No JDK found.

freswa commented on 2017-02-24 14:41 (UTC)

sorry, just fixed that

bruceutut commented on 2017-02-24 14:38 (UTC)

frederik, PKGBUILD file uses rsync for packaging. So rsync should be listed as a makedep at least.

freswa commented on 2016-11-30 00:22 (UTC)

Hi lyoneel, this is a workaround for a bug and not a dependency. If you like to use SSH in the IDE you may install gnome-keyring yourself. Cheers

lyoneel commented on 2016-11-29 11:43 (UTC) (edited on 2016-11-29 11:57 (UTC) by lyoneel)

please, add as dependency gnome-keyring, because DB SSH Tunnel not gonna work without it. this fix the error "Connection to **: SSH: Auth fail. SSH: Auth fail"

j_heimbach commented on 2016-11-24 15:32 (UTC)

as meridius mentioned the icon is not longer displayed. Problem is that Jetbrains renamed the icon png in bin/. the .desktop file must be edited, in the following gist are the changes, (change webide.png to phpstorm.png

meridius commented on 2016-11-24 14:14 (UTC)

Here is PKGBUILD for 2016.3 Please note that new icon is not displaying in Gnome Shell (at least) and the old one was removed.

freswa commented on 2016-10-20 13:24 (UTC)

@arjen: This is not the EAP package...

andoni commented on 2016-08-24 16:19 (UTC)

New PHPStorm 2016.2.1 +pkgver=2016.2.1 +_pkgver=162.1889.1 +sha512sums=('c21a2456c55407663251913d59621c81e1e0feab87a3a6e703d7824331e65bc08a37b5863a5fc31cb4029cef0ca4834c2ea9c06efdda262428706beace000186'

bcremer commented on 2016-07-13 12:07 (UTC)

+pkgver=2016.2 +_pkgver=162.1121.38 +sha256sums=('2cba44d6106b82e9acac222683bbd2528a31b3311948aad9fdfff608c321eaa2'

bcremer commented on 2016-05-11 14:17 (UTC)

New important security update was just released sha256 442d98120763932bc34545df022171baca5d2bc44e34b1f36f949e4355b99441 See:

freswa commented on 2016-03-21 18:51 (UTC)

@KingCrunch: Thank you. Gonna fix PKGBUILD. So their "System requirements" on this page are completely wrong:

KingCrunch commented on 2016-03-21 18:39 (UTC)

@frederik No /opt/phpstorm$ java -version java version "1.7.0_95" OpenJDK Runtime Environment (IcedTea 2.6.4) (Arch Linux build 7.u95_2.6.4-1-x86_64) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) /opt/phpstorm$ bin/ Unsupported Java Version: Cannot start under Java 1.7.0_95-b00: Java 1.8 or later is required. To be fair it was not that obvious to find some information See also

freswa commented on 2016-03-19 01:11 (UTC)

@KingCrunch Please see phpstorm page. It depends on 'Oracle JRE 1.6+ or OpenJDK 1.7+'

KingCrunch commented on 2016-03-19 00:57 (UTC)

The intelliJ-platform requires Java >=8

freswa commented on 2016-03-18 20:03 (UTC)

@declasun: thx for the hint. I don't think that a wrapper around the startscript is a good way to achieve this. I've just added a profile.d file and a note in the PKGBUILD.

dcelasun commented on 2016-03-18 15:13 (UTC)

@frederik: intellij-idea-ultimate-edition [0] recently merged this [1] patch so IDEA would prefer the system JDK. Could you also make the same change here? [0] [1]

retzudo commented on 2016-02-01 13:29 (UTC)

Thanks Wietse for the explanation and workaround. Starting PhpStorm with `WEBIDE_JDK=/usr/lib/jvm/java-8-openjdk /opt/phpstorm/bin/` from the terminal did in fact work for me. I copied the desktop file located at /usr/share/applications/jetbrains-phpstorm.desktop to ~/.local/share/applications/, changed the Exec line from Exec="/opt/phpstorm/bin/" %f to Exec=env WEBIDE_JDK=/usr/lib/jvm/java-8-openjdk "/opt/phpstorm/bin/" %f logged out and back in (GNOME wouldn't pick up the new desktop file otherwise) and Bob's your uncle. No more ugly fonts. This fix should persist through updates.

Wietse commented on 2016-01-31 11:48 (UTC)

@retzudo PhpStorm uses it's own packaged Oracle Java JDK, which causes the fonts to be terribly ugly. Phpstorm tries to locate a JDK installation directory which will be used to run the IDE in the following order: WEBIDE_JDK, ../jre, JDK_HOME, JAVA_HOME, "java" in PATH. The clean solution is to set the WEBIDEA_JDK environment variable to the OpenJDK path. For some reason this did not work for me, but I did not feel like spending a lot of time to find out why, so I just renamed /opt/phpstorm/jre to something else so PhpStorm would use JDK_HOME instead. (I will have to do this after each PhpStorm update.) PhpStorm does not officially support OpenJDK, but I have experienced no problems so far.

retzudo commented on 2016-01-21 14:00 (UTC)

With PhpStorm 10 I once again have font rendering issues that other people and I had with PhpStorm 9 (i.e. no anti-aliasing). The PKGBUILD for 9 had these lines to fix the issue: # fixing FS#40934 here too sed -i 's/lcd/on/' "${pkgdir}/usr/share/phpstorm/bin/phpstorm${SUFFIX}.vmoptions" echo "-Dswing.aatext=true" >> "${pkgdir}/usr/share/phpstorm/bin/phpstorm${SUFFIX}.vmoptions" So I tried to replicate that in /opt/phpstorm/bin/phpstorm64.vmoptions which didn't help. I also copied the file to ~/.WebIde100/ which also didn't fix the font rendering. Running PhpStorm via `_JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=on' phpstorm` also didn't make any difference. I have infinality packages installed (fonts & JRE/JDK) and font rendering in PhpStorm 9 (installed via commit b164826 & makepkg) works correctly. Suggestions?

freswa commented on 2016-01-12 11:42 (UTC)

@ram4nd Could you point me to a complete list of additional tools which phpstrom optdepends on?

ram4nd commented on 2016-01-12 08:54 (UTC)

Please add optional dependencies for closure-linter, code-sniffer, etc... Linters and tools for code validation.

m79reed commented on 2015-11-12 10:59 (UTC)

It looks like the download service had temporary problems. File size is correct now: 198M. Thanks for response.

freswa commented on 2015-11-12 10:34 (UTC)

The checksum in the PKGBUILD ist correct, see here:

m79reed commented on 2015-11-12 10:32 (UTC) (edited on 2015-11-12 10:32 (UTC) by m79reed)

==> Validating source files with sha256sums... PhpStorm-10.0.1.tar.gz ... FAILED $ wget $ sha256sum PhpStorm-10.0.1.tar.gz 140b5e45a6d9a3333300ecf6224f6d49abbdc385883c448ce649a38c91a06b0d PhpStorm-10.0.1.tar.gz Note: PhpStorm-10.0.tar.gz (198M) PhpStorm-10.0.1.tar.gz (94M) ?

marcvangend commented on 2015-10-21 20:38 (UTC) (edited on 2015-10-21 21:08 (UTC) by marcvangend)

Thank you Frederik. I have posted a feature request upstream (

freswa commented on 2015-10-20 22:42 (UTC)

Dear Marc, there are two ways to create the .desktop-file: 1) Start a fresh installed PhpStorm (or temporary move you ~/.WebIde90 folder) and you'll be asked if you like to create a desktop shortcut 2) Start a previously used PhpStorm. On the first screen where you can choose between your last projects (if you haven't set the option to always open the last project), choose Configure -> Create Desktop Entry In both cases if you uncheck "Create entry for all users" you find the .desktop file in ~/.local/share/applications.

marcvangend commented on 2015-10-20 22:06 (UTC)

Thanks frederik, I didn't realize this was coming from upstream, I only saw its existence in Sure enough I can file a bug report / feature request upstream, but when I do I want to be sure I know all facts and details. Can you please point out where in the upstream archive this default phpstorm.desktop file is stored? There is no install script in there so it is not generated on-the-fly, is it? Thanks, Marc

freswa commented on 2015-10-20 14:29 (UTC) (edited on 2015-10-20 14:48 (UTC) by freswa)

Hi marcvangend, I agree with you, that the latest change is not "optimal". To understand the changes I made, you should know that the desktop file that I have updated, is the one that is generated by the application itself. Since ArchLinux follows the KISS principle I think the best way to request the changes to the desktop file is upstream[1]. As soon as PhpStorm generates a proper desktop file I will update this package. If you like to permanently change the behaviour on your desktop, put the edited desktop file into ~/.local/share/applications. This will overwrite the one in the package. Cheers, Frederik [1]

marcvangend commented on 2015-10-20 14:20 (UTC)

@frederik it's awesome that you respond to requests from the community so quickly. Thanks for that. However... In phpstorm.desktop, line 5: -Icon=phpstorm +Icon=/usr/share/phpstorm/bin/webide.png This change in the latest build forces all users to use the default icon, even if you're using a custom icon theme (eg. Numix-circle provides It is not the responsibility of the package to choose exactly which icon file is used. IMHO if vanilla Gnome (with the default icon theme) does not find the correct high-res icon when asked for the "phpstorm" icon, that problem should be fixed elsewhere, not in the .desktop file.

elvetemedve commented on 2015-10-19 20:26 (UTC)

Application icon of the latest PHPStorm (9.0.2-1) looks ugly under Gnome 3 (low resolution image on high zoom), because the window class is incorrect in phpstorm.desktop file. The line for that should look like this: StartupWMClass=jetbrains-phpstorm9.0.2

t638403 commented on 2015-10-16 18:42 (UTC) (edited on 2015-10-18 09:06 (UTC) by t638403)

I had problems running phpstorm with glib2 2.46.1, see links for more info:

fzerorubigd commented on 2015-08-18 16:20 (UTC)

hash is not correct.

nineinchnick commented on 2015-08-12 12:19 (UTC)

A new version is available: Version: 9.0.1 Build: 141.2402 Released: August 12, 2015

snout commented on 2015-03-04 10:51 (UTC)

Does anyone know which part(s) of PHPstorm actually depend on JDK (java-environment)? I've been running it on JRE (java-runtime) for a while and so far haven't found anything that doesn't work. Jetbrains specifically state JDK is required, so I don't think the package should change its dependency (yet), but...

r1pp3rj4ck commented on 2015-02-13 21:05 (UTC)

Shit, sorry, I actually compiled the stuff and all but forgot to upload it here. I'm getting drunk right now but when I get home I will upload it. In the meantime you can download it from my Github:

chrko commented on 2015-02-13 20:27 (UTC)

But now is 8.0.3 out ;)

r1pp3rj4ck commented on 2015-02-05 12:56 (UTC)

@fzerorubigd no problem :)

fzerorubigd commented on 2015-01-17 05:38 (UTC)

@r1pp3rj4ck sorry for wrong out of date notify. my mistake. It was early access suggestion.

r1pp3rj4ck commented on 2014-12-30 16:22 (UTC)

@sender, the package is NOT out of date. 8.0.3 is an EAP version (early access preview). If you want to use it, you can switch to the phpstorm-eap[1] package. @rikless, as @falmp has explained, this is not the package's fault. --asroot was never considered the best way to build packages (from the man page: This is for security purposes as it is normally dangerous to do so). You should build the package as a normal user instead of root. [1] -

falmp commented on 2014-12-29 16:45 (UTC)

Which AUR helper are you using? --asroot is no longer a valid option to pacman, so I know at least packer is still using it and should be fixed soon ( Not sure about yaourt or other AUR helpers, but you might wanna try downloading the .tar.gz, extracting it and running makepkg -sic inside the extracted directory (that's what the AUR helper is basically doing anyway).

rikless commented on 2014-12-29 16:31 (UTC)

It looks like since last pacman update, you can't install Jetbrains software : makepkg: invalid option '--asroot' Impossible to read PKGBUILD

kamazee commented on 2014-12-11 17:31 (UTC)

8.0.2 is out! Things to change in the PKGBUILD (other than pkgver): Build number (_pkgbuild): 139.732 SHA256: 0d46442aa32174fe16846c3c31428178ab69b827d2e0ce31f633f13b64c01afc → 2ec7766bbd0176b3f84335ff01590817d3c8a295211e9641d3e144ae4ddf6805

roheim commented on 2014-09-18 18:26 (UTC)

PKGBUILD for 8.0.1 can be found here:

marcvangend commented on 2014-09-18 08:07 (UTC)

The PKGBUILD by dcelasun worked perfectly for me. Thanks.

dcelasun commented on 2014-09-16 14:02 (UTC)

PhpStorm 8 is out! Updated PKGBUILD:

r1pp3rj4ck commented on 2014-08-27 09:24 (UTC)

Sorry, missed that one :/ Should work now.

SZoPer commented on 2014-08-26 20:38 (UTC)

@muesli: Change line 7 of PKGBUILD to this: _pkgbuild=133.1777

muesli commented on 2014-08-26 18:34 (UTC)

Getting this error: ==> Starting package()... cp: cannot stat ‘/tmp/yaourt-tmp-muesli/aur-phpstorm/src/PhpStorm-133.982’: No such file or directory

marcvangend commented on 2014-06-27 07:33 (UTC)

I had a font rendering problem as well after the update (there was no text anywhere in PhpStorm). The solutions in the comments below didn't look as good as I expected (jagged fonts) but the solution at worked perfectly for me.

falmp commented on 2014-06-19 11:40 (UTC)

Is it only here the system fonts (menus, buttons, etc.) got too small with these system properties passed as a workaround?

Skullcrasher commented on 2014-06-19 03:14 (UTC)

got the font rendering issue here too. With adding the stuff from bitdagger it worked, although the font looks not perfectly antialiased. A patch would be appreciated :) For me these two settings worked/looked better: -Dswing.aatext=true -Dawt.useSystemAAFontSettings=on

0x6d617474 commented on 2014-06-17 19:14 (UTC)

Can we add a patch to fix the font rendering issue in the latest openjdk? The following needs to be added to the /usr/share/phpstorm/bin/phpstorm64.vmoptions file: -Dswing.aatext=true -Dawt.useSystemAAFontSettings=gasp -Dsun.java2d.xrender=true

pelmennoteam commented on 2014-02-26 03:43 (UTC)

md5sum 5c68dce5fa53ce2ff42fa8a590561c40 for new version (7.1.3)

r1pp3rj4ck commented on 2013-12-17 16:50 (UTC)

Updated to PhpStorm PHP 7.1. You can contribute now here: @marcvangend, thanks for pinging me @thenonameguy, thanks for testing the package while I'm forced to use Ubuntu :D

marcvangend commented on 2013-12-17 14:13 (UTC)

Version 7.1 is out.

r1pp3rj4ck commented on 2013-11-20 06:38 (UTC)

lib32-glibc removed from deps. Actually, I'm not sure why I included it in the first place, sorry about that :/

Michitux commented on 2013-11-19 15:49 (UTC)

The lib32-glibc dependency breaks building/installing on i686 platforms as without multilib repository this package doesn't exist - please remove this dependency at least on i686. Thank you!

Tucker commented on 2013-11-08 08:07 (UTC)

Can someone point out to me the need of the lib32-glibc dependency? I removed that for now and test my installation - so far no bugs or crashes. Of course i would stop any further evaluation - if there is a showstopper! Thx. By the way: eap package comes without the dependency.

edke commented on 2013-11-04 10:52 (UTC)

There is package in AUR, that follows Jetbrains's EAP pogramme:

r1pp3rj4ck commented on 2013-11-04 10:42 (UTC)

Emmaseven, 7.0.1 is not released yet. There is however an Early Access Preview, and if you want to use that, you can install this package: I'm unflagging this package for now.

Emmaseven commented on 2013-11-04 07:12 (UTC)

Please upgrade to 7.0.1

r1pp3rj4ck commented on 2013-10-25 08:53 (UTC)

marcvangend: done, thanks :)

marcvangend commented on 2013-10-25 08:27 (UTC)

I use Docky ( and ran into 2 problems since the upgrade to version 7: A) Docky didn't display the PhpStorm icon correctly B) It didn't allow me to pin PhpStorm to the dock This happens because Docky does not know the relation between the .desktop launcher and the java application it spawns. This can be solved by adding the following line to phpstorm.desktop: StartupWMClass=jetbrains-phpstorm I hope you can add this to the package. Thanks!

r1pp3rj4ck commented on 2013-10-24 07:18 (UTC)

grindcore: thanks, fixed both of them!

grubersjoe commented on 2013-10-23 21:51 (UTC)

I'm facing two problems 1) In /usr/bin are two scripts: phpstorm and, whereof just is working. /usr/bin/phpstorm results in the following error: Error: Main class com.intellij.idea.Main could not be found or be loaded 2) The native file watcher executable is not found. See the following bug of intellij-idea-libs:

r1pp3rj4ck commented on 2013-10-23 12:34 (UTC)

edke: thank you! scarpino: working on it

edke commented on 2013-10-23 12:05 (UTC)

Disowned package, wish good luck to new maintainer :-)

ilpianista commented on 2013-10-23 11:48 (UTC)

BTW, $startdir is deprecated

ilpianista commented on 2013-10-23 11:48 (UTC)

install: cannot stat ‘/tmp/phpstorm/phpstorm-eap.desktop’: No such file or directory

ryad.eldajani commented on 2013-10-23 09:41 (UTC)

PhpStorm 7.0 PKGBUILD:

r1pp3rj4ck commented on 2013-10-22 12:38 (UTC)

PhpStorm 7.0:

roheim commented on 2013-06-24 18:33 (UTC)

PhpStorm 6.0.3:

roheim commented on 2013-06-24 18:24 (UTC)

PhpStorm 6.0.3 released.

ryad.eldajani commented on 2013-05-15 07:08 (UTC)

PhpStorm 6.0.2 released. PKGBUILD:

ryad.eldajani commented on 2013-04-18 07:10 (UTC)

PhpStorm 6.0.1 released. PKGBUILD Patchfile:

edke commented on 2013-03-28 08:29 (UTC)

Latest release is EAP, if you check product page, stable release is still 6.0. If you want latest release, please switch to phpstorm-eap package and follow EAP programme.

commented on 2013-03-16 12:07 (UTC)

edke: thanks! looks like it works now! :)

edke commented on 2013-03-15 21:10 (UTC)

skwo: added, please report back if working as requested.

commented on 2013-03-13 09:27 (UTC)

Following masser comments, can the maintainer add options=(!strip) to the MAKEPKG? Without this, PhpStorm complains about "External file sync may be slow" due to outdated fsnotifer or fsnotifer64 (on x86_64 systems) For more details

commented on 2013-03-12 16:55 (UTC)

phpstorm6 is now released

edke commented on 2013-02-12 01:58 (UTC)

Added to makepkg.conf and rebuilded both packages.

masser commented on 2013-02-11 15:34 (UTC)

Stripping the fsnotifier debug symbols causes notices of outdated native FileWatcher. Could the maintainer please add options=(!strip) to the MAKEPKG?

edke commented on 2012-11-22 05:59 (UTC)

Dropped conflict with phpstorm-eap, more in discussion at

edke commented on 2012-11-19 07:40 (UTC)

@atommixz As you can see, java dependency (java-runtime>=6)is set correctly. Therefore upon installing this had to be settled. Check or re-install your Java. I use JDK from AUR, currently 7.9-2

whoami commented on 2012-11-19 07:31 (UTC)

$ phpstorm ERROR: cannot start PhpStorm. No JDK found. Please validate either WEBIDE_JDK, JDK_HOME or JAVA_HOME environment variable points to valid JDK installation. Press Enter to continue.

edke commented on 2012-11-02 14:54 (UTC)

Updated to 5.0.4 (build 121.390).

edke commented on 2012-10-24 08:04 (UTC)

Updated to 5.0.3 (build 121.351).

edke commented on 2012-10-03 13:05 (UTC)

Updated to 5.0.2 (build 121.285).

edke commented on 2012-09-13 07:05 (UTC)

@andrgrau btw issues with 5.0 that I was writing to you about seem to be resolved in 5.0.1.

andrgrau commented on 2012-09-13 06:52 (UTC)


edke commented on 2012-09-12 22:53 (UTC)

Updated to 5.0.1 (build 121.215).

edke commented on 2012-09-11 14:16 (UTC)

As andrgrau suggested, downgraded back to 4.0.3 till final stable 5.0 comes out.

andrgrau commented on 2012-09-11 06:48 (UTC)

Me neither unless a colleague told me so. I haven't been experiencing bugs but I'm not using very intensely.

edke commented on 2012-09-11 06:36 (UTC)

@andrgrau didn't now and experienced some bugs myself, had to revert back to 4.0.3, will revert package also.

andrgrau commented on 2012-09-11 06:21 (UTC)

Thanks for updating to version 5 but it is not yet officially released and is consoidered to be a RC due to some bugs.

edke commented on 2012-07-13 21:12 (UTC)

Updated to latest 4.0.3 (build 117.746).

edke commented on 2012-06-12 11:04 (UTC)

Added link to to /usr/bin.

bab00n commented on 2012-06-01 11:20 (UTC)

Hello, md5sums and pkgbuild are outdated, please, update your script to : pkgbuild=117.501 md5sums=('d8005bbaadfbc57c991834ca9e1ee3fc') Thanks !

edke commented on 2012-05-30 04:46 (UTC)

Updated to latest 4.0.2 (build 117.474) @Popcorned thank you

commented on 2012-05-29 20:39 (UTC)

4.0.2 has been released:

edke commented on 2012-05-02 20:41 (UTC)

Updated to latest 4.0.1 (build 117.257) @ggayan thank you

commented on 2012-05-02 14:35 (UTC)

last version is 4.0.1 now :)

edke commented on 2012-04-24 13:01 (UTC)

Updated to latest 4.0 (build 117.222). @andrgrau thanx for noticing.

andrgrau commented on 2012-04-17 11:15 (UTC)

The new version is out :-)

mrozanc commented on 2012-02-28 09:32 (UTC)

You are welcome :)

mrozanc commented on 2012-02-28 09:32 (UTC)

As there is no changelog published, I have check here The fixes are mainly for the JavaScript platform.

edke commented on 2012-02-28 09:28 (UTC)

Updated to build 111.344, version 3.0.3 (thanx Chinoisfurax for noticing).

mrozanc commented on 2012-02-28 09:10 (UTC)

PhpStorm 3.0.3 (build 111.344) is available at md5sum for this package is af1a42bd3a3ba7f20efc55c861870a39 This release is not announced on the jetbrains site but is indicated in the IDE menu (Help/Check for Update…)

edke commented on 2012-02-07 22:42 (UTC)

As there is no RSS for comments of package or updates (or there is?), follow @edke on twitter to get updates.

edke commented on 2012-02-07 22:31 (UTC)

Updated to build 111.296, version 3.0.2

edke commented on 2012-01-31 15:52 (UTC)

Updated to build 111.271, version 3.0.1

dcelasun commented on 2011-10-29 22:11 (UTC)

Package adopted and updated.

mortan commented on 2011-06-03 16:07 (UTC)

Needs update or orphan!

edke commented on 2007-01-01 00:18 (UTC)

Package disowned (thank you mortan), adopted and updated to just released PhpStorm 3.0 (build 111.19).