Package Details: minecraft-technic-launcher 4.757-1

Git Clone URL: (read-only, click to copy)
Package Base: minecraft-technic-launcher
Description: Choose from thousands of community-made Minecraft modpacks
Upstream URL:
Licenses: custom
Submitter: someoneelse123
Maintainer: prolletto64 (prolletto64)
Last Packager: prolletto64
Votes: 62
Popularity: 0.44
First Submitted: 2012-05-10 16:14 (UTC)
Last Updated: 2022-07-11 06:30 (UTC)

Dependencies (4)

Required by (0)

Sources (3)

Latest Comments

prolletto64 commented on 2022-08-01 12:41 (UTC)

Have you tried other java apps, do they work with your proxy settings?

mahjong commented on 2022-07-22 14:29 (UTC)

This doesn't detect system proxy settings.

prolletto64 commented on 2022-05-23 14:30 (UTC)

Guys, I'm sorry for the recent delay with updates but had a issue with my computer

RVOtakuMike commented on 2022-05-06 18:40 (UTC)

They fixed the 401 issue in the latest build. Which is 744.

rassawyer commented on 2022-04-24 20:31 (UTC)

On the latest version, all modpacks return a 401 unauthorized error from

vladimir1922 commented on 2022-03-18 10:07 (UTC)

at this point, if you want to update it, the checksum fails. I managed to install it by modifying the PKGBUILD:

$HOME/.cache/yay/minecraft-technic-launcher (If you use YAY). Otherwhise whenever the PKGBUILD lives

did a sha256sum for minecraft-technic-launcher-4.720.jar. You might need to run makepkg to retrieve that. It returned as 7266c2a2bd26732639850f4e373aa07d2807bbdd7b99b5e010b275fee2148a87

replaced the first sha256sum by this one, and did a makepkg -si

jkhsjdhjs commented on 2022-03-17 00:20 (UTC)

Yes, same issue. Looks like @prolletto64 forgot to update the checksum.

jorenvG commented on 2022-03-16 14:03 (UTC)

the update you pushed today results in a failed install, same issue on multiple computers

==> ERROR: One or more files did not pass the validity check!

prolletto64 commented on 2021-07-12 19:53 (UTC)

ainola, I could help you maintaining it. I tried to write you an email, but the server returned an error

ainola commented on 2021-07-10 20:18 (UTC)

I haven't used this in years, so it's probably best if someone were to take over ownership of this package. Anyone interested in monitoring updates/maintaining, please pipe up!

Luca_S commented on 2020-04-29 14:56 (UTC)

@UnicornsOnLSD From what I see you can modify /usr/bin/technic-launcher so that instead of "exec java -jar ..." it does "exec /usr/lib/jvm/java-8-openjdk/jre/bin/java -jar ..."

UnicornsOnLSD commented on 2019-12-26 12:59 (UTC)

Is it possible to change the java version for this program only? I don't want to set everything to Java 8 if possible.

Bojahdok commented on 2019-08-24 19:40 (UTC)

Launcher is out of date

evernow commented on 2019-08-24 19:37 (UTC)

Launcher out of date, unfortunately will not work now

cobaltspace commented on 2019-04-09 20:33 (UTC)

I think the java dependency should be java-runtime=8 instead of just java-runtime.

huupoke12 commented on 2019-02-24 13:53 (UTC) (edited on 2019-02-24 14:23 (UTC) by huupoke12)

For those who installed the lastest version, run this command to set the default java to jre8: sudo archlinux-java set java-8-openjdk/jre or sudo archlinux-java set java-8-openjdk

sum01 commented on 2018-11-19 23:01 (UTC) (edited on 2018-11-20 19:58 (UTC) by sum01)

There are errors when trying to run with the newest java (v11). I wasn't able to run it until I switched to jre8-openjdk, although I didn't try v10.

EDIT: v10 didn't work either, so v8 seems the way to go.

killermoehre commented on 2018-09-06 06:15 (UTC)

The technic-launcher.desktop got the wrong sha256sum.

agentcobra commented on 2018-09-05 18:40 (UTC) (edited on 2018-09-05 18:40 (UTC) by agentcobra)

Hi, it's not an "AudioVideo" application

nichdel commented on 2017-02-18 12:28 (UTC)

Well that's what I get for relying on a helper. It works now, thanks!

ainola commented on 2017-02-17 17:38 (UTC)

@nichdel: This is due to your AUR helper thinking the source is already downloaded so it's using the previous version. I've commited an update that will fix that.

nichdel commented on 2017-02-17 12:02 (UTC) (edited on 2017-02-17 12:03 (UTC) by nichdel)

Now the jar fails the validity check.

ainola commented on 2017-02-16 16:56 (UTC)

thanks for the report, nichdel. There was indeed an update that slipped by me. I've updated. Does it work properly now?

nichdel commented on 2017-02-16 13:51 (UTC) (edited on 2017-02-16 13:53 (UTC) by nichdel)

Downloading and using the latest .jar from their website works, btw. Does this launcher need to be updated?

nichdel commented on 2017-02-16 13:47 (UTC) (edited on 2017-02-16 13:49 (UTC) by nichdel)

I too am having an error connecting to any of the API. The logs are also showing weird FileNotFound errors. ---- An example connection error. [B#347] 2017/02/16 07:40:23 [WARNING] Unable to load platform pack hexxit Error accessing URL [] > curl { "status": 401, "error": "Request Unauthorized" } ---- An example FileNotFound [B#347] 2017/02/16 07:08:01 [SEVERE] File '/home/nichdel/.technic/assets/launcher/OpenSans+Cyberbit.ttf' does not exist > ls /home/nichdel/.technic/assets/launcher/ OpenSans+Cyberbit.ttf Raleway+FireflySung.ttf aether-dep.jar patches

ainola commented on 2017-01-12 01:11 (UTC)

@ullebe1, good catch! I can confirm this behavior. I've "blacklisted" the option while preserving any others.

ullebe1 commented on 2017-01-11 20:52 (UTC)

I have experienced some problems where if the "_JAVA_OPTIONS" environment variable was set to "-Dawt.useSystemAAFontSettings=on" the launcher would enter an infinite loop of crashing and restarting. Changing line 4 in the "technic-launcher" file to "unset XMODIFIERS GTK_IM_MODULE QT_IM_MODULE _JAVA_OPTIONS" fixed the problem for me. Can anyone confirm this observation?

ainola commented on 2017-01-08 22:34 (UTC)

I'm sorry for the delay: I had meant to do this and completely forgot. I've just commented out the bsdtar commands for the licenses until upstream fixes the issue. Thanks for reporting it, DarkShadow44.

DarkShadow44 commented on 2016-11-07 09:38 (UTC)

@ainola Thanks for the reply, I've made a few tests, and think it's related to libarchive. I'm using 3.2.2 (testing) and it works with 3.2.1. I'm reporting the issue there, but in case anyone comes across this, downgrade should do the trick.

ainola commented on 2016-11-07 00:24 (UTC)

@DarkShadow44, I can't replicate this issue. Are you using an AUR helper? If so, maybe try clearing out package cache.

DarkShadow44 commented on 2016-11-07 00:15 (UTC)

Latest update fails for me with licenses/javolution.license.TXT: Could not stat licenses/javolution.license.TXT licenses/ Could not stat licenses/ licenses/thoughtworks.TXT: Could not stat licenses/thoughtworks.TXT bsdtar: Error exit delayed from previous errors.

ainola commented on 2016-11-06 16:20 (UTC)

@MarcinWieczorek: I'm pretty late to the party. Thanks for the heads-up. I think I may have been mistaken when I found the source code on Github. It appears that older versions may have been GPL3 but I'm unable to find any repositories or code dumps of the newer version; therefore, I'm re-licensing to "custom" and including whatever txt files they have for licenses. Someone could go to the technic forums and inquire if this matter doesn't appear to be correct.

MarcinWieczorek commented on 2016-09-25 15:50 (UTC)

I'm pretty sure the license is not GPL3. If so, why don't you compile it from source?

ainola commented on 2016-08-15 00:13 (UTC)

Thanks, @Muhaha, for bringing this to my attention. It should be fixed now!

muhaha commented on 2016-08-12 09:39 (UTC)

Then I try to build this package I get the following message META-INF/: Can't replace existing directory with non-directory bsdtar: Error exit delayed from previous errors. I fixed it by adding these 5 lines to the building script optdepends=('unzip: Needed for unpack jar-file') noextract=('TechnicLauncher.jar') prepare() { unzip -y TechnicLauncher.jar }

ainola commented on 2016-05-19 14:14 (UTC)

Lubosz: That doesn't make sense. Are there any relevant logs?

lubosz commented on 2016-05-19 12:22 (UTC)

Running the launcher from the command line did not work for me! It spawns a java process, but does not display a window. The shell is distached at "Setting up logging", and I need to kill the java instance. It works when I launch the .desktop file from the GUI. (GNOME)

commented on 2016-04-20 20:27 (UTC)

.technic/logs is how I found out it was a 401 error... sadly, nothing else was useful. I guess I'll keep poking around...

ainola commented on 2016-04-20 14:15 (UTC)

@Celti, I'm not having any such problems. Perhaps you could try looking in your .technic/logs folder to see if anything relevant pops up.

commented on 2016-04-20 03:37 (UTC)

Anyone else having issues with the launcher giving 401 errors when trying to do anything with the API (access news, download modpacks — even vanilla!)? Not sure what I've done wrong.

ainola commented on 2016-03-06 04:47 (UTC)

It looks like technic's window draws properly when using the latest batches of updates. Maybe Mutter, maybe Java (I run OpenJDK 8), but whatever was updated seems to have fixed the grey window bug on my Nvidia (proprietary) and Intel Haswell graphics under Gnome.

ainola commented on 2016-02-19 01:46 (UTC)

I have been unsuccessful with my own experimentation. At this point I think that Mutter should have a bug raised against it (if it doesn't already exist). Please, do the honors!

lipe_cantarelli commented on 2016-02-18 12:37 (UTC)

Guys, Any updates on the blank screen problem? I have nvidia drivers but I don't use awm and the issue is still hapening.

altiris commented on 2015-09-16 01:21 (UTC)

@ainola No need to be sorry, you're the maintainer :D Thanks again!

ainola commented on 2015-09-15 14:54 (UTC)

Fixed, sorry about that: wrong checksum line was updated...

altiris commented on 2015-09-15 14:50 (UTC)

Can't update, TechnicLauncher.jar failed the checksum, I noticed in the commit/changes you changed the URL of the .jar, im guessing there is a different checksum that goes along with it?

ainola commented on 2015-05-15 19:00 (UTC)

@delusionallogic: I've attempted a lot of tinkering with wmname with no success on my end. I'm not convinced there's anything that can be done on the PKGBUILD end. I'd love to be proven wrong. All in all, this is just proof that implementing your own window controls is not only stupid design but certainly bug-inducing. :)

delusional commented on 2015-05-15 18:57 (UTC)

@ainola It is indeed a problem with non-reparenting WM's, I'm not sure it's nvidias fault though. It happens on my intel laptop as well (although it has optimus, so who knows). The awesome wiki describes this as a problem with the java implementation, dating all the way back to java 1.5 An easy workaround that works for most java applications is to run "wmname LG3D". This works since java contains a hardcoded list of "supported" non reparenting VMs, so it enables some fixes specifically for these systems when they are detected. LG3D is one those supported VMs

ainola commented on 2015-05-01 13:19 (UTC)

Removed dependency on java-environment.

altiris commented on 2015-04-27 18:15 (UTC)

@ainola Hey its all good we all make mistakes! I tried it again and it works fine! Thanks for fixing it and thanks for maintaining this as well! Have a good day!

ainola commented on 2015-04-27 03:00 (UTC)

"PKGBUILD failures are only the opportunity to begin again more intelligently." ~Henry Ford Apologies for the mishap.

altiris commented on 2015-04-26 16:26 (UTC)

Im unable to update, I get ==> Starting package()... install: cannot stat ‘/tmp/yaourt-tmp-andre/aur-minecraft-technic-launcher/src/icon_?_16x16x32.png’: No such file or directory ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build minecraft-technic-launcher.

ainola commented on 2015-03-11 18:46 (UTC)

Some on-and-off research seems to really suggest to me that this is Nvidia's fault. While there are indeed many articles and suggestions about this blank window problem, it all appears to be linked to the Awesome Window Manager and the fact that it's a non-reparenting WM. Gnome/Mutter should not have this sort of issue. The fact that my intel laptop has no issues whatsoever (admittedly, running cinnamon) really does suggest that this is one of the many Nvidia bugs that have reared up in the last year. If someone feels brave enough, one could bring it up in the devtalk forums at Nvidia: I'm not interested in dealing with those cronies any more as they could care less about customer problems.

penetal commented on 2015-03-11 18:00 (UTC)

Using "_JAVA_AWT_WM_NONREPARENTING=1; export _JAVA_AWT_WM_NONREPARENTING" in a terminal before launching the application from the same terminal does not help me. nvidia 346.47-3

ainola commented on 2015-02-26 22:54 (UTC)

@evilhamsterman, it appears it was an old holdover from when xorg-xrandr was not in the repos. I have removed it as well as openal - both appear to be unneccesary. Thanks for the heads up.

evilhamsterman commented on 2015-02-26 22:44 (UTC)

Why is this dependent on xorg-server-utils. I can understand being dependent on the xorg-server but not the utils. I have removed the dependency from the PKDBUILD everytime and it installs and runs without issues.

ainola commented on 2015-02-09 02:12 (UTC)

This very well may also be an Nvidia problem - my quick testing shows that arch+cinnamon+intel laptop works just fine wheras my arch+gnome+nvidia desktop has the issue. Nvidia has been plagued with repainting issues for some time now, and they're very slow with fixing it. Are you running an Nvidia card?

ryanvade commented on 2015-02-09 00:00 (UTC)

The AWT wm flag does not always work. Sometimes it does, others it doesn't.

ainola commented on 2015-02-08 20:25 (UTC)

@ryanvade, it appears that this is an old java bug in regards to undecorated windows. Can anyone that is affected by the problem tell me if running: _JAVA_AWT_WM_NONREPARENTING=1; export _JAVA_AWT_WM_NONREPARENTING before launching technic launcher fixes the issue?

ryanvade commented on 2015-02-08 18:06 (UTC)

Is there a fix for the Grey screen? I asked about it on the github but the developer is a complete ****.

muflone commented on 2015-01-13 16:29 (UTC)

@lakotajames please adopt the package minecraft-technic-launcher and we'll merge the package technic-launcher4 into that which also has a lot of votes.

someoneelse123 commented on 2015-01-11 17:24 (UTC)

Well, it's better than having numbers going backwards (456 -> 211)

ainola commented on 2015-01-11 16:14 (UTC)

Because I'm determined to be a pain in the ass, I'll point out that your update does not register with automated AUR installers (pacaur) due to the new versioning scheme.

someoneelse123 commented on 2015-01-11 12:46 (UTC)

Sorry, I completely forgot about this :( Updated & orphaned. I'll adopt it back if it will get out-of-date before someone else adopts it.

ainola commented on 2015-01-11 12:12 (UTC)

This package should be merged with minecraft-technic-launcher as that is the established package for the latest Technic Launcher. If you're interested in maintaining technic launcher please do pipe up on minecraft-technic-launcher's page as it appears the current maintainer is not.

ainola commented on 2015-01-11 12:09 (UTC)

If you are unable to update, please orphan it. Thank you :)

someoneelse123 commented on 2014-12-31 14:56 (UTC)

@lakotajames Yeah, sorry, I plan to do update, but don't have much time for resurrecting my Arch VM lately :( If you are still using this, I can orphan package and let you maintain it.

Svante commented on 2014-12-31 12:52 (UTC)

It generates an error and a report. Maybe this version is outdated...?

lakotajames commented on 2014-12-27 07:56 (UTC)

I updated to the new launcher here : If you were planning on doing that with this package, just copy mine if you want and let me know and I'll take it off.

Kyahco commented on 2013-12-27 01:48 (UTC)

another updated PKGBUILD:

commented on 2013-11-30 16:59 (UTC)

This version is out of date. A updated PKGBUILD can be found here:

commented on 2013-11-29 19:00 (UTC)

Launcher Build #365 is out - please update the PKGBUILD soon.

someoneelse123 commented on 2013-05-11 11:17 (UTC)

$ diff TechnicLauncher.jar.224 TechnicLauncher.jar.236 $ md5sum TechnicLauncher.jar.224 TechnicLauncher.jar.236 121c6f01e5bf6ace1db3d5eb509cea8e TechnicLauncher.jar.224 121c6f01e5bf6ace1db3d5eb509cea8e TechnicLauncher.jar.236 Version got bumped, but launcher is still same.

quantumphaze commented on 2013-05-11 07:00 (UTC)

Current Launcher Build: 236

someoneelse123 commented on 2013-03-18 21:30 (UTC)

LordHelmchen: Thanks

commented on 2013-03-18 20:19 (UTC)

Changed Source and Version # Maintainer: kozec <kozec at kozec dot com> # Updated by MetaNova <jtxtek at gmail dot com> # Based on minecraft package by Christophe Robin pkgname=minecraft-technic-launcher pkgver=213 pkgrel=1 pkgdesc="Minecraft mod collection and launcher by" arch=(i686 x86_64) license=('gpl2') url="" depends=('java-runtime' 'xorg-server-utils' 'openal') source=(technic-launcher${pkgver}/TechnicLauncher.jar technic-launcher.desktop technic-launcher.png) build() { cd "$srcdir" || return 1 install -D -m755 "${srcdir}/technic-launcher" "${pkgdir}/usr/bin/technic-launcher" install -D -m644 "${srcdir}/TechnicLauncher.jar" "${pkgdir}/usr/share/technic-launcher/technic-launcher.jar" # Desktop launcher with icon install -D -m644 "${srcdir}/technic-launcher.desktop" "${pkgdir}/usr/share/applications/technic-launcher.desktop" install -D -m644 "${srcdir}/technic-launcher.png" "${pkgdir}/usr/share/pixmaps/technic-launcher.png" } md5sums=('6925c510406e38ff40463e6b4128e0d0' '5a95edf785612414fb07deb44b37ec47' '0227e827bd02ed3e720aa0f9edaf6645' 'b27bcba897d293cdf480f7efc9da2863')

someoneelse123 commented on 2013-03-03 23:56 (UTC)

Ok, no problem, but version numbering scheme got changed so pacman may think of this as of downgrade. *upgraded*

MetaNova commented on 2013-03-03 22:52 (UTC)

The Technic Launcher has recently been redone, check the website for the new filenames/versioning.

commented on 2013-01-16 21:18 (UTC)

md5sums=('6925c510406e38ff40463e6b4128e0d0' '5facb08f75c9f79958c1fd7ac4bf8849' '0227e827bd02ed3e720aa0f9edaf6645' 'b27bcba897d293cdf480f7efc9da2863')

someoneelse123 commented on 2013-01-08 18:37 (UTC)

Nobody _ever_ saw my post that I just deleted :D *updated*

MetaNova commented on 2013-01-08 03:40 (UTC)

The version here is out of date, and the remote file name has changed. Here is a PKGBUILD with the appropriate corrections: Hope this helps!

someoneelse123 commented on 2012-11-27 07:21 (UTC)


commented on 2012-11-26 08:21 (UTC)

Gives MD5 error with the technic-launcher-latest.jar