"Could not find a 'Notifications' widget"
Page 1 of 1 (10 posts)
Tags:
None
Registered Member 
|
Hi!
My computer freezes every time I get a notification. When I enter the settings menu I get this message: "Could not find a 'Notifications' widget which is required for displaying notifications." I couldn't find anything on the issue so I'm posting here. All help is appreciated! |
|
Registered Member
|
Hi!
Please give us more informations.
- What do the logs contain? (journalctl on most systems) - Which modifications did you apply? - Did you check the permissions in your homefolder? |
|
Registered Member
|
Right! 1. I am running the latest version of arch. 2. I'm relatively new to this kind of stuff so you'll have to be more specific. I don't think I can paste the whole log. 3. Only the arch dark theme. 4. I can check the permissions but I don't know what they should be. |
|
Registered Member
|
- The systemd-logging is explained here: systemd/journal - You can check the permissions with `find $HOME ! -user $USER -ls`. No output is good output. Anything else can be changed using chown/chmod. |
|
Registered Member
|
1. I tried the installation guide but after a few attempts, I resorted to using archfi. I got plasma-desktop through archfi. 3. Got no output with that command. 2. I ran the command 'sudo journalctl -b -p 4' after a restart and a notification from a friend. Here is the logs:
|
|
Registered Member
|
Please use tags to enclose long log outputs or a paste service. Its hard to read like this.
Done by moderator As I do not know archfi and am also not familiar with snap-packages I can only give you some hints. There are a lot of issues with your graphics card like «kwin_core: XCB error: 152 (BadDamage)» and failing bumblebeed.service. Consider using the firmware-package and properly set up your nvidia card: - Did you install the `linux-firmware`-package? Consider using fwupd → firmware update (if your system supports it) - NVidia, Optimus / Bumblebee Why did you install discord via snap? Did you have trouble using the native arch package? |
|
Registered Member
|
1. Dosn't seem like it supports ASUS sadly. 2. My laptop uses integrated intel graphics. There is no Nvidia card installed. I can't remember why I installed with snap. I removed the snap version and installed the native package. No differance tho. |
|
Registered Member
|
You know the ASUS-Site in arch wiki with tables of compatibility and todo? Perhaps it can help you with your specific model.
So why there is a bumblebee.service in your system? I'll recomment you to set up your graphics environment properly. Perhaps open a thread in the archlinux forums to get help with your specific model if the basic setup articles do not help you. Back to the notifications: Does a simple `notify-send title content` work? This needs the packacge libnotify to be installed. You can follow the logmessages with `journalctl -f` in a separate terminal emulator window. If this freezes too, create a new user (without special permissions), log in with this user and try again. |
|
Registered Member
|
Thanks! I'll look into asking about drivers on the arch form. Not sure why I have bumblebee.service on my system. My problem solving method is to throw everything at the wall and se what sticks. # notify-send title content Jul 08 16:51:58 Zensei dbus-daemon[661]: [session uid=1000 pid=661] Activating service name='org.freedesktop.Notifications' requested by ':1.275' (uid=1000 pid=16636 comm="notify-send title content ") Jul 08 16:52:59 Zensei plasma_waitforname[16640]: org.kde.knotifications: WaitForName: Service was not registered within timeout Jul 08 16:52:59 Zensei dbus-daemon[661]: [session uid=1000 pid=661] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1 The new user got the notification! Would that make it an issue with the permissions? |
|
Registered Member
|
That is a good approach to mess up the whole system  Never(!) copy&paste stuff / commands without knowing what they are for. At the beginning it is a lot to read and it takes a lot of time, but it is worth doing it.So as the new user gets the permission it is just your primary user messed up. That is solvable by either cleaning the configuration or finding the problem. As most systems nowadays use systemd, you can just use it to learn a bit about it. Set up the second user to be your main user and the first one to try things. And never use root permissions if they are not absolutely needed, e.g. for installing new packages to the whole system, performing updates, etc.
Reading a message like xy.service failed (or .timer, .mount,…) tells us, that there is more information available using the `systemctl` command, e.g. `systemctl --user status pulseaudio` for the pulseaudio.service unit. In this case the interprocess communication bus called dbus failed (see DBus) and we can ask systemctl for more information:
Sometimes there is more information, sometimes it just contains what you've already read in the journalctl-log. The following is not needed, just a «good to know section» on how to get some information. The session dbus (per user) is started by loginctl (dbus:org.freedesktop.login1), so you already should have a running session-dbus. You can get the currently running dbus processes with `ps aux | grep dbus. to see the system and session bus if you're interested in. Your mention process id 661 should be something like
where stuff are some numbers like pid, memory and cpu consumption, starting time,… See `ps aux | head -n1` to get the headers. To see a list of dbus-names, processes and the units, see `busctl list`. Again, there are options to get the information you want, like querying for all dbus-services from the current user point of view with busctl --user --full list`. |
Page 1 of 1 (10 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]
