Search found 60 matches

by flexoron
Fri Sep 20, 2019 0:46
Forum: 3D Desktops and Window Managers
Topic: Gnome-Shell Upgrade Trouble
Replies: 0
Views: 15

Gnome-Shell Upgrade Trouble

Hello, Repository: sabayonlinux.org Revision: 4015 Gnome-Shell: 3.32 Gnome-Shell has been upgraded this time and crashed after gdm login process: systemd-coredump[1788]: Process 1764 (gnome-shell) of user 1000 dumped core and gdm login screen starts again. It turned out that an extension caused the ...
by flexoron
Fri Jun 28, 2019 0:56
Forum: Sabayon Linux General Discussion
Topic: Upgrade to kernel 5.1.5 induces mouse wheel problems
Replies: 5
Views: 243

Re: Upgrade to kernel 5.1.5 induces mouse wheel problems

Hi, yes...these are different Roccat models: Kone, Koneplus, Arvo, Lua .... I've a Kone. # lsmod | grep roccat hid_roccat_kone 20480 0 hid_roccat 16384 1 hid_roccat_kone Kernel 5 implements a feature called high resolution smooth scrolling, I guess. Seems that Roccat drivers need adaption. Next, I'l...
by flexoron
Thu Jun 27, 2019 20:55
Forum: Sabayon Linux General Discussion
Topic: Upgrade to kernel 5.1.5 induces mouse wheel problems
Replies: 5
Views: 243

Re: Upgrade to kernel 5.1.5 induces mouse wheel problems [Solved]

The problem goes away if not Roccat(Kone) mouse. /lib/modules/4.20.0-sabayon/kernel/drivers/hid/hid-roccat.ko /lib/modules/4.20.0-sabayon/kernel/drivers/hid/hid-roccat_kone.ko <--- Good /lib/modules/5.1.0-sabayon/kernel/drivers/hid/hid-roccat.ko /lib/modules/5.1.0-sabayon/kernel/drivers/hid/hid-rocc...
by flexoron
Sat Jun 15, 2019 1:45
Forum: Sabayon Linux General Discussion
Topic: Upgrade to kernel 5.1.5 induces mouse wheel problems
Replies: 5
Views: 243

Upgrade to kernel 5.1.5 induces mouse wheel problems

Hello, after switching to kernel 5.1.5, mouse wheel scrolling speed is decelerated. Even firefox, chrome, terminals differ about that. (Chrome dead slow, firefox slow, terminals stutter) Needless to say, it is unusable. It seems it is a hardware-independent kernel series 5 issue with scrolling. Swit...
by flexoron
Sun May 05, 2019 14:38
Forum: Software in General
Topic: Firefox hiatus [Solved]
Replies: 6
Views: 220

Re: Firefox hiatus

hmm..ok..I just have Sabayon and all firefox extensions were disabled this morning.
Setting xpinstall.signatures.required to false brings them back into action.
by flexoron
Sun May 05, 2019 14:26
Forum: Software in General
Topic: Firefox hiatus [Solved]
Replies: 6
Views: 220

Re: Firefox hiatus

Sorry...forgot to mention the environment and I am, I mean Sabayon firefox is affected.
Sabayon Repository: sabayonlinux.org
Firefox Version 66.0.3
by flexoron
Sun May 05, 2019 14:12
Forum: Software in General
Topic: Firefox hiatus [Solved]
Replies: 6
Views: 220

Re: Firefox hiatus

Hello,

setting this parameter below to false and all extensions are back at work.
But, of course, you have to trust your extensions.

about:config
xpinstall.signatures.required false
by flexoron
Tue Feb 26, 2019 23:20
Forum: Sabayon Linux General Discussion
Topic: Linux kernel options not set
Replies: 2
Views: 196

Re: Linux kernel options not set

This applies to Docker and the question is how to check whether aufs4/aufs3 is in use. It doesn't affect the system. * CONFIG_AUFS_FS: is required to be set if and only if aufs-sources are used instead of aufs4/aufs3 This might be critical because Systemd is a pawn in the game(known as number one, /...
by flexoron
Mon Feb 25, 2019 10:54
Forum: Sabayon Linux General Discussion
Topic: Linux kernel options not set
Replies: 2
Views: 196

Linux kernel options not set

Hello Upgrade reports kernel options not set. Repository: sabayonlinux.org Revision: 3936 Kernel: 4.20.12 ## Unpacking: app-emulation:docker-18.09.2.9244d1b96a9a563af5f6531f96d2d70a7fbda8d0~0.tbz2 * Checking for suitable kernel configuration options... * CONFIG_AUFS_FS: is required to be set if and ...
by flexoron
Thu Dec 06, 2018 0:41
Forum: Sabayon Linux General Discussion
Topic: GNOME gdm service does not start after upgrade
Replies: 4
Views: 342

Re: GNOME gdm service does not start after upgrade

The problem as such has nothing to do with GNOME or KDE.
Perhaps it is a package upgrade issue.
If the new version moves its systemd service file to another location (here from /usr/lib64 to /lib)
it might recreate(if enabled) its 'enable link' in /etc/systemd/..., too?