[ Release Testing ] Release .rpm, .deb, .AppImage for testing! #86

holazt · 2018-01-13T13:14:44Z

🎉 I'm very happy to publish this news!
Release .rpm, .deb, .AppImage package for testing!
The download link (files stored for 14 days from now):

fedora 25: https://transfer.sh/BRI9g/flameshot_0.5.0-x86_64.rpm
fedora 26: https://transfer.sh/Y2zFt/flameshot_0.5.0-x86_64.rpm
ubuntu 16.04 LTS: https://transfer.sh/5i6pq/flameshot_0.5.0-x86_64.deb
ubuntu 17.04: https://transfer.sh/zpZEq/flameshot_0.5.0-x86_64.deb
ubuntu 17.10: https://transfer.sh/10uhZ4/flameshot_0.5.0-x86_64.deb
debian 8: https://transfer.sh/nmKIx/flameshot_0.5.0-x86_64.deb
debian 9: https://transfer.sh/c0UTi/flameshot_0.5.0-x86_64.deb
AppImage: https://transfer.sh/5CCBh/flameshot_x86_64_0.5.0.AppImage

Windows portable port (NOTICE official release with support for Windows is 0.6.0. Can try this Windows portable at your own risk, but currently please do not try to report any issues about Windows):

Windows x64: https://transfer.sh/nUPvE/flameshot_win_X64_portable_0.5.0.zip
Windows x86: https://transfer.sh/euVaH/flameshot_win_x86_portable_0.5.0.zip
(under Windows: using msvc compiler.)

build details:
https://travis-ci.org/ZetaoYang/flameshot/builds/328444596
https://ci.appveyor.com/project/ZetaoYang/flameshot/build/job/13o15j8yywjsfu3v
https://ci.appveyor.com/project/ZetaoYang/flameshot/build/job/i70ukfnx9qb27w1b

~~If the link above fails, use the alternate link:~~

~~fedora 25: https://drop.me/omVJwv~~
~~fedora 26: https://drop.me/aq3WwY~~
~~ubuntu 16.04 LTS: https://drop.me/M0xAvW~~
~~ubuntu 17.04: https://drop.me/BxpnwV~~
~~ubuntu 17.10: https://drop.me/Mv7Gw9~~
~~debian 8: https://drop.me/BrxGwg~~
~~debian 9: https://drop.me/ByWAwJ~~
~~AppImage: https://drop.me/o293yD~~
~~(NOTICE official release with support for Windows is 0.6.0. Can try this Windows portable at your own risk, but currently please do not try to report any issues about Windows):~~
~~Windows x64: https://drop.me/oj2Jw7~~
~~Windows x86: https://drop.me/MYmdWj~~

Welcome to test, discuss here.
(When discussing, be sure to explain your system and desktop environment.)

lupoDharkael · 2018-01-13T13:28:41Z

The windows version is still in development and requires some work to be complete. Most things work but keep in mind the official release with support for Windows is 0.6.0.

holazt · 2018-01-13T13:30:15Z

@lupoDharkael Yes, I know. And I wish you can add travis build status badge to README.md

lupoDharkael · 2018-01-13T13:33:23Z

I know you are aware of the situation, but people could try to download the portable version and try to report issues as they don't know it.

probonopd · 2018-01-13T23:30:58Z

Getting on netrunner-desktop-1703-64bit.iso:

live@live-pc:~$ Downloads/flameshot_x86_64_0.5.0.AppImage 
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 267, resource id: 77594629, major code: 55 (CreateGC), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 268, resource id: 77594629, major code: 130 (Unknown), minor code: 3

Why could that be? Attaching the output of qdbus org.kde.KWin /KWin supportInformation in case it helps.

KWin_Support_Information.txt

scoony · 2018-01-14T07:31:52Z

Ubuntu 17.10:

"Launch Flameshot" got no UI? no icon tray? (still start a process)
"Configure Flameshot" looks like working (except for tray icon)

Working perfectly if I use "Take graphical screenshot"

Any way to use the printscreen button?

uuencode · 2018-01-14T10:03:16Z

I agree with Scoony that "Launch Flameshot" shortcut is misleading and useless - "Take Graphical Screenshot" starts the service as well. The .deb file works flawlessly with Ubuntu 17.10 and Xorg. Thank you!

4goodapp · 2018-01-14T14:09:50Z

Debian Buster.
Like @scoony said, Launch Flameshot does nothing (at least, nothing seems to happen, no UI, no tray icon)),

Take Graphical Screenshot works though.

probonopd · 2018-01-15T18:17:19Z

AppImage works here:

probonopd · 2018-01-15T18:18:38Z

When one starts the AppImage, could it directly do the screenshot rather than waiting in the notification area as an icon that could easily be overlooked?

thomas-mc-work · 2018-01-16T10:59:01Z

Don't forget to run sudo make uninstall if you've installed it before with sudo make install.

thomas-mc-work · 2018-01-16T11:03:07Z

Works on Ubuntu 16.04!

The deb package indicates that no dependencies are required. Is that really true?

$ ldd /usr/bin/flameshot 
linux-vdso.so.1 =>  (0x00007fff14664000)
libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 (0x00007f22dd97e000)
libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x00007f22dd436000)
libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 (0x00007f22de185000)
libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (0x00007f22dd2dc000)
libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 (0x00007f22dce06000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f22dca84000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f22dc77b000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f22dc565000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f22dc19b000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f22dbf7e000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f22dbd2b000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f22dba1a000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f22db6e0000)
libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007f22db4bb000)
libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007f22db25d000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f22db043000)
libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 (0x00007f22dadd0000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f22dab84000)
libproxy.so.1 => /usr/lib/x86_64-linux-gnu/libproxy.so.1 (0x00007f22da963000)
libicui18n.so.55 => /usr/lib/x86_64-linux-gnu/libicui18n.so.55 (0x00007f22da501000)
libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 (0x00007f22da16d000)
libpcre16.so.3 => /usr/lib/x86_64-linux-gnu/libpcre16.so.3 (0x00007f22d9f07000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f22d9d03000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f22d9afb000)
/lib64/ld-linux-x86-64.so.2 (0x00007f22de00b000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f22d98f3000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f22d9683000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f22d9461000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f22d91b7000)
libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007f22d8f91000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f22d8d68000)
libxcb-dri3.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 (0x00007f22d8b65000)
libxcb-present.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-present.so.0 (0x00007f22d8962000)
libxcb-sync.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1 (0x00007f22d875b000)
libxshmfence.so.1 => /usr/lib/x86_64-linux-gnu/libxshmfence.so.1 (0x00007f22d8558000)
libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 (0x00007f22d8328000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f22d8116000)
libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007f22d7f13000)
libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f22d7d0d000)
libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007f22d7b0b000)
libxcb-glx.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 (0x00007f22d78f2000)
libxcb-dri2.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0 (0x00007f22d76ed000)
libXxf86vm.so.1 => /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1 (0x00007f22d74e7000)
libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2 (0x00007f22d72d6000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f22de0f2000)
libicudata.so.55 => /usr/lib/x86_64-linux-gnu/libicudata.so.55 (0x00007f22d581f000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f22d561b000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f22d5415000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f22d51f3000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f22d4fd1000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f22d4cf0000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f22d4adc000)

holazt · 2018-01-20T08:58:04Z

In my physical machine Linux mint 18.3 (Cinnamon), running AppImage went wrong and it suddenly crashed when I dragged the drop-down bar in the setup interface. But in Virtual Box Linux mint 18.3 (Cinnamon), it works normally. I don't know what causes it.

./flameshot_x86_64_0.5.0.AppImage 

(flameshot_x86_64_0.5.0.AppImage:6403): Gtk-WARNING **: /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so: symbol xkb_compose_state_get_utf8, version V_0.5.0 not defined in file libxkbcommon.so.0 with link time reference

(flameshot_x86_64_0.5.0.AppImage:6403): Gtk-WARNING **: Loading IM context type 'fcitx' failed

(flameshot_x86_64_0.5.0.AppImage:6403): Gtk-WARNING **: /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so: symbol xkb_compose_state_get_utf8, version V_0.5.0 not defined in file libxkbcommon.so.0 with link time reference

(flameshot_x86_64_0.5.0.AppImage:6403): Gtk-WARNING **: Loading IM context type 'fcitx' failed

(flameshot_x86_64_0.5.0.AppImage:6403): Gtk-WARNING **: /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so: symbol xkb_compose_state_get_utf8, version V_0.5.0 not defined in file libxkbcommon.so.0 with link time reference

(flameshot_x86_64_0.5.0.AppImage:6403): Gtk-WARNING **: Loading IM context type 'fcitx' failed

(flameshot_x86_64_0.5.0.AppImage:6403): GLib-GObject-WARNING **: /build/glib2.0-prJhLS/glib2.0-2.48.2/./gobject/gsignal.c:1250: unable to lookup signal "page-changed" for non instantiatable type 'AtkDocument'

** (flameshot_x86_64_0.5.0.AppImage:6403): WARNING **: Invalid signal type page-changed

./flameshot_x86_64_0.5.0.AppImage: symbol lookup error: /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0: undefined symbol: atk_table_cell_get_type

holazt · 2018-01-20T09:01:25Z

@probonopd Wait for the global shortcut key on it.

holazt · 2018-01-20T09:36:18Z

@lupoDharkael @scoony @uuencode @4goodapp I do not think flameshot needs three .desktop files, just keep one, launch flameshot. Because in the near future, flameshot will support global shortcuts/hotkeys.

probonopd · 2018-01-20T09:44:06Z

The libatk-bridge-2.0.so.0 issue is possibly something caused by the GTK platform plugin. Can you delete, from the AppDir, usr/plugins/platformplugins, and retry?

holazt · 2018-01-20T10:00:53Z

@probonopd Yes, you're right.
Just delete libatk-1.0.so.0 in ./squashfs-root/lib.
And now, it run normally. Thank you.

ATK is an approachable toolkit of functions, and it offers shortcut key services that facilitate the use of computers by physically handicapped people.

flameshot-org/flameshot#86 (comment)

lupoDharkael · 2018-01-20T12:45:03Z

@ZetaoYang I don't know if I will be adding global shortcuts on x11 because users could migrate to Wayland in the future and say "where is the global shortcut configuration?" (wayland doesn't allow to listen for global key events). The tendency is to move towards Wayland and desktops provide a simple way to configure shortcuts, the project just needs tutorials and a clear user manual.

A few months ago the project used to have just one .desktop but a few users asked for a desktop file to just start the process as some desktop environment allow the use them instead of a command to defined what programs to launch at startup.

The config desktop file is required as you can disable the trayicon in configuration, some users don't use the terminal so the desktop file is the only intuitive way they have to open the configuration window.

Do not run ldd on platformthemes, don't bundle their dependencies flameshot-org/flameshot#86 (comment)

holazt · 2018-01-21T03:47:05Z

@lupoDharkael Wayland integration into the major Desktop Environments is far from mature. The hotkey does not work under Wayland, but user can let desktop environment handle the registration of shortcuts/hotkeys.
Just use your desktop evironment to bind some shortcuts/hotkeys to flameshot gui or flameshot config.

yermulnik · 2018-01-21T22:15:39Z

Any chance for Ubuntu 14.04?

probonopd · 2018-01-21T23:11:13Z

Any chance for Ubuntu 14.04?

The AppImage should work on Ubuntu 14.04. Did you test it?

yermulnik · 2018-01-22T10:42:46Z

@probonopd just tried. It outputs text to console, but does nothing when ran with gui arg. Generally it does nothing at all except outputting help messages to console. E.g.:

$> /tmp/yz/flameshot_x86_64_0.5.0.AppImage full
you have to set a valid flag:

Usage: /tmp/yz/flameshot_x86_64_0.5.0.AppImage full [full-options]

Options:
  -p, --path <path>           Path where the capture will be saved
  -c, --clipboard             Save the capture to the clipboard
  -d, --delay <milliseconds>  Delay time in milliseconds
  -r, --raw                   Print raw PNG capture
  -h, --help                  Displays this help
$> /tmp/yz/flameshot_x86_64_0.5.0.AppImage gui
$>

probonopd · 2018-01-22T19:12:44Z

It doesn't do a screenshot directly, but shows an icon in the icon bar. At least it does that for me...

yermulnik · 2018-01-22T19:15:18Z

But it does not for me unfortunately =( Thanks anyway =)

holazt · 2018-01-23T03:48:05Z

@yermulnik You have to run flameshot_x86_64_0.5.0.AppImage first before you can use these flags.
For instance,

./flameshot_x86_64_0.5.0.AppImage &; (Must ensure that flameshot has been running.)
./flameshot_x86_64_0.5.0.AppImage gui or ./flameshot_x86_64_0.5.0.AppImage full -c.

Then enjoy!

yermulnik · 2018-01-23T13:57:29Z

Wow, this time it worked! Thanks to all of who helped =)

yermulnik · 2018-01-23T14:33:06Z

Though the icon in systray doesn't show up most of the time when I run AppImage =( Everything else work just fine =)

probonopd · 2018-01-23T22:13:06Z

Again, I would prefer that when one starts the application it would directly do the screenshot rather than waiting in the notification area...

yermulnik · 2018-01-23T22:23:07Z

I'd prefer both: systray and direct call. But not the thing when user have to start the app and then call it once again to make a job.

holazt · 2018-01-24T02:38:55Z

@probonopd I found the root of that problem.It is caused by ./squashfs-root/usr/lib/libxkbcommon.so.0 and ./squashfs-root/usr/lib/libatk-1.0.so.0. The workaround is to delete them.
But If there is a dependency problem, users themselves need to install libxkbcommon.
Debian/Ubuntu: sudo apt-get install libxkbcommon0
Fedora: dnf install libxkbcommon
openSUSE: zypper install libxkbcommon0

thanhnha1103 · 2018-01-25T04:37:35Z

Awesome! all features worked well.
Please add "Add text feature"

probonopd · 2018-01-25T21:39:46Z

But If there is a dependency problem, users themselves need to install libxkbcommon.

That is not how an AppImage is supposed to work...

CHBMB · 2018-01-25T21:53:15Z

chmod a+x ./flameshot_x86_64_0.5.0.AppImage
./flameshot_x86_64_0.5.0.AppImage
./flameshot_x86_64_0.5.0.AppImage gui

Works on Solus Budge. No icon in the notification try but able to use the tool well. Have to open two terminals one to run the first two commands and then a second to run the gui

4sStylZ · 2018-01-30T15:22:57Z

Hi. I got a Not Found when trying to DL the Ubuntu 16.04 LTS.
Can someone provide me another link ? :)

holazt · 2018-01-31T01:44:34Z

@4sStylZ ubuntu 16.04 LTS: https://drop.me/M0xAvW

Philippe734 · 2018-02-08T09:27:40Z

Ubuntu 14.04
Day 1 : the appimage 0.5 works fine !
Day 2 : But the appimage don't work, nothing was change in the system. When I run ./flameshot_x86_64_0.5.0.AppImage gui, it's happen nothing, exit immediately, no return, no error in terminal.

yermulnik · 2018-02-08T09:42:52Z

@Philippe734 I've got similar situation: it does work, but the icon in notification area doesn't appear most of the time.

4sStylZ · 2018-02-08T15:36:57Z

Thank you very much @ZetaoYang

holazt · 2018-02-09T11:14:12Z

Before asking questions, be sure to explain your system and desktop environment .

View system information: run cat /etc/issue.
View desktop environment information: run echo $XDG_CURRENT_DESKTOP.

@Philippe734
For screenshot tools, I prefer to graphically interact than command line interface.

Please ensure that flameshot has been running. And then you can run ./flameshot_x86_64_0.5.0.AppImage gui.

@yermulnik
Ubuntu 14.04 canceled the system tray whitelist mechanism, resulting in the use of traditional system tray technology program can not display the tray icon.

workaround:

For Ubuntu 14.04~17.10, can install indicator-systemtray-unity (Only Unity desktop environment)

sudo apt-add-repository ppa:fixnix/indicator-systemtray-unity  
sudo apt-get update
sudo apt-get install indicator-systemtray-unity

Once installed, log out and log in and Indicator Systemtray Unity should start automatically.

Settings

To change the mode position: press the middle mouse button on the indicator.
The horizontal position can be changed: scrolling the mouse over the indicator.

Settings can be changed in gsettings:/net/launchpad/indicator/systemtray (use dconf-editor).
more details: http://www.webupd8.org/2015/05/on-demand-system-tray-for-ubuntu.html
2.

yermulnik · 2018-02-09T11:44:54Z

@ZetaoYang thank you for detailed explanation. the thing is that sometimes icon does appear, but most of the time it does not.

Ubuntu 14.04 canceled the system tray whitelist mechanism, resulting in the use of traditional system tray technology program can not display the tray icon.

Any other workaround on flameshot side available? I'm not kind of switching to Unity just because one single app (a wonderful app I wish to use!) doesn't show up in notification area (I've got about 15 other apps running and showing up in notification area correctly).

Philippe734 · 2018-02-12T12:26:44Z

For Ubuntu 14.04, you're right ZetaoYang, we need to run the appimage before the gui. Sorry. The AppImage 0.5 works fine with 14.04. So with command line the trick is :

Run in a terminal: ./flameshot_x86_64_0.5.0.AppImage
Run in other terminal: ./flameshot_x86_64_0.5.0.AppImage gui

probonopd · 2018-02-12T18:09:02Z

Can this be scripted in the form of a custom AppRun script so that one needs no terminal to use it?

holazt · 2018-02-13T04:01:19Z

For Ubuntu 14.04 Unity, the AppImage tray icon does not display properly. Even if indicator-systemtray-unity is installed, clicking the icon will not take a direct screenshot, only the right-click menu will be displayed.

For Ubuntu 16.04 Unity, similar to the above situation.

For Ubuntu 17.10 Gnome, the AppImage tray icon does not display.

For Linux Mint 18.3 Cinnamon: it works fine.

@probonopd I think users can start flameshot using their own scripts outside AppImage. Even can bind desktop shortcuts.
I would suggest that the author add a screenshot submenu item in the flameshot right-click menu.

lupoDharkael · 2018-02-24T11:55:18Z

https://github.com/lupoDharkael/flameshot/releases/tag/v0.5.1

Do not run ldd on platformthemes, don't bundle their dependencies flameshot-org/flameshot#86 (comment)

holazt mentioned this issue Jan 13, 2018

Add .deb or .snap for Ubuntu #46

Closed

holazt changed the title ~~[Release Testing ] Release .rpm, . deb, .AppImage and Windows portable port for testing!~~ [Release Testing ] Release .rpm, . deb, .AppImage for testing! Jan 13, 2018

holazt changed the title ~~[Release Testing ] Release .rpm, . deb, .AppImage for testing!~~ [ Release Testing ] Release .rpm, . deb, .AppImage for testing! Jan 13, 2018

holazt changed the title ~~[ Release Testing ] Release .rpm, . deb, .AppImage for testing!~~ [ Release Testing ] Release .rpm, .deb, .AppImage for testing! Jan 14, 2018

lupoDharkael added the Help Wanted Issues that the main devs need some help from community. Similar to "Good first issue" but harder. label Jan 14, 2018

holazt mentioned this issue Jan 20, 2018

Please provide a Linux AppImage for download #39

Closed

probonopd added a commit to probonopd/linuxdeployqt that referenced this issue Jan 20, 2018

Do not run ldd on platformthemes, don't bundle their dependencies

e38262b

flameshot-org/flameshot#86 (comment)

probonopd mentioned this issue Jan 20, 2018

Do not run ldd on platformthemes, don't bundle their dependencies probonopd/linuxdeployqt#217

Merged

probonopd added a commit to probonopd/linuxdeployqt that referenced this issue Jan 20, 2018

Do not run ldd on platformthemes, don't bundle their dependencies (#217)

fd33511

Do not run ldd on platformthemes, don't bundle their dependencies flameshot-org/flameshot#86 (comment)

rassie mentioned this issue Feb 19, 2018

Wrong screen captured #119

Open

lupoDharkael closed this as completed Feb 24, 2018

turmary pushed a commit to turmary/linuxdeployqt that referenced this issue Jul 31, 2022

Do not run ldd on platformthemes, don't bundle their dependencies (#217)

e94cdd5

Do not run ldd on platformthemes, don't bundle their dependencies flameshot-org/flameshot#86 (comment)

[ Release Testing ] Release .rpm, .deb, .AppImage for testing! #86

[ Release Testing ] Release .rpm, .deb, .AppImage for testing! #86

Comments

holazt commented Jan 13, 2018 • edited

lupoDharkael commented Jan 13, 2018

holazt commented Jan 13, 2018 • edited

lupoDharkael commented Jan 13, 2018

probonopd commented Jan 13, 2018

scoony commented Jan 14, 2018

uuencode commented Jan 14, 2018

4goodapp commented Jan 14, 2018

probonopd commented Jan 15, 2018 • edited

probonopd commented Jan 15, 2018 • edited

thomas-mc-work commented Jan 16, 2018

thomas-mc-work commented Jan 16, 2018

holazt commented Jan 20, 2018 • edited

holazt commented Jan 20, 2018

holazt commented Jan 20, 2018

probonopd commented Jan 20, 2018

holazt commented Jan 20, 2018 • edited

lupoDharkael commented Jan 20, 2018 • edited

holazt commented Jan 21, 2018 • edited

yermulnik commented Jan 21, 2018

probonopd commented Jan 21, 2018 • edited

yermulnik commented Jan 22, 2018

probonopd commented Jan 22, 2018

yermulnik commented Jan 22, 2018

holazt commented Jan 23, 2018

yermulnik commented Jan 23, 2018

yermulnik commented Jan 23, 2018

probonopd commented Jan 23, 2018 • edited

yermulnik commented Jan 23, 2018

holazt commented Jan 24, 2018

thanhnha1103 commented Jan 25, 2018

probonopd commented Jan 25, 2018

CHBMB commented Jan 25, 2018 • edited

4sStylZ commented Jan 30, 2018

holazt commented Jan 31, 2018

Philippe734 commented Feb 8, 2018 • edited

yermulnik commented Feb 8, 2018

4sStylZ commented Feb 8, 2018

holazt commented Feb 9, 2018

workaround:

Settings

yermulnik commented Feb 9, 2018

Philippe734 commented Feb 12, 2018

probonopd commented Feb 12, 2018

holazt commented Feb 13, 2018

lupoDharkael commented Feb 24, 2018

holazt commented Jan 13, 2018 •

edited

holazt commented Jan 13, 2018 •

edited

probonopd commented Jan 15, 2018 •

edited

probonopd commented Jan 15, 2018 •

edited

holazt commented Jan 20, 2018 •

edited

holazt commented Jan 20, 2018 •

edited

lupoDharkael commented Jan 20, 2018 •

edited

holazt commented Jan 21, 2018 •

edited

probonopd commented Jan 21, 2018 •

edited

probonopd commented Jan 23, 2018 •

edited

CHBMB commented Jan 25, 2018 •

edited

Philippe734 commented Feb 8, 2018 •

edited