How long can we delay this update, before the next stable release update will show the light?

Not if you go about it the smart and responsible way. I have a fairly customized setup, and yet here I am, running Plasma 6, with my old window decorations, my old Plasma styles — several of them — and my old kvantum theme. :point_down:

But of course, if people just open up the pamac-gui, run the update process, and cannot even be bothered looking at the Stable Updates threads, then yes, there will be problems.

Look, Plasma 6 isn’t perfect, and yes, there are several bugs — I’ve discovered a whole slew of new (but small) 15-minute bugs, even — but if you consider how much work has gone into getting both Plasma 6 and the KDE Frameworks 6 out by a deadline — which in and of itself is not such a good strategy — then it’s amazing how stable and usable Plasma 6 is.

Granted, I’m still on X11 because there are still some obvious issues with qt6 on Wayland, but if you update the smart and responsible way, and you read up on the caveats on the Stable Updates thread, then there’s very little to worry about.

Back when we upgraded from Plasma 5.24 LTS to 5.25, I had far greater problems, and Plasma 5.25 was completely unusable for myself and for many others — about half of the Plasma users on this forum. At my own responsibility, I then kept my system in a partial-upgrade state by skipping all Plasma-related updates until 5.27 LTS was released, and several other people here did the same. But compared to the transition from 5.24 LTS unto the for many people broken 5.25, the upgrade from 5.27.11 to 6.0.4 now was a breeze — pun not intended.

Again, there are bugs, but they are all fairly small and mostly cosmetic ones. Everyone else who’s had problems with the upgrade from 5.27.11 to 6.0.4 — I’m not going to be addressing GNOME or Xfce, because I don’t use either of those — owes those problems to not having done their homework and not updating responsibly.

There’s a reason why I wrote this little HowTo:point_down:

But nooo, people are allergic to the command line. They don’t want to update from a tty. They want point & click. Well, guess what, they’re the ones with all the issues now, and as usual, we see dozens of threads popping up that are all about the same issues, because nobody bothers to even check whether their issue has already been reported, let alone that the solution and other advice was already given on the Stable Updates thread from before they updated their systems.

Look guys, if you don’t want to be responsible, then that’s all fine. But then don’t come crying that Manjaro broke your system. That’s what the word responsibility is all about. We can put the food on the table in front of you, along with a spoon and a fork. But if you’re going to be spitting it out, then you’re going to stay hungry, and then that’s not our fault.

Switch to the Breeze window decorations, application style and Plasma style before the update. Then log out, reboot, and instead of logging in at the GUI, log in at a tty, delete the contents of your ~/.cache/, stop sddm — you should definitely know how to do that by now on a systemd-based system — and run the update. Then reboot again, log into Plasma and restore your theme settings.

Don’t believe everything you read on the internet. :stuck_out_tongue:


Great and all but what about my trackpad? was this my fault, do i have any solution at all?

I never said that every problem anyone has after updating would be the result of an irresponsible updating strategy. There are bugs, and trackpad support sits much deeper than Plasma.

Plasma is only a user interface, and the trackpad support is actually handled at a much lower level in the operating system — possibly the kernel.

I still dont understand how you cannot use synaptics on plasma 6.

As far as I know there is nothing to break it.

It simply does not provide the configuration GUI.

(and when I last saw your synaptics config … all it did was enable tap-to-click)

As mentioned before, make sure you have xf86-input-synaptics installed.
Otherwise of course the synaptics driver cannot be used.

Am i missing the point, it works fine until the plasma6 update, so it is the update. Maybe you ar referring to much deeper things but im still stuck.

No it didn’t, it had about 5 tabs you obviously didn’t see.

Yes xf86-input-synaptics it is installed and we have checked if its being used, it is not.

@cscs if you know of a way to get synaptic to work even without the GUI (which is fine i dont mind) Then please please show me how :smile:

Yes it did, and it couldnt possibly have tabs … it was a single text file.

But I accept you want to include the options you set in the graphical interface and not that config file you showed.

Then I think you should revisit that config file you had.

At least thats what I think would make sense to try if you must use synaptics.

In case the original scenario was somehow unclear I will quote a KDE dev on the subject:

(no you will not be able to wait long enough to get that GUI for synaptics back)

If you have the package installed. And its not automatically being used.
Then make sure to use a configuration file like:

Section "InputClass"
    Identifier "touchpad"
    Driver "synaptics"
    MatchIsTouchpad "on"
        Option "TapButton1" "1"
        Option "TapButton2" "3"
        Option "TapButton3" "2"
        Option "VertEdgeScroll" "on"
        Option "VertTwoFingerScroll" "on"
        Option "HorizEdgeScroll" "on"
        Option "HorizTwoFingerScroll" "on"
        Option "CircularScrolling" "on"
        Option "CircScrollTrigger" "2"
        Option "EmulateTwoFingerMinZ" "40"
        Option "EmulateTwoFingerMinW" "8"
        Option "CoastingSpeed" "0"
        Option "FingerLow" "30"
        Option "FingerHigh" "50"
        Option "MaxTapTime" "125"

1 Like

emmm, ok :confused:

Ok well lets take another look. I have a duel boot with one pre-plasma6 (call it install1) and one post update (install2). The trackpad is working just as it always has on install 1, i can grab whatever setting or config files you suggest from install 1 and move them to install 2.

Im seriously up for trying anything atm. Where can we do this ? not on this thread i assume.

EDIT: sorry missed your edit, but ok i shall try that now.


something has happened, i think it is almost working, maybe just some tinkering in some setting file somewhere and i can get the coasting to work as well but the problem of the 2 finger scrolling does actually seem to be fixed! (touch wood)

The synaptic driver is also showing as being used this time,

❱xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Hailuck Co.,Ltd PTP TouchPad Mouse        id=14   [slave  pointer  (2)]
⎜   ↳ Hailuck Co.,Ltd PTP TouchPad Touchpad     id=17   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
    ↳ SINO WEALTH USB KEYBOARD                  id=10   [slave  keyboard (3)]
    ↳ SINO WEALTH USB KEYBOARD System Control   id=11   [slave  keyboard (3)]
    ↳ SINO WEALTH USB KEYBOARD Consumer Control id=12   [slave  keyboard (3)]
    ↳ Hailuck Co.,Ltd PTP TouchPad Keyboard     id=13   [slave  keyboard (3)]
    ↳ Hailuck Co.,Ltd PTP TouchPad System Control       id=15   [slave  keyboard (3)]
    ↳ Hailuck Co.,Ltd PTP TouchPad Consumer Control     id=16   [slave  keyboard (3)]
    ↳ Dell WMI hotkeys                          id=18   [slave  keyboard (3)]
    ↳ Dell AIO WMI hotkeys                      id=19   [slave  keyboard (3)]

⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼ /home/greg ⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼
❱xinput list-props 14
Device 'Hailuck Co.,Ltd PTP TouchPad Mouse':
        Device Enabled (179):   1
        Coordinate Transformation Matrix (181): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        libinput Natural Scrolling Enabled (310):       0
        libinput Natural Scrolling Enabled Default (311):       0
        libinput Scroll Methods Available (312):        0, 0, 1
        libinput Scroll Method Enabled (313):   0, 0, 0
        libinput Scroll Method Enabled Default (314):   0, 0, 0
        libinput Button Scrolling Button (315): 2
        libinput Button Scrolling Button Default (316): 2
        libinput Button Scrolling Button Lock Enabled (317):    0
        libinput Button Scrolling Button Lock Enabled Default (318):    0
        libinput Middle Emulation Enabled (319):        0
        libinput Middle Emulation Enabled Default (320):        0
        libinput Rotation Angle (293):  0.000000
        libinput Rotation Angle Default (294):  0.000000
        libinput Accel Speed (321):     -0.400000
        libinput Accel Speed Default (322):     0.000000
        libinput Accel Profiles Available (323):        1, 1, 1
        libinput Accel Profile Enabled (324):   1, 0, 0
        libinput Accel Profile Enabled Default (325):   1, 0, 0
        libinput Accel Custom Fallback Points (326):    <no items>
        libinput Accel Custom Fallback Step (327):      0.000000
        libinput Accel Custom Motion Points (328):      <no items>
        libinput Accel Custom Motion Step (329):        0.000000
        libinput Accel Custom Scroll Points (330):      <no items>
        libinput Accel Custom Scroll Step (331):        0.000000
        libinput Left Handed Enabled (332):     0
        libinput Left Handed Enabled Default (333):     0
        libinput Send Events Modes Available (295):     1, 0
        libinput Send Events Mode Enabled (296):        0, 0
        libinput Send Events Mode Enabled Default (297):        0, 0
        Device Node (298):      "/dev/input/event7"
        Device Product ID (299):        9610, 16
        libinput Drag Lock Buttons (334):       <no items>
        libinput Horizontal Scroll Enabled (335):       1
        libinput Scrolling Pixel Distance (336):        15
        libinput Scrolling Pixel Distance Default (337):        15
        libinput High Resolution Wheel Scroll Enabled (338):    1

⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼ /home/greg ⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼
❱xinput list-props 17
Device 'Hailuck Co.,Ltd PTP TouchPad Touchpad':
        Device Enabled (179):   1
        Coordinate Transformation Matrix (181): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        Device Accel Profile (306):     1
        Device Accel Constant Deceleration (307):       2.500000
        Device Accel Adaptive Deceleration (308):       1.000000
        Device Accel Velocity Scaling (309):    12.500000
        Synaptics Edges (340):  61, 1474, 47, 832
        Synaptics Finger (341): 30, 50, 0
        Synaptics Tap Time (342):       125
        Synaptics Tap Move (343):       77
        Synaptics Tap Durations (344):  180, 180, 100
        Synaptics ClickPad (345):       1
        Synaptics Middle Button Timeout (346):  0
        Synaptics Two-Finger Pressure (347):    40
        Synaptics Two-Finger Width (348):       8
        Synaptics Scrolling Distance (349):     35, 35
        Synaptics Edge Scrolling (350): 1, 1, 0
        Synaptics Two-Finger Scrolling (351):   1, 1
        Synaptics Move Speed (352):     1.000000, 1.750000, 0.113122, 0.000000
        Synaptics Off (353):    0
        Synaptics Locked Drags (354):   0
        Synaptics Locked Drags Timeout (355):   5000
        Synaptics Tap Action (356):     0, 0, 0, 0, 1, 3, 2
        Synaptics Click Action (357):   1, 1, 1
        Synaptics Circular Scrolling (358):     1
        Synaptics Circular Scrolling Distance (359):    0.100000
        Synaptics Circular Scrolling Trigger (360):     2
        Synaptics Circular Pad (361):   0
        Synaptics Palm Detection (362): 0
        Synaptics Palm Dimensions (363):        10, 200
        Synaptics Coasting Speed (364): 0.000000, 50.000000
        Synaptics Pressure Motion (365):        30, 160
        Synaptics Pressure Motion Factor (366): 1.000000, 1.000000
        Synaptics Grab Event Device (367):      0
        Synaptics Gestures (368):       1
        Synaptics Capabilities (369):   1, 0, 1, 1, 1, 0, 0
        Synaptics Pad Resolution (370): 7, 7
        Synaptics Area (371):   0, 0, 0, 0
        Synaptics Soft Button Areas (372):      767, 0, 720, 0, 0, 0, 0, 0
        Synaptics Noise Cancellation (373):     8, 8
        Device Product ID (299):        9610, 16
        Device Node (298):      "/dev/input/event11"

The difference was that i was told to use /etc/X11/xorg.conf.d/30-touchpad.conf last time not /etc/X11/xorg.conf.d/99-synaptics.conf Cant see how that made a dif but who knows.

And the data to use in the file was different.

Now all i need to see is if i can find how you turn on the coasting and i will be over the moon (kinda, still have no calendar and other minor (possibly) things to deal with. But we can move on.

Thank you Sir, thank you.


I dont even have a /etc/X11/xorg.conf.d/99-synaptics.conf
in my instalation1? i do have a /etc/X11/xorg.conf.d/30-touchpad.conf but that only contains

Section “InputClass”
Identifier “touchpad”
Driver “synaptics”
MatchIsTouchpad “on”
Option “Tapping” “on”

So where would all the synaptic setting in my instalation1 be?

Anyhow, thank you again.

There isnt.
Configuration files go there.
Just like if I wanted certain amdgpu options, I might make /etc/X11/xorg.conf.d/99-amdgpu.conf.
The names dont really matter as long as they end in .conf - but they are loaded in order.
Meaning if you want to make sure something is loaded last, and therefor applied, you might use a high number like 99 for a preface.
In the example above … with both those files present 99-synaptics would be applied last and thus take precedence.

There should also be a template you can copy from at /usr/share/X11/xorg.conf.d/70-synaptics.conf though.

For all the particular options… I have no idea whats actually copied here. Its just a bunch of the options, though not all of them. Of course set them according to your needs. Most information you would need is at the wiki link posted. You mentioned ‘coasting’ and I note the example here has a speed of 0 for that … so you would probably want to set that to something else. etc.

All possible options should also be here: synaptics(4) — Arch manual pages

1 Like

Yea is kinda the hazy idea that i already had about these config files. But I’m still curious where then must be all the synaptic setting on my instalation1? Its still there and working with coasting etc so its settings must be held somewhere. just curious now as iv got instalation2’s trackpad all working now including coasting (until they remove synaptic all together as it sound like they are heading that way). Cross that bridge when i come to it.

Maybe in /usr/share/X11/xorg.conf.d/* ?

I really dont know about that SystemSettings module and how its actually functioning underneath, or where it applies or saves configs, etc.

xf86-input-synaptics is for X11 only, not for Wayland. Plasma 6 enables Wayland in session by default, but you can switch it to X11 manually.

I and many others have experienced that any touchpad works smoother under Wayland than under Xorg without having to configure it manually. It already fits what we need.

I believe you have that backwards. As of this release, X11 has again been made the default. The option to switch to Wayland still remains.