Yes, this is what I did. I back to the stable version of Vlc
I post here because I think the problem is related to the latest updates. I'm relaying here a small issue that users report on manjaro.fr. I'm on testing branch since long time and with xfce4-gtk3 .
2019-03-14 21:38] [PACMAN] Running 'pacman -Syu'
- Some have problems with xfce4-screenshooter in unstable with a message such ' "Unable to open ~/Write images: is a folder"'. I have no problem, but it's look like a bug.
2/ In Thunar, a right clic > create new file give a very small empty window and I can't do anything with it.
xfce4-popup-applicationsmenu -pworks fine. I can see a window under the cursor with all options to create a new file.
It seams that some unstable and testing users are impacted with this issue, but not today users with stable.
Of course, I did not modify anything and it works before some of us detect this small problem.
Any idea ?
I noticed I have this problem in Testing
For the screenshooter problem see this thread: Saving a screenshot fails after upgrading to xfce4-screenshooter-1.9.4-1.
Downgraded to last libsoup version and Gnome is working again
I can confirm this on my side in my XFCE VM. It works fine on the desktop, but not inside a Thunar window. Perhaps a regression introduced when GTK3 got upgraded to version 3.24.7.
This issue is also on Arch Linux, according to their forum. They worked around the issue by downgrading gtk3 to a previous version.
Reported to upstream too: https://bugzilla.xfce.org/show_bug.cgi?id=15200
EDIT: I could work around the issue by downgrading first lib32-gtk3-classic, then gtk3-classic from 3.24.7-1 to 3.24.5-1. I rebooted right after doing the downgrade, although a simple log out-log in might be enough to fix the issue. (Most likely downgrading the regular gtk3 package, if you use this one instead, will produce the same result.)
I do not guarantee that downgrading gtk3-classic/gtk3 packages will not cause other issues elsewhere.
? Downgraded to last? From which version to which version more precisely?
Haven't noticed this as my prt sc key is mapped to
xfce4-screenshooter -fs [location of screenshot folder] -- using this instead may work.
Confirmed on my desktop as well -- seeing it on all themes.
I noticed in the upstream bug report, @ToZ also mentioned a slight "scrollable" context menu on individual files -- I can also confirm seeing that. Pinging @korealinux to see if you're seeing the same items coming from a rolling update position.
I noticed on my install I still have
gtk3)...I'm coming from v18's iso...is
gtk3 still not quite ready for "prime time" yet?
GTK3, or a full GTK3 XFCE desktop?
Anyway, it looks more like an unexpected issue introduced with changes within GTK3 than XFCE (or Thunar in this case) not being ready. It worked fine before, right?
Simply the package
gtk3. I noticed
gtk3-classic is also known as gtk3-mushrooms whose maintainer is apparently looking for a replacement in the next few months...
Sorry, I was playing with my new SSD. I am following the thread but not rolling at the moment. We will resume rolling momentarily. ~
I get it but if I stuff around a little it disappears. Try this: (right) click to open the menu then close it. Click the same file (or a different one but still in the same window) and scroll up. Then the menu consistently becomes solid/unscrollable for me. Once this happens opening the menu from any file in that window works as it should (i.e. does not have a scroll) until the window is closed. There are a couple of other methods to trigger the correct menu behaviour but they are less consistent. (By the way this differs a little from what is described in the bug report...)
No moss on me.
That was my real KDE+GNOME on-SSD. This afternoon i have belatedly also updated my two Testing VMs [both = KDE+Cinnamon; one VM is a clone of t'other]. I updated one in tty2, but the clone i did within the desktop using Pamac. BOTH went just fine, even though it was a big update involving
systemd* & Plasma. It seems more & more that Pamac has become pretty fine even for these major changes... despite our collective "excitement" in the forum some weeks back.
* From a previous Testing Update; i'd not done these VMs for a few weeks.
I get Create Document / Empty File and it works, see scrn shots. 1.8.4git-955b94a Thunar ver.
Are you using gtk3 packages? Version of your
Yes, I am:
Classic = 3.24.5-1
Desktop = 4.13.2-14
gtk3-classic 3.24.7-1 is affected, it's not a big deal as I'll just wait for an upstream fix. Maybe worth mentioning as a "known issue" if it gets pushed to a stable announcement but again, minor issues.
I'm back from #clt2019. Please check if pamac 7.3.5-2 fixes the reported issues ...
Sorry, still the same for me . Still enable to create new file with right clic into Thunar. I did relog into session. Same small empty window.
$ pacman -Q pamac pamac-gtk 7.3.5-2 $ pamac info pamac-gtk Nom : pamac-gtk Version : 7.3.5-2 Description : A Package Manager based on libalpm with AUR and Appstream support URL : https://gitlab.manjaro.org/applications/pamac Licences : GPL3 Dépôt : extra Taille : 575,5 ko Dépend de : pamac-cli vte3>=0.38 gtk3>=3.22 Requis par : pamac-dev-tray-appindicator Fournit : pamac=7.3.5-2 Remplace : pamac Est en conflit avec : pamac pamac-aur Paqueteur : Philip Mueller <firstname.lastname@example.org> Compilé le : 18/03/2019 Installé le : 18/03/2019 Motif d’installation : Explicitement installé
Downgraded from 2.66.0-1 to 2.64.2-1
It didn't work on my side, and I take the blame for it, because I completely missed a very important detail in my previous explanation to make it work. Reminder here.
vercmp now works properly since we are using $1 instead of $2 in post-installation. It doesn't fail and show an error. The problem now is that we are not using the right comparison, so the test just doesn't execute. Let me explain.
Currently, the comparison used is "less than", or -lt in bash. We are testing if the value given by vercmp is lesser than 0. It is only the case if the version given in the first argument (here, it is $1) is a lower version than the second argument of vercmp (see the manual of vercmp).
However, in the post_install() function, $1 is the version of the package that is installed. Thus, what is happening here is that vercmp is comparing 7.3.5-2 vs 7.3.5-2 and since both versions are the same, vercmp returns 0 as the output. Is 0 is lesser than 0? NO. Therefore, the instruction in the first if is not executed at all.
So instead of using "less than", we could use "less or equal than", or -le in bash. Instead of
if [ "$(vercmp $1 7.3.5-3)" -lt 0 ]; then, we would have something like
if [ "$(vercmp $1 7.3.5-3)" -le 0 ]; then. (I'm taking into account the next rebuild.)
@philm Sorry for the lost time because of an error in my logic.
Here's the details for the VM I used to test out the rebuild. The .pacsave didn't get replaced.
Pamac details - Manjaro Gnome
Synchronizing package databases... Starting full system upgrade... Resolving dependencies... Checking inter-conflicts... Downloading systemd-libs (241.607-1-x86_64)... Downloading e2fsprogs (1.45.0-1-x86_64)... Downloading systemd (241.607-1-x86_64)... Downloading nspr (4.21-1-x86_64)... Downloading linux419 (4.19.29-1-x86_64)... Downloading lib32-pcre (8.43-1-x86_64)... Downloading lib32-systemd (241.607-1-x86_64)... Downloading at-spi2-core (2.32.0-1-x86_64)... Downloading atk (2.32-1-x86_64)... Downloading dconf (0.32.0-1-x86_64)... Downloading glib-networking (22.214.171.124-1-x86_64)... Downloading libsoup (2.66.0-1-x86_64)... Downloading gtk3 (3.24.7-1-x86_64)... Downloading baobab (3.32.0-1-x86_64)... Downloading double-conversion (3.1.4-1-x86_64)... Downloading file-roller (3.32.0-1-x86_64)... Downloading firefox (66.0-0-x86_64)... Downloading gtksourceview4 (4.0.3-1-x86_64)... Downloading gobject-introspection-runtime (1.60.0-1-x86_64)... Downloading gedit (3.32.0-1-x86_64)... Downloading geocode-glib (3.26.1-1-x86_64)... Downloading upower (0.99.10-1-x86_64)... Downloading libwbclient (4.9.5-1-x86_64)... Downloading tevent (1:0.9.39-1-x86_64)... Downloading ldb (1:1.4.6-1-x86_64)... Downloading smbclient (4.9.5-1-x86_64)... Downloading lua52-lpeg (1.0.2-1-x86_64)... Downloading grilo (0.3.7-1-x86_64)... Downloading webkit2gtk (2.24.0-1-x86_64)... Downloading gnome-control-center (3.30.3+4+g26287234b-1-x86_64)... Downloading qt5-base (5.12.1-3.1-x86_64)... Downloading libdazzle (3.32.0-1-x86_64)... Downloading protobuf (3.7.0-1-x86_64)... Downloading libphonenumber (8.10.6-1-x86_64)... Downloading ntp (4.2.8.p13-2-x86_64)... Downloading pamac-common (7.3.5-2-x86_64)... Downloading pamac-cli (7.3.5-2-x86_64)... Downloading udisks2 (2.8.2-1-x86_64)... Downloading yelp-xsl (3.32.0-1-any)... Checking keyring... Checking integrity... Loading packages files... Checking file conflicts... Checking available disk space... Running pre-transaction hooks... Remove Firefox Distribution Settings Save Linux kernel modules Removing pamac (7.3.4-2)... /etc/pamac.conf installed as /etc/pamac.conf.pacsave. Upgrading systemd-libs (241.588-1 -> 241.607-1)... Upgrading e2fsprogs (1.44.6-1 -> 1.45.0-1)... Upgrading at-spi2-core (2.30.1-1 -> 2.32.0-1)... Upgrading atk (2.30.0-1 -> 2.32-1)... Upgrading at-spi2-atk (2.30.1-1 -> 2.32.0-1)... Upgrading dconf (0.30.1-1 -> 0.32.0-1)... Upgrading gtk-update-icon-cache (3.24.5-1 -> 3.24.7-1)... Upgrading systemd (241.588-1 -> 241.607-1)... Upgrading tdb (1.3.16-1 -> 1.3.18-1)... Upgrading glib-networking (2.58.0-1 -> 126.96.36.199-1)... Upgrading libsoup (2.64.2-1 -> 2.66.0-1)... Upgrading gtk3 (3.24.5-1 -> 3.24.7-1)... Upgrading baobab (3.30.0-1 -> 3.32.0-1)... Upgrading double-conversion (3.1.1-1 -> 3.1.4-1)... Upgrading file-roller (3.30.1-1 -> 3.32.0-1)... Upgrading nspr (4.20-1 -> 4.21-1)... Upgrading firefox (65.0.2-1 -> 66.0-0)... Installing gtksourceview4 (4.0.3-1)... Upgrading gobject-introspection-runtime (1.58.3-1 -> 1.60.0-1)... Upgrading gedit (3.30.2-1 -> 3.32.0-1)... Upgrading geocode-glib (3.26.0-1 -> 3.26.1-1)... Upgrading upower (0.99.9-1 -> 0.99.10-1)... Upgrading libwbclient (4.9.4-2 -> 4.9.5-1)... Upgrading talloc (2.1.14-1 -> 2.1.16-1)... Upgrading tevent (1:0.9.37-1 -> 1:0.9.39-1)... Upgrading ldb (1:1.4.3-1 -> 1:1.4.6-1)... Upgrading smbclient (4.9.4-2 -> 4.9.5-1)... Upgrading lua52-lpeg (1.0.1-2 -> 1.0.2-1)... Upgrading grilo (0.3.6-1 -> 0.3.7-1)... Upgrading webkit2gtk (2.22.7-1 -> 2.24.0-1)... Upgrading gnome-control-center (3.30.3-1 -> 3.30.3+4+g26287234b-1)... Upgrading qt5-base (5.12.1-2.1 -> 5.12.1-3.1)... Upgrading kvantum-manjaro (0.12.0-1 -> 0.13.0-1)... Upgrading lib32-pcre (8.42-1 -> 8.43-1)... Upgrading lib32-systemd (241.588-1 -> 241.607-1)... Upgrading libdazzle (3.30.2-1 -> 3.32.0-1)... Upgrading libgexiv2 (0.10.8-2 -> 0.12.0-1)... Upgrading protobuf (188.8.131.52-1 -> 3.7.0-1)... Upgrading libphonenumber (8.10.1-2 -> 8.10.6-1)... Upgrading linux419 (4.19.28-1 -> 4.19.29-1)... Upgrading linux419-virtualbox-guest-modules (6.0.4-10 -> 6.0.4-11)... Upgrading ntp (4.2.8.p12-2 -> 4.2.8.p13-2)... Installing pamac-common (7.3.5-2)... Configuring pamac-common... ==> An authentication agent is required Cinnamon, Deepin, GNOME, GNOME Flashback, KDE, LXDE, LXQt, MATE and Xfce have an authentication agent already. See https://wiki.archlinux.org/index.php/Polkit#Authentication_agents for other desktop environments. Installing pamac-cli (7.3.5-2)... Installing pamac-gtk (7.3.5-2)... Configuring pamac-gtk... ==> Enable Pamac Updates Indicator via Gnome Tweak Upgrading systemd-sysvcompat (241.588-1 -> 241.607-1)... Upgrading terminus-font (4.46-1.1 -> 4.47-2)... Upgrading udisks2 (2.8.1-1 -> 2.8.2-1)... Upgrading yelp-xsl (3.30.1-1 -> 3.32.0-1)... Running post-transaction hooks... Updating linux419 module dependencies... Updating linux419 initcpios... ==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default' -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64.img ==> Starting build: 4.19.29-1-MANJARO -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [resume] -> Running build hook: [filesystems] ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64.img ==> Image generation successful ==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback' -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect ==> Starting build: 4.19.29-1-MANJARO -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [resume] -> Running build hook: [filesystems] ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64-fallback.img ==> Image generation successful Updating Grub-Bootmenu Generating grub configuration file ... Found theme: /usr/share/grub/themes/manjaro/theme.txt Found linux image: /boot/vmlinuz-4.19-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img Found memtest86+ image: /boot/memtest86+/memtest.bin done Copy Firefox Distribution Settings Updating fontconfig cache... Updating GIO module cache... Compiling GSettings XML schema files... Probing GTK3 input method modules... Updating icon theme caches... Restore Linux kernel modules e[1;1me[1;32m==>e[1;0me[1;1m Warning: -> Kernel has been updated. Modules of the current kernel -> have been backed up so you can continue to use your -> computer. However, the new kernel will only work -> at next boot. e[1;0m e[1;0m Updating journal message catalog... Reloading system manager configuration... Updating udev hardware database... Applying kernel sysctl settings... Creating system user accounts... Creating temporary files... Reloading device manager configuration... Arming ConditionNeedsUpdate... Updating the info directory file... Updating the desktop file MIME type cache... Updating the MIME type database... Updating X fontdir indices... Transaction successfully finished.
Btw, it was not necessary to use $1 instead of $2 in the post_upgrade() function in the .install. For the post_upgrade() function, $1 is the version of the new package (the one replacing) and $2 is the version of the old package (the one being replaced). Quoting
man PKGBUILD :
post_upgrade Run after files are extracted. Two arguments are passed in this order: new package full version string, old package full version string.
It is necessary to use $1 in post_install() because there is only one argument passed in this function, the version of the package being installed.
post_install Run right after files are extracted. One argument is passed: new package full version string.
In this case, using the same line for the if in both post_install() and post_upgrade() doesn't seems to be much a problem, because the instruction executed if the condition is verified will only do something if the .pacsave file exists and if it doesn't, it does nothing at all.
But this could be something significant in the future if you have to use arguments passed in post_install()/post_upgrade()/etc.