Gnome Power Manager Applet

Hi all,
since the last update, the gnome power manager applet is gone. I can change the preferences with the gnome-power-preferences tool, but the applet in the system bar is gone... Any idea?
Acker

Master One wrote:
So what's going on?
I do not assume, that users of other distros have such problems, at least in Foresight Linux the applet is working as supposed to, which confirms that it's not an upstream problem. There is a bug open, but no info about any progress.
Is anybody working on a fix?
Jan de Groot has been assigned to this task a few days ago. Jan works on 580 open tasks, most of which have a higher priority then this bug.
As seen from the screenshot threads, quite some Arch users are on Gnome, so that's surely not something just a minority is in need of.
What's with the Gnome 2.18.1 updates (though the working version of the Gnome Power Manager in Foresight Linux is 2.18.2 as well)?
Oh my, an icon is not shown, man the life boats. The gnome-power-manager works perfectly -- at least for me -- it just doesn't show an icon in the notification area. If you absolutely need the icon, deploy Iloeki's script. It should do the job.

Similar Messages

AUR eee-control/gnome-power-manager

I updated my system, and seem to have a minor issue between gnome-power-manager 2.30 and eee-control-tray 9.4 (from the AUR, this might be the wrong section). The tray tool functions normally, except for the automatic FSB scaling with the new gnome-power-manager applet: When I launch eee-control-tray from the command line, I get an output of "FSB scaling not available. Is gnome-power-manager running?" I was wondering if anybody else has encountered this so far, and if it can be fixed.
Last edited by arinlares (2010-04-22 23:38:07)

Hello combuster!
gpm 2.26.3 ?
Is it just a misstyping ?

Power-manager applet: wrong alerts

I have Gnome and I use power-manager-applet in the taskbar to check the life of the battery.
I noticed this strange problem... When I use the laptop with batteris and I connect the power cable, the applet displays a popup alerting me that the power cable has been disconnected! But the icon shows the right image with the plug over the battery. And if I put the mouse on it, a tooltip says that the battery is charging...
If I disconnect the cable, the applet doesn't display no alters and an OSD popup with a stylized gear appears in the middle-botton of the monitor....
Does anybody has experienced something similar?

I've tried xfce4-power-manager but this program has a bug too.
Its icon appears in the sys-tray only after about 20 seconds after Gnome's loaded...
I've tried to load it from ~/.bashrc but it manifest the same problem: it appears only after a while... Could it do this because I use it under Gnome instead of XFCE?
P.S.:
I've noticed that it is also slower than gnome-power-manager in refreshing its state: if I disconnect the power cable, it pops up the notification after 5-10 seconds...
Last edited by leo72 (2009-06-30 20:26:22)

[SOLVED] gnome-power-manager issues since update?

Since maybe an update (I'm not sure), gnome-power-manager isn't launched anymore. No battery applet, suspend and hibernation buttons.
acpid, pm-utils are on.
By launching it in terminal, it gives:
~$ gnome-power-manager
(gnome-power-manager:3238): libupower-glib-WARNING **: Couldn't enumerate devices: Launch helper exited with unknown return code 127
TI:17:42:09 TH:0x10cf090 FI:gpm-engine.c FN:gpm_engine_coldplug_idle_cb,834
- failed to get device list: Launch helper exited with unknown return code 127
Traceback:
gnome-power-manager() [0x419a64]
gnome-power-manager() [0x41904e]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f3) [0x7f72b683abf3]
/usr/lib/libglib-2.0.so.0(+0x423d0) [0x7f72b683b3d0]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x182) [0x7f72b683ba42]
gnome-power-manager() [0x40f11b]
/lib/libc.so.6(__libc_start_main+0xfd) [0x7f72b6239c3d]
gnome-power-manager() [0x407a49]
So would libupower-glib bug?
Last edited by feNNec (2011-01-16 19:03:59)

yes there is:
$ ./upowerd start
./upowerd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory
libusb-1.0.8-1 is installed
What's this daemon for?

Gnome-power-manager not recognizing battery

Gnome-power-manager seems to act as if I have no battery whatsoever, and, when I am on battery power, keeps saying that I am running on AC power, despite the fact that both typing "acpi" into a terminal and the battery monitor applet give the correct state. I do have the dbus and acpid daemons running (they're in my rc.conf), and my laptop is an Acer Aspire 3618AWLCI.
Does anyone know what I could do? I would much rather use gnome-power manager than the batter monitor applet.

I realized that my problem since the update is that hald crashes after the session is launched. noamsml, did you check that hald is running on your laptop ?
Last edited by vlaaad (2007-02-05 14:17:04)

Gnome-power-manager 2.26 does not suspend on idle

I got a problem with gnome-power-manager 2.26 (several Versions 2.26.0 2.26.1 2.26.2 (original PKGBUILD)). I can suspend from the applet menu. It does hibernate on critical bat level, but i does not suspend on idle, regardless what timeout values I set in screensaver and gnome-power-manager. Display sleep seems to work though. First I thought, this might be only an issue on my particular notebook, as I could not find anything on google about this, but it is the same behavior on my freshly installed desktop system.
gnome-power-manager --verbose outputs nothing about going to standby.
I built gnome-power-manager and gnome-screensaver from 2.24 and they do work porperly, except the notebook will not hibernating on crit bat level.
Hardware:
Notebook: HP Pavilion dv3550eg (centrino2 - Nvidia 9300M GS)
Desktop: GB AMD 790XT, Phenom 720, Nvidia GTX 260
Software:
Arch64
Might this be an Policy issue? Nevertheless if anyone out there has has this problem, let me know and i am goning to file a bug report.

uwinkelvos wrote:I filed a bugrepoert about this: http://bugs.archlinux.org/task/15038
anyone willing and able to have a look at the sources is welcome... i just do not have the skills and tools to get to the right conclusion.
is a well know upstream problem. you should have been fill/comment on bugzilla bugtracker because is not archlinux fault.
http://bugzilla.gnome.org/buglist.cgi?q … r-manager+
http://blogs.gnome.org/hughsie/2009/05/ … tableness/

Gnome Power Manager after Last Upgrade

Hi There,
I just did a pacman -Syu and upgraded lots of packages which also include dbus etc.. I just restarted and puzzled that GNOME Power Manager is a lot different now then it's used to be before the upgrade. First of all, it's systray logo is different. Then it's menu, it's options, everything about it are different. I can't see an upgrade in the pacman.log for gnome-power-manager but it's completely changed..
When I pull the AC power and work on the batteries, it doesn't change the status of the applet. So the applet is very useless right now.. Although it doesn't seem to be an applet while it can't be moved around or I can't change anything about it..
Before the upgrade, I was able to get information by simply right clicking on it selection Information.. But now, even that option is completely changed.. Is there something wrong ?

Hello.
Is the bug fixed already? I have some problems with gnome-power-manager, dbus and hal. After installing Gnome everything was just fine, after I reboot I cannot start HAL:
[root@ichi ~]# /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
[root@ichi ~]# lshal
error: dbus_bus_get: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
gnome-power-manager gives msgbox with error about connecting to DBUS.
What is the issue?

Gnome-power-manager update causes backlight to power off frequently

After the upgrade to gnome-power-manager 2.26.1-1 today, my laptop screen backlight is being powered off constantly, after only about 1 minute. It's not the screen blanking, but the backlight going off. It comes right back up if I do anything on the keyboard.
My power management preferences haven't changed though. They're all set (as before the upgrade) to never dim the display and never put the display to sleep. So why is the backlight going off anyway?
Also, this pretty distinctly seems to have to do with Gnome and not X. If I leave the laptop for an extended period at the GDM login screen, the backlight is never powered off. The problem only develops after I have logged into Gnome.
Thanks for any help.
Last edited by cb474 (2009-04-23 07:14:55)

Thanks, I looked for bugs on this, but didn't find that one on the backlight for some reason. I was about to issue my own bug report. Anyway, so I added my comments to the bug report, but it has been marked "fixed" already (because it was really addressing a slightly different issue with DPMS), so I don't know if I need to start a new bug report or not. I'll wait and see what kind of reply I get. (In fact, it seems like the fix to the problem in the backlight bug report may have caused the problem addressed in this thread.)
That said, I found a work around, if you want to completely disable the backlight ever going off. You can issue the command:
xset -dpms
This disables entirely the display power management system (which I'm guessing gnome-power-manager operates as a frontend for). Of course, if you want your screen to be put to sleep after some set point of time this won't work. But you may be able to configure this directly with other xset commands or in xorg.conf (see links below).
To disable dpms at startup. I found oddly that it didn't work to add it to my .xinitrc. So instead I went to System > Preferences > Startup Applications. Added an a program in the "Startup Programs" tab, named it "DPMS (disable)" and for the command put:
xset -dpms
This is working.
You can also configue DPMS in xorg.conf, but I'm not using xorg.conf so I didn't fiddle with it. See: http://wiki.archlinux.org/index.php/DPMS and http://www.shallowsky.com/linux/x-screen-blanking.html.
Hope that helps.
Last edited by cb474 (2009-04-24 08:26:23)

Gnome-power-management: /etc/group question

gnome-power-management suspending works great for me as root , but not as unprivileged user:
# groups
root bin daemon sys adm disk wheel log
# su print
$ groups
wheel video audio power noah thinkpad
Wondering why this is? (pm-suspend works as unprivileged user)
TIA,
print

well, have a look at error messages (users.log, errors.log, messages.log, pm-suspend.log, ecc...). Did you log out after adding the "power" group to your user?

Changing brightness in gnome-power-manager has no effect

Well it's mostly all in the title. When I change the brightness slider in gnome-power-manager it has no affect on brightness. However the fn key combo for changing the brightness does have change the brightness yet it brings up the volume like dialog for brightness yet no change is registered on the slider (despite brightness increasing). This erratic behavior is not seen in Fedora or Ubuntu so I know it can be made to work. I have a Dell Inspiron 640m.

thunderogg wrote:Maybe a stupid question: Are you a member of the power group? I had a similar problem when I forgot to add my user to the power group.
I am now. But it hasn't fixed anything. I restarted X after adding my user to the group.
However when I started gnome-power-manager as root. It wouldn't let me access the preference dialog BUT when I increased or decreased the brightness it showed me the proper progressbar indicator. I will restart and see what happens.
edit:
After a restart all is working well as far as I can tell. Thank you very much for all your help. It seems it was in fact an issue with the groups.
Last edited by ihavenoname (2008-09-09 05:26:13)

[Solved] Systemd - Overrides settings of Gnome-Power-Manager?

Hello!
I've always used the following to lines to tell Gnome-Power-Manager not to suspend my laptop, when the lid is closed:
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
I remember a huge (and regular...) discussion around Gnome 3, because the developers resisted to re-implemented a button for this in the UI of Gnome3. Well, the two lines above done their job all the time. Since the last update of Systemd this seems to be ignored:
Oct 09 01:19:58 cupcake systemd-logind[273]: Lid closed.
Oct 09 01:19:58 cupcake systemd-logind[273]: Suspending...
Oct 09 01:19:58 cupcake systemd[1]: Starting Sleep.
Oct 09 01:19:58 cupcake systemd[1]: Reached target Sleep.
Oct 09 01:19:58 cupcake systemd[1]: Starting Suspend...
Is anyone other affected? Looks like a real problem for me. If I close the lid I want to close my lid, nothing more an especially not suspend
/var/log/pacman.log
[2012-10-08 21:59] upgraded systemd (193-1 -> 194-1)
[2012-10-08 21:59] upgraded systemd-sysvcompat (193-1 -> 194-1)
Last edited by hoschi (2012-10-08 23:53:06)

pablox wrote:
hoschi wrote:
Nope. Found it five minutes ago. My shame! Thank you
https://wiki.archlinux.org/index.php/Sy … th_systemd
This is driving me crazy. I've read the article, but I still don't understand what I'm supposed to do. I have tried changing values from logind.conf *IgnoreInhibited to yes to no, but the laptop still suspend when the lid is closed .
All you need to do is set HandleLidSwitch=ignore in logind.conf, this will make systemd ignore the lid switch completely, and leave gnome to handle it. Its pretty self explanatory... You can also set the other similar options to ignore, like HandlePowerKey, HandleSuspendKey, HandleHibernateKey if you want only gnome to handle them.
Last edited by bwat47 (2012-10-10 22:02:54)

How do I get gnome-power-manager working with standalone Openbox?

I'm brand new to Arch, so sorry if this is a dumb question that's already been answered. I'm installing on a Thinkpad T410, and I want a battery icon in my system tray. I've installed Openbox as a standalone window manager, and I'm using tint2 for a panel and system tray. I need something in my system tray to show my battery status.
I've looked around, and I don't really see any alternative to gnome-power-manager (I looked at trayfreq and batterymon), so I'm attempting to use that. I've installed it, but if I try to run it from a terminal I get this:
GLib-GIO-ERROR **: Settings schema 'org.gnome.settings-daemon.plugins.power' is not installed
aborting...
Aborted
After I get that, it quits and I really don't know what's going on there. Searching for "settings schema not installed" gets me nothing useful, so does anyone have an idea as to how to solve this problem?

n1md4 wrote:This solution worked for me too. I run a vanilla openbox install. Although I now have the battery icon in the panel, when selecting preferences, nothing loads. Any ideas?
From this thread https://bbs.archlinux.org/viewtopic.php?id=118420 the user said it solved it installing gnome-control-center.

Udev and gnome-power-manager

Hi,
Recently I upgrade the udev from 141-5-i686 to 145-1-i686 in my MSI wind. Then the following problem begins:
When the system boots this characters can be seen in the screen just before udev is finished: ^@^@
I can add more characters during the whole boot process if I press Fn+F5 (the brightness hotkey).
When gnome is running, in few minutes the screen change the brightness very fast, like blinking. This problem only happens if the gnome-power-manager is enabled.
Downgrading udev fix the problem.
Does anyone know if this is something related with this particular version of udev, or can I do something to fix it?
I don't know if the following messages will help, because them can be seen with the current and with the old udev version. But they are the only ones that I think are related with hotkeys amb modules loading. So I post them just in case.
messages.log:
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd06/26/2008:svnMICRO-STARINTERNATIONALCO.,LTD
:pnU-100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU-100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvrVer.001:' is
not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d000027A6sv00001462sd00000110bc03sc80i00' is not a valid module or alias
name
Aug 29 14:57:02 peremsi load-modules.sh: 'platform:vesafb' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d00002448sv00000000sd00000000bc06sc04i01' is not a valid module or alias
name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0103:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0303:PNP030B:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0F03:PNP0F13:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'usb:v0C45p62C0d0100dcEFdsc02dp01ic0Eisc02ip00' is not a valid module or alias name
Aug 29 14:57:08 peremsi ntfs-3g[2611]: Version 2009.4.4 integrated FUSE 27
(so many times) This message is because the kernel do not map some hotkeys. Gnome do it.
atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e078 <keycode>' to make it known.

recently, I updated system, and now I have same problem like you had. I was not sure, what could cause this brightness fast changing. I thought about hal, dbus, udev. Never tried to downgrade udev. Now, I have udev 146. I am not sure what version I had before system upgrading.
Now, I have kernel 2.6.31, and I am not sure if udev 141 will work with this kernel...
I have MSI WIND, also...
Last edited by kunalagon (2010-01-08 11:15:54)

Gnome-power-manager with networkmanager_sleep option

I have a wireless device using the ipw2200 module. I have always found it extremely annoying that gnome-power-manager asks NetworkManager to sleep before suspending, since, first of all, the ipw2200 module doesn't need to be unloaded and, secondly, because I always have to wait the extra few seconds it takes for NM to send the dhcp request after resuming. I made a patch that adds an option to turn the NM-sleep call on or off via a gconf entry (networkmanager_sleep). The patch has been accepted upstream and included in CVS. However, I've made a patch that applies cleanly to gnome-power-manager 2.16.1 as well. Here it is:
diff -Naur gnome-power-manager-2.16.1/data/gnome-power-manager.schemas.in gnome-power-manager-2.16.1-new/data/gnome-power-manager.schemas.in
--- gnome-power-manager-2.16.1/data/gnome-power-manager.schemas.in 2006-07-30 14:51:52.000000000 +0200
+++ gnome-power-manager-2.16.1-new/data/gnome-power-manager.schemas.in 2006-10-05 11:56:10.000000000 +0200
@@ -571,6 +571,17 @@
<long>This is the laptop panel screen brightness used when the session is idle. Only valid when use_time_for_policy is true.</long>
</locale>
</schema>
+ <schema>
+ <key>/schemas/apps/gnome-power-manager/networkmanager_sleep</key>
+ <applyto>/apps/gnome-power-manager/networkmanager_sleep</applyto>
+ <owner>gnome-power-manager</owner>
+ <type>bool</type>
+ <default>true</default>
+ <locale>
+ <short>If Networkmanager should disconnect.</short>
+ <long>Chooses whether Networkmanager should disconnect from the network before suspending.</long>
+ </locale>
+ </schema>
</schemalist>
</gconfschemafile>
diff -Naur gnome-power-manager-2.16.1/src/gpm-manager.c gnome-power-manager-2.16.1-new/src/gpm-manager.c
--- gnome-power-manager-2.16.1/src/gpm-manager.c 2006-09-17 22:33:51.000000000 +0200
+++ gnome-power-manager-2.16.1-new/src/gpm-manager.c 2006-10-05 12:03:22.000000000 +0200
@@ -1172,6 +1172,7 @@
gboolean allowed;
gboolean ret;
gboolean do_lock;
+ gboolean nm_sleep;
gpm_manager_allowed_hibernate (manager, &allowed, NULL);
@@ -1190,7 +1191,12 @@
gpm_screensaver_lock (manager->priv->screensaver);
- gpm_networkmanager_sleep ();
+ nm_sleep = gconf_client_get_bool (manager->priv->gconf_client,
+ GPM_PREF_NETWORKMANAGER_SLEEP, NULL);
+ if (nm_sleep) {
+ gpm_networkmanager_sleep ();
+ }
+
ret = gpm_hal_hibernate (manager->priv->hal);
manager_explain_reason (manager, GPM_GRAPH_EVENT_RESUME,
@@ -1230,7 +1236,12 @@
if (do_lock) {
gpm_screensaver_poke (manager->priv->screensaver);
- gpm_networkmanager_wake ();
+ nm_sleep = gconf_client_get_bool (manager->priv->gconf_client,
+ GPM_PREF_NETWORKMANAGER_SLEEP, NULL);
+ if (nm_sleep) {
+ gpm_networkmanager_wake ();
+ }
+
sync_dpms_policy (manager);
@@ -1257,6 +1268,7 @@
gboolean allowed;
gboolean ret;
gboolean do_lock;
+ gboolean nm_sleep;
GpmPowerStatus status;
char *message;
int charge_before_suspend;
@@ -1279,7 +1291,12 @@
gpm_screensaver_lock (manager->priv->screensaver);
- gpm_networkmanager_sleep ();
+ nm_sleep = gconf_client_get_bool (manager->priv->gconf_client,
+ GPM_PREF_NETWORKMANAGER_SLEEP, NULL);
+ if (nm_sleep) {
+ gpm_networkmanager_sleep ();
+ }
+
/* We save the current charge in mWh so we can see how much power we
lost or gained over the suspend cycle */
@@ -1348,7 +1365,12 @@
if (do_lock) {
gpm_screensaver_poke (manager->priv->screensaver);
- gpm_networkmanager_wake ();
+ nm_sleep = gconf_client_get_bool (manager->priv->gconf_client,
+ GPM_PREF_NETWORKMANAGER_SLEEP, NULL);
+ if (nm_sleep) {
+ gpm_networkmanager_wake ();
+ }
+
sync_dpms_policy (manager);
diff -Naur gnome-power-manager-2.16.1/src/gpm-prefs.h gnome-power-manager-2.16.1-new/src/gpm-prefs.h
--- gnome-power-manager-2.16.1/src/gpm-prefs.h 2006-07-30 14:51:54.000000000 +0200
+++ gnome-power-manager-2.16.1-new/src/gpm-prefs.h 2006-10-05 12:05:15.000000000 +0200
@@ -55,6 +55,9 @@
#define GPM_PREF_CAN_HIBERNATE GPM_PREF_DIR "/can_hibernate"
#define GPM_PREF_LOCK_USE_SCREENSAVER GPM_PREF_DIR "/lock_use_screensaver_settings"
+
+#define GPM_PREF_NETWORKMANAGER_SLEEP GPM_PREF_DIR "/networkmanager_sleep"
+
/* These are only effective if the system default is turned off. See bug #331164 */
#define GPM_PREF_LOCK_ON_BLANK_SCREEN GPM_PREF_DIR "/lock_on_blank_screen"
#define GPM_PREF_LOCK_ON_SUSPEND GPM_PREF_DIR "/lock_on_suspend"
It would be great if this could be added to the official package, but I'm not expecting it

Have a look in gconf-editor to see if there's a setting for that? (I can't check now, I'm using XFCE.) Also, check that you didn't keep the default "put computer to sleep when the lid is closed", but I suppose you've done it already...

APC UPS & gnome-power-manager

Hi there,
I am running gnome-power-manager on a system which is connected to an APC Back-UPS CS 500. It appears gnome-power-manager fails to recognize the UPS, however. In the preferences window, I only have an "On AC Power" and a "General" tab. AFAIK there ought to be an "On UPS Power" tab as well.
The UPS is connected correctly, as I can query it via apcaccess.
Any hints?
Edit: Just found http://bbs.archlinux.org/viewtopic.php?id=75730
Gonna see if this fixes it.
Last edited by Edmond (2009-07-13 21:44:53)

pyther wrote:Does this post resolve the issue? http://bbs.archlinux.org/viewtopic.php? … 86#p583386
Nope. As I said before:
Edmond wrote:I compiled devicekit-power 009 and then recompiled gnome-power-manager. No visible change.

Gnome Power Manager Applet

Similar Messages

Maybe you are looking for