Preflight Checklist

• [X] I have read the Contributing Guidelines for this project.
• [X] I agree to follow the Code of Conduct that this project adheres to.
• [X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

Screen sharing is an essential part of modern online communication, and recently I noticed it working within Chromium, so I believe it can here too?

Proposed Solution

Implement screen-share support on Wayland

Alternatives Considered

n/a

Additional Information

No response

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.0.0.nightly.56.r5506.cf182890-1 (AUR ferdi-git package)

What Operating System are you using?

Other Linux

Operating System Version

Archlinux

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

When starting ferdium, the window should show my services and I should be able to interact with them.

Actual Behavior

After starting (and opening) ferdium, the window remains blank (see screenshot below). I get the following log output:

Steps to reproduce

Launch ferdium

Debug link

Not Possible. The help menu has no entries (show (empty)

Screenshots

Screenshot of the ferdium window, just to make sure we talk about the same thing when I say it remains blank

Additional information

$ ferdium --enable-logging             
[37145:0611/132530.385413:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[37177:0611/132530.411115:WARNING:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[37145:0611/132530.644542:INFO:CONSOLE(111)] "%cDownload the React DevTools for a better development experience: https://reactjs.org/link/react-devtools
You might need to use a local HTTP server (instead of file://): https://reactjs.org/link/react-devtools-faq font-weight:bold", source: /opt/ferdium-git/resources/app.asar/node_modules/@sentry/utils/dist/instrument.js (111)
[37145:0611/132531.169996:INFO:CONSOLE(943)] "Uncaught Error: Cannot find module 'react-virtualized'
Require stack:
- /opt/ferdium-git/resources/app.asar/node_modules/electron-react-titlebar/dist/renderer.js
- /opt/ferdium-git/resources/app.asar/components/layout/AppLayout.js
- /opt/ferdium-git/resources/app.asar/containers/layout/AppLayoutContainer.js
- /opt/ferdium-git/resources/app.asar/routes.js
- /opt/ferdium-git/resources/app.asar/index.html", source: node:internal/modules/cjs/loader (943)
[37145:0611/132532.337313:INFO:CONSOLE(111)] "Could not connect to Sentry main process. Did you call init in the Electron main process?", source: /opt/ferdium-git/resources/app.asar/node_modules/@sentry/utils/dist/instrument.js (111)

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.2.1

What Operating System are you using?

Windows

Operating System Version

windows 10 and Windows Server 2019

What arch are you using?

x64

Last Known Working Ferdium version

6.2.0

Expected Behavior

Open Ferdium

Actual Behavior

Opens to blue screen.

Steps to reproduce

1. install either 6.2.1 or nightly 6.2.2.
2. Run program
3. notice the blue screen

Debug link

No response

Screenshots

Additional information

No response

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.0.0-nightly.69

What Operating System are you using?

Other Linux

Operating System Version

Arch Linux

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

Whatsapp should not reload at every interaction with the interface.

Actual Behavior

Every time I interact with Whatsapp web the page stays unresponsive for a couple of seconds and the loading message keeps flashing until the page starts responding again. After the introduction of the line loading indicator only the indicator flashes and not the loading message. The issue is present on both Linux and Windows and both local account and synced account.

Steps to reproduce

1. Open Ferdium
2. Open the whatsapp web service

Debug link

No response

Screenshots

No response

Additional information

No response

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.2.0

What Operating System are you using?

Windows

Operating System Version

Windows 11

What arch are you using?

x64

Last Known Working Ferdium version

6.2.0

Expected Behavior

It should show my services

Actual Behavior

It is showing the red bar with "Could not load services and user information Try again"

Steps to reproduce

1. Open the ferdium

Debug link

No response

Screenshots

Additional information

It started last night

Your issue

Hello guys!

Yesterday I started to see this. This is pretty nice actually.

Every time this appears, I reload the services. But this thing keeps appearing. I am not sure if it is a bug or if these files a constantly being updated. It they are being updated it is fine, I will deal with it since it is a nightly build. But I would like to say that this thing is appearing quite often. However, it may be a bug where the service files are not being updated or something.

Version I am using,

Cheers!

I expanded here on a list I found on discord on things that need to be done before initial release. if I missed something or added something unnecessary please let me know/ add it in comment

• [x] update name to "Ferdium" everywhere
• [x] update visual branding everywhere (logo, images in READMEs of app, recipes and server)
• [x] change copyright message everywhere to "Ferdium Contributors"
• [x] Setup the nightly build process
• [x] Setup the beta build process
• [x] Enable Snapstore login + publishing
• [ ] review licensing
• [x] add 'https://ferdium.org' to org repo description
• [x] temporarily make https://ferdium.org/download redirect to https://github.com/ferdium/ferdi/releases
• [x] get apple dev license and sign the macos builds
• [x] get windows dev license and sign the windows builds
• [x] host/run the API server
• [x] get the debug API server running
• [x] Initial setup is done. For the following (post 6.0.0 release) see #185
• [x] transferring pre-existing ferdi profile to ferdium:
  • [x] Migration scripts (#4)
  • [x] Further testing on migration scripts
• [x] replace ferdi with ferdium on all package managers
  • [x] homebrew (we ended up creating our own tap: https://github.com/ferdium/homebrew-ferdium )
  • [x] scoop
  • [x] chocolatey
  • [x] winget
  • [x] aur
  • [x] flatpak
• [x] documentation and FAQ ⇒ first FAQ on https://ferdium.org/faq
• [ ] then make an initial release - Ferdium 6.0
• [x] make https://ferdium.org/download redirect to https://github.com/ferdium/ferdium-app/releases (or just remove the old redirect) ⇒ custom page on the website
• [x] after the initial release: website
• [ ] Make recipes automatically update on the API server. https://github.com/ferdium/ferdium-server/issues/31 and https://github.com/ferdium/ferdium-server/issues/32
• [x] Find a solution for https://github.com/ferdium/ferdium-app/issues/224

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.2.0 + 6.2.1

What Operating System are you using?

Windows

Operating System Version

win 10 pro 21H2 19044.2251

What arch are you using?

x64

Last Known Working Ferdium version

6.2.0

Expected Behavior

app start when i press icon

Actual Behavior

start to happen a week ago. app not start (6.2.0 and 6.2.1) at all, it show in win task bar try to reinstall, it say it open and cannot close it. I delete the files and make 6.2.0 and 6.2.1 install and same issue continue PORTABLE version working perfect :)

Steps to reproduce

I guess its something in my computer please help me fix or fully clear installation files. I will try to re-install again and hope it work

Debug link

No response

Screenshots

Additional information

No response

Avoid duplicates

• [x] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.1.0

What Operating System are you using?

Windows

Operating System Version

Windows 10 22H2, 19045.1889

What arch are you using?

x64

Last Known Working Ferdium version

6.1.0

Expected Behavior

To not slow down to a crawl.

Actual Behavior

In Whatsapp, when you have a chat with stickers (not emoji!) and a chat without stickers:

• Switching between these chats slows down the software, i.e. it takes 2-3 seconds to switch to chat with stickers, and back to normal chats with just text and emojis.
• In chats with stickers, in my case, whenever I try to type ?, ! or (), the software takes about 4-5 seconds to actually type it it.
• If I copy/paste ?, !, (, ) it works normal

Steps to reproduce

See "Actual Behavior"

Debug link

https://debug.ferdium.org/0c33e1df-80f1-4160-9f36-2cad855f167b

Screenshots

No response

Additional information

No response

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.0.0.nightly.31

What Operating System are you using?

Other Linux

Operating System Version

5.17.5-arch1

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

Ferdium on wayland utilizes as much CPU as chromium on wayland with a few tabs open.

Actual Behavior

When I open ferdium and add a few services, after a short while my fan springs into action and when I check htop, it reveals that ferdium utilizes an entire thread, for reasons unknown to me.

Steps to reproduce

It should be noted that I run ferdium with the --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-features-WaylandWindowDecorations options. The bug does not appear to affect non-wayland instances. (Edit: It does, it just doesn't do so as fast)

1. Run ferdium
2. Open htop
3. Sort by maximum CPU utilization

Debug link

https://debug.ferdium.org/735bad7f-3a58-46dd-b297-b9adc4f5df6f

Screenshots

No response

Additional information

No response

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.0.0-nightly.24

What Operating System are you using?

Ubuntu

Operating System Version

20.04

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

I can add new services

Actual Behavior

Nothing is added, dmesg spawn various apparmour DENIED accesses

Steps to reproduce

1. Open the app
2. Add new service
3. Nothing is selected

Alternatively, import old services from export.ferdi-data file

Debug link

No response

Screenshots

No response

Additional information

[157230.876045] audit: type=1326 audit(1651589474.806:11111): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.ferdium.ferdium pid=1015456 comm="ferdium" exe="/snap/ferdium/7/ferdium" sig=0 arch=c000003e syscall=330 compat=0 ip=0x7f86d3c044e7 code=0x50000
[157230.895345] audit: type=1326 audit(1651589474.822:11112): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.ferdium.ferdium pid=1015457 comm="ferdium" exe="/snap/ferdium/7/ferdium" sig=0 arch=c000003e syscall=330 compat=0 ip=0x7ffa1e4d44e7 code=0x50000
[157231.110968] audit: type=1326 audit(1651589475.038:11113): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.ferdium.ferdium pid=1015482 comm="ferdium" exe="/snap/ferdium/7/ferdium" sig=0 arch=c000003e syscall=330 compat=0 ip=0x7f0abef944e7 code=0x50000
[157231.125334] audit: type=1326 audit(1651589475.054:11114): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.ferdium.ferdium pid=1015483 comm="ferdium" exe="/snap/ferdium/7/ferdium" sig=0 arch=c000003e syscall=330 compat=0 ip=0x7f192274d4e7 code=0x50000
[157236.082786] audit: type=1326 audit(1651589480.010:11115): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.ferdium.ferdium pid=1015405 comm="ferdium" exe="/snap/ferdium/7/ferdium" sig=0 arch=c000003e syscall=326 compat=0 ip=0x7f596682e539 code=0x50000
[157239.795856] audit: type=1326 audit(1651589483.722:11116): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.ferdium.ferdium pid=1015405 comm="ferdium" exe="/snap/ferdium/7/ferdium" sig=0 arch=c000003e syscall=326 compat=0 ip=0x7f596682e539 code=0x50000

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.2.3

What Operating System are you using?

Ubuntu

Operating System Version

Ubuntu 22.04.1

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

After sleep mode and logging back to your account, the icon on top is showing once and is working

Actual Behavior

After going to sleep mode, the icon in the top taskbar is showing twice, and the second one is not doing anything when I click on it.

Steps to reproduce

1. Launch Ferdium
2. Go to sleep mode
3. Turn back on your computer
4. After logging back, the icon is now showing twice

Debug link

No response

Screenshots

Additional information

No response

Pre-flight Checklist

• [x] I have read the Contributing Guidelines for this project.
• [x] I agree to follow the Code of Conduct that this project adheres to.
• [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Note: I'm pretty new and don't know much about Ferdium's architecture so I tried my best, but do not hesitate to tell me if anything needs to be changed

Description of Change

At start, Ferdium looks for a ~/.config/Ferdium/config/custom.css and applies it if it exists. The CSS customises Ferdium's UI, not the webview.

Motivation and Context

I made a custom CSS for Ferdium in order for it to better fit my desktop environment and I'd like to have a better way to apply it than just compiling the software myself.

Screenshots

Not very relevant, but for an example with my own theme :

Checklist

• [x] My pull request is properly named
• [x] The changes respect the code style of the project (pnpm prepare-code)
• [x] pnpm test passes
• [x] I tested/previewed my changes locally

Release Notes

Added support for a custom CSS stylesheet for Ferdium's UI

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.2.2

What Operating System are you using?

Other Linux

Operating System Version

Arch Rolling; 6.1.2-zen1-1-zen; GNOME 43.2 Wayland

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

I should see and be able to stream my Display contants, not just my windows

Actual Behavior

I can't Stream My Windows because they are blacked out. Other Participants just see a black screen, without any contens

Steps to reproduce

1. Open Teams Service
2. Start a Meeting
3. Click on the Share Screen Icon
4. See the Screenshot. Windows can be shared, the Screen can't

Debug link

https://debug.ferdium.org/49eb0f53-3492-49a5-bded-5a3e58182c10

Screenshots

Additional information

No response

Pre-flight Checklist

1. Please remember that if you are logging a bug for some service that has stopped working or is working incorrectly, please log the bug here
2. If you are requesting support for a new service in Ferdium, please log it here
3. Please remember to read the self-help documentation - in case it helps you unblock yourself for issues related to older versions of recipes that were installed on your machine. (These will get automatically upgraded when you upgrade to the newer versions of Ferdium, but to get new recipes between Ferdium releases, this documentation is quite useful.)
4. Please ensure you've completed all of the following.

• [x] I have read the Contributing Guidelines for this project.
• [x] I agree to follow the Code of Conduct that this project adheres to.
• [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Description of Change

This patch adds a basic D-Bus IPC interface under Linux to expose information about notification. This is useful for, e.g., displaying notification status in a system status bar like waybar, polybar, or i3status.

Security considerations for untrusted D-Bus access apply. The information exposed to the bus may be private in nature. However, desktop environments such as GNOME already expose copious amounts of private information to the bus in order to enabled integration between various desktop applications. Thus, the normal care for running untrusted applications (e.g., flatpak or firejail sandboxing) should be sufficient to mitigate any threats to privacy or security.

Ferdium exposes under the org.ferdium.Ferdium bus name at the /org/ferdium object path an object implementing the org.ferdium.Ferdium interface. The interface has the following methods:

• ToggleMute() toggles the muted state of notifications. Use the Muted property to query muted state.
• ToggleWindow() makes visible and focuses the Ferdium window if not focused, hides it if it was already focused. This is equivalent to clicking on the Ferdium tray icon.

The interface has the following properties:

• Muted: b read-write true if notifications are currently muted, false otherwise. Writing a boolean value to this property sets the muted state (i.e., set to true to mute, false to unmute).
• UnreadDirectMessageCount: u read-only the number of unread direct messages.
• UnreadIndirectMessageCount: u read-only the number of unread indirect messages.
• UnreadServices: a(suu) read-only an array tuples corresponding to services with unread messages. Services with no unread direct or indirect messages are omitted, i.e., if there are no new messages at all, this array is empty.
  • The first element of the tuple is the name of the service as a string.
  • The second element of the tuple is the number of unread direct messages.
  • The third element of the tuple is the number of unread indirect messages.

UnreadDirectMessageCount, UnreadIndirectMessageCount, and UnreadServices are governed by the same rules w.r.t. global mute, service muting, hiding indirect notifications, etc. as the tray icon itself.

I also moved some documentation to the docs/ directory (except those .md files that are required to be in the repository root by convention) and added some documentation of the D-Bus API (including a usage example to display unread message counts on the Waybar status bar) there, too.

Motivation and Context

Fixes #863.

Checklist

• [x] My pull request is properly named
• [x] The changes respect the code style of the project (pnpm prepare-code)
• [x] pnpm test passes
• [x] I tested/previewed my changes locally

Signed-off-by: Kristóf Marussy [email protected]

Release Notes

Added D-Bus API (#863).

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.2.3

What Operating System are you using?

Other Linux

Operating System Version

Zorin OS 16.2 (Based on Ubuntu 20.04 LTS)

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

Toggle dark mode from custom services.

Actual Behavior

Nothing happens. It only works for Whatsapp, so my thought was that this is possibly related to the custom workaround, because there where I time the dark mode hasn't worked and caused issues.

Steps to reproduce

1. Right click on service
2. Enable Dark mode
3. Disable Dark mode

Debug link

No response

Screenshots

No response

Additional information

I don't know if that might just not be implemented but it can only say it doesn't work for me.

Preflight Checklist

• [X] I have read the Contributing Guidelines for this project.
• [X] I agree to follow the Code of Conduct that this project adheres to.
• [X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

I really like to use the custom app feature because there are just so many great apps that can't be all naively supported an that's okay. :)

I currently don't want to spend my time by adding all the custom apps to the repository but maybe I will do that some day. 😄

Proposed Solution

So I have 3 Ideas I wanted to share:

• Use service title from search bar So you are searching an app and you don't find it, so I basically always copy paste the name to the add service screen. Why don't use the input from the search field? :)

• Add new service directly to a work spaces It would also be nice to be able to directly add the new app to a work space. My thought would be to display the list of work spaces with a toggle button like you can toggle apps in the workspace view.

• Auto fetch icons from websites You copy the link from the service you want to add, but I found it a bit frustrating that you always need to search for an icon. So I found a trick how you can directly get the website icon, by adding /favicon.ico to the url.

There might be a better solution or online service for this, because the icons are normally pretty small but I just wanted to share it. :)

Alternatives Considered

These are improvement ideas, as I said for image fetching there might be a better solution.

Additional Information

Nothing, I just want to say thank you for continuing this awesome project. I really appreciate that work from all of you. ❤️