I still need to get used to some shortcuts.
For instance, select the address bar usually is: Alt-D. With Vivaldi this is Ctrl-L.
For the rest: It’s a new skin on the chrome/chromium browser.
I just hope it doesn’t send my browsing habits to Google ;)
I’d say: Worth a try.
Left a questing in the Slack channel of Franz.
I the meantime I switched to Rambox.
Though I’d like to know why and how this works, I guess this is not an Antergos issue, but more with the Franz App (or one of its configured web-apps).
Thanks @Modisc for helping!
Found it, but I don’t understand it.
When I’m running Franz, on my Desktop the screensaver behaves normally, but on my laptop, the screen does not get locked.
When I stop Franz, locking works normal.
I guess I will need the Franz developers for this problem.
Thanks @Modisc for your assistance.
I will keep you informed…
xscreensaver is installed.
Here’s the autostart:
/home/herman/.config/autostart: anydesk.desktop* dropbox.desktop franz.desktop /home/herman/.config/autostart-scripts:
That’s the same thing as
- System Settings
- Desktop behavior
- Screen locking
- Desktop behavior
It is set to:
- Automatically (after 1 minute)
- Require a password: immediately
- Single image
I picked one allready in the list, I think it’s this one: /usr/share/wallpapers/FlyingKonqui/contents/images/
The screen does dim (after 5 minutes as per energy saving setting)
Could this be related to Bumblebee?
Here’s another thing I noticed.
On a clean boot, the screensaver does not work.
When I wake the laptop from suspend, screensaver works!
Key difference I noticed is: ksmserver.
When the screensaved does start, the journal has a log line :
ksmserver: lock called (... powerdevil...) ksmserver: Lock window Id: 18874397 dbus-daemon: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.47' (uid=1000 pid=6820 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper) ksmserver: CreateNotify: 18874397 dbus-daemon: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' org_kde_powerdevil: powerdevil: Udev device changed "/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight" "/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight" ksmserver: CreateNotify: 60817411 (...)
Those are not present when the screen goes black because of power savings.
And this does not always happen.
2n time around the ksmserver is called to log me back in, but does not get the “lock called” event again.
- System Settings
On a new installation (see also https://forum.antergos.com/topic/9985/) I can not get the screen lock to work.
PowerDevil does dimm the screen, but the Screen Locking (System settings, workspace, desktop behavior, screen locking) does not kick in after the desired time.
It does work when I hit Ctrl+Alt+L,
It does work when I close the lid and re-open the lid (which is under hardware energy settings).
I tried changing the wallpaper type (https://bbs.archlinux.org/viewtopic.php?id=236664), both to image and plain color.
Set the activation to 1min (ask for password: immediately)
Switched my DM from LightDM to SDDM.
I don’t know where to look next.
Is there anyone that can help me figure this thing out?
There does not seem to be any mention in the journal.
It’s just like the timer for activity does not start (But it does for the PowerDevil backlight.
There are some errors in the journal:
- plasmashell: QXcbConnection: XCB error: 2 (BadValue), sequence: 11113, resource id: 79691781, major code: 142 (Unknown), minor code: 3
- org_kde_powerdevil: powerdevil: Can’t contact ck
- org_kde_powerdevil: powerdevil: We are now into activity “adcfdab2-360b-4c18-9848-88dd6e2c8107”
- kdeinit5: kf5.kservice.services: The desktop entry file “/usr/share/applications/org.kde.systemmonitor.desktop” has Type= “Application” but no Exec line
- kdeinit5: kf5.kservice.sycoca: Invalid Service : “/usr/share/applications/org.kde.systemmonitor.desktop”
- kwin_x11: QXcbConnection: XCB error: 3 (BadWindow), sequence: 65463, resource id: 79691931, major code: 18 (ChangeProperty), minor code: 0
What a search.
Can’t believe I missed it earlier.
Below the BIOS setting for allowing Legacy mode, there’s the secure boot option.
When Legacy is allowed, this setting is grey.
When Legacy is disabled, only then I could also disable secure boot.
Still booted default to windows, but I got the option to change the boot order.
Ran grub mkconfig and install
Then I changed the default boot order of the EFI boot
So now I have
default boot: GRUB
default grub entry: Antergos.
but I can allways choose something different.