still usb keyboard and mouse frezing problems.
still usb keyboard and mouse frezing problems.
After update and reboot, Gnome is restarting again and again after login. It begins to show desktop, some app, but then goes black and I have to start session again. Working good with i3, so it seems a Gnome problem.
dmesg show this error:
[ 90.836400] gnome-shell: segfault at 30 ip 00007fa454796f42 sp 00007ffdd47340d0 error 4 in libsoup-2.4.so.1.8.0[7fa454787000+4c000]
[ 96.624789] gnome-shell: segfault at 30 ip 00007f69806cdf42 sp 00007ffe5c0d55e0 error 4 in libsoup-2.4.so.1.8.0[7f69806be000+4c000]
I completely forgot that vlc-nightly has been dropped. Added information in the Wiki post in case there are still people using this package.
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?
[Stable Update] 2019-03-21 - Kernels, Deepin, Browsers, Pamac, Plasma, Python
[Stable Update] 2019-03-29 - Kernels, Gnome, LibreOffice, Mesa, Budgie, Browsers, Qt
thunar dies at least once a day
[Stable Update] 2019-04-03 - Mate, KDE-Dev, Cinnamon, Deepin, Browsers
Create from template menu bug
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.
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.