Hello,
Despite recent openSUSE 13.1 kernel update, GNOME power management in my
Lenovo G470 is still pretty broken.
Somebody suggested this could be due the BIOS or firmware installed in
my laptop, but power-management is perfectly working whenever I boot
into WIN7.
GNOME Power-Management still lacks to:
a) Notify the user when battery level is critical
b) Suspend on RAM automatically at reached battery threshold
c) Hibernate automatically at reached battery threshold
Currently GNOME Power-Management simply shut-down the laptop when
battery reaches critical threshold that's a very annoying and irritating
behaviour.
Regards,
--
Ever notice how fast Windows runs? Neither did I...
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
For my notebook, in addition to the main battery I've got a
secondary that I uses when traveling.
In generally things work fine, except when openSUSE 13.1/GNOME
decide to shoot me in my foot. :-)
When the secondary battery drains, and the system switches to
back to the primary while I work, everything is fine.
When I then suspend-to-RAM and wake up again, I get a pop up
indicating that my battery (singular) is running low and the
system will be shut down.
/proc/acpi/battery/BAT*/* and the battery indicator in the status
panel (upper right corner of the screen) both indicate that I have
hours to go.
Still, within seconds a shutdown of the system is initiated without
me having any change to stop.
Soo, two questions:
- How can we get this fixed properly such that whatever is deciding
my battery is running low actually uses the same source of information
as the status indicator (which gets it right)?
- As a stop gap measure, but generally: How can I avoid such a forced
shutdown? Frankly, I'd rather let the system run out of battery than
anything being force on my.
Gerald (on a long haul flight back home this evening)
--
Dr. Gerald Pfeifer <gp(a)suse.com>
Sr. Director Product Management and Operations, SUSE
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hi GNOMEs!
I know you have been patiently waiting for a sign of life from the
GNOME Team.. sorry for the quietness, but we did not get lost; we are
still here with you and for you.
As the geeko following GNOME releases knows, GNOME 3.13.4 (the branch
potentially leading to GNOME 3.14) has been released last Wednesday.
As usual, the packages have been ready by that time in the Build
Service, but you want to know HOW to get there, don't you?
In line with the 're-targeting' of Factory, there are a few changes in
repositories that you should be aware of:
- openSUSE Factory => The 'Base' distribution repository we develop for
- GNOME:Factory => latest STABLE GNOME Version, receiving regular updates
of the stable branch, to keep GNOME in Factory
'up-to-date';
This is a small change, as it means you no
longer get 'unstable'
branches of GNOME in here. But it gets you
(hopefully!) stable
experience, which you can expect 'quickly' to
land in openSUSE:Factory
- GNOME:Next => This is where all the fun happens now: the NEXT
release of GNOME is prepared here
If it breaks, we're happy; if it works, we're
even happier.
In short: no 'guarantee' at any moment that
this works; but I run it on my system.
With this new layout, we believe to be able to better deliver upon the
promise of a 'stable Factory'.
Of course, this means lower speed of IN Factory, but users can rely on it.
The GNOME Team runs as a bare minimum GNOME:Factory on top of that; in
quiet times (between two major GNOME releases), this will be only very
few differences, but we 'test' bug-fixes in here.
And the crazy part of the GNOME Team is asked to run GNOME:Next (but
is also asked to FIX stuff they break :) )
for you as User? Pick you poison! Carefully balance between new/stable
and be prepared for an occasional break, the 'newer' you get. Users of
GNOME:Next are most welcome, but encouraged to also hang around on IRC
(#opensuse-gnome @ freenode) to have a short communication line to the
team; and who knows? If you like it enough, you might be our new most
active team member in no time!
Special not when adding the repositories:
GNOME:Next depends on GNOME:Factory depends on openSUSE:Factory; make
sure to add THE FULL chain of repositories. Put the priorities right,
so zypper dup knows what to do.
All nice and good, you DO want to test GNOME 3.13.x, but for nothing
on the world do you want to run Factory on your disk or mess with all
those repositories? We are regularly building a live image, based on
the GNOME:Next stack! there is NO QA (neither automatic nor manual)
happening on it; at best, some of us might try to boot it every now
and then.
For the curious ones, it is available at
http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME…
Questions? Comments? As usual, simply approach us!
Best regards,
Dominique / DimStar
openSUSE GNOME Team
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hello,
As you probably know, GNOME 3.12 is out.
What is the plan for openSUSE?
I guess extra repository that will add GNOME 3.12.
Any instructions? Any ideas when we'll have it?
Thanks
Stathis
--
http://about.me/iosifidishttp://linkedin.eiosifidis.info/http://www.eiosifidis.infohttp://gnome.eiosifidis.infohttp://www.gnome.grhttp://www.opensuse.gr
Great leaders don't tell you what to do...They show you how it's done.
Power corrupts. Absolute power corrupts...absolutely.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Evolution 3.12.3
I am attempting to import a CA into Evolution can I get "Enter the
password for 'NSS User Private Key and Certificate Services", token "NSS
Certificate DB".
If I have ever entered that password before i do not recall it [or
when]. Is there a way to find this an delete/reset it? I also cannot
delete a certificate in that dialog.
I was surprised that I cannot seem to manage certificates, at least CAs,
within Seahorse.
--
Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hey Gnome team. I don't know if any of you have read the discussion on
the Xfce mailing list regarding Adwaita branding for openSUSE. I'd
politely request if you can take a peek here:
http://lists.opensuse.org/opensuse-artwork/2014-07/msg00001.html - and
tell us what you think. (I posted a link so i don't create an
unreadable quoting block).
Hope you think we could pull it off.
Regards,
--
Nenad Latinović
nenad(a)latinovic.info
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
How can one disable print notifications in GNOME Shell?
There is no such option in "Notifications" settings.
I tried "gsettings set
org.gnome.settings-daemon.plugins.print-notifications active false" but
it has no effect
--
Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org