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
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
Рогнеда,
Thank you for contacting us. This is an automated response confirming the receipt of your ticket. One of our agents will get back to you as soon as possible. For your records, the details of the ticket are listed below. When replying, please make sure that the ticket ID is kept in the subject line to ensure that your replies are tracked appropriately.
Ticket ID: XMD-349-45029
Subject: Система BancBot – простой и доступный заработок в инте рнете! Доход $150 в час и выше!
Department: Reflected Support
Status: Open
Kind regards,
Reflected Networks, Inc.
You may visit https://portal.reflected.net/chat/?t=XMD-349-45029&ac=1 for live chat support.
You may also visit https://portal.reflected.net/chat/?t=XMD-349-45029&ac=0 to view ticket history.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
I have asked you to stop sending these emails dozens of times the only reason I'm replying to your whole group that was tagged in my email is so that they can see what kind of jerks you are too.
Sent from my iPad
> On Apr 12, 2014, at 9:17 PM, "Reflected Networks, Inc." <support(a)reflected.net> wrote:
>
> XSMOKS f,
>
> Thank you for contacting us. This is an automated response confirming the receipt of your ticket. One of our agents will get back to you as soon as possible. For your records, the details of the ticket are listed below. When replying, please make sure that the ticket ID is kept in the subject line to ensure that your replies are tracked appropriately.
>
> Ticket ID: YAL-976-56456
> Subject: [SPAM] Единственный способ бросить курить раз и навсегда. За 1 день.
> Department: Reflected Support
> Status: Open
>
> Kind regards,
>
> Reflected Networks, Inc.
>
>
> You may visit https://portal.reflected.net/chat/?t=YAL-976-56456&ac=1 for live chat support.
> You may also visit https://portal.reflected.net/chat/?t=YAL-976-56456&ac=0 to view ticket history.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
I DID NOT CONTACT YOU JERKS!! I AM SICK OF YOU SENDING THESE RIDICULOUSLY STUPID EMAILS STOP NOW!
Sent from my iPad
> On Apr 12, 2014, at 9:17 PM, "Reflected Networks, Inc." <support(a)reflected.net> wrote:
>
> XSMOKS f,
>
> Thank you for contacting us. This is an automated response confirming the receipt of your ticket. One of our agents will get back to you as soon as possible. For your records, the details of the ticket are listed below. When replying, please make sure that the ticket ID is kept in the subject line to ensure that your replies are tracked appropriately.
>
> Ticket ID: YAL-976-56456
> Subject: [SPAM] Единственный способ бросить курить раз и навсегда. За 1 день.
> Department: Reflected Support
> Status: Open
>
> Kind regards,
>
> Reflected Networks, Inc.
>
>
> You may visit https://portal.reflected.net/chat/?t=YAL-976-56456&ac=1 for live chat support.
> You may also visit https://portal.reflected.net/chat/?t=YAL-976-56456&ac=0 to view ticket history.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
I am used to control + arrow keys (left / right) to navigate across
words in the terminal. Suddenly it has stopped working in
gnome-terminal. It works fine in konsole though. Is this a bug ?
--
Sankar P
http://psankar.blogspot.com
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Using opensuse 13.1 stock gnome
Wireless works fine but the tray icon is flaky.
It doesn't always display the connected icon even though it has connected.
This can happen about 50% of the time and it can be from a cold reboot or
waking from sleep.
Initially the icon is not connected, then it goes to the 3 dots for
connecting, but it doesn't change from the 3 dots. It never gets stuck on
the not connected icon, only on the connecting...
So for example. You wake from suspend, the not connected icon changes to
connecting... the wireless connects, but the icon doesn't change from
connecting to connected.
See image here: http://paste.opensuse.org/28966939
Given some hours of use, the icon will usually come good eventually.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
UBOT,
Thank you for contacting us. This is an automated response confirming the receipt of your ticket. One of our agents will get back to you as soon as possible. For your records, the details of the ticket are listed below. When replying, please make sure that the ticket ID is kept in the subject line to ensure that your replies are tracked appropriately.
Ticket ID: ZRK-294-26272
Subject: [SPAM] Ubot - Робот который принос ит деньги. Вы отдыхаете. Ubot работает за вас!
Department: Reflected Support
Status: Open
Kind regards,
Reflected Networks, Inc.
You may visit https://portal.reflected.net/chat/?t=ZRK-294-26272&ac=1 for live chat support.
You may also visit https://portal.reflected.net/chat/?t=ZRK-294-26272&ac=0 to view ticket history.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
I am suffering a bad stability regression with GNOME 3 in openSUSE 13.1.
With a certain Huawei USB 3G stick, I've had to restart ModemManager
(via pkill ModemManager) and/or pull and reinsert the USB stick for
years. This is necessary since ModemManager fails to properly close
open ports when a connection breaks. Not ideal, but effective.
With GNOME 3 on openSUSE 13.1, often this leads to GNOME Shell going
down in flames when I try to reestablish a mobile broadband connection
later on:
[88116.886900] gnome-shell[1548]: segfault at d445000 ip 00007fa416282eb6 sp 00007fff06649fc8 error 4 in libc-2.18.so[7fa41615a000+1a5000]
[88144.679178] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[88144.779906] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[88144.780145] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[88144.782651] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[88144.789305] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[88144.872905] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[88170.571392] gnome-shell[23540]: segfault at 6675000 ip 00007f2f3b713eb6 sp 00007fffe8e24d68 error 4 in libc-2.18.so[7f2f3b5eb000+1a5000]
[88253.631370] gnome-shell[24105]: segfault at 6a5e000 ip 00007fda95f25eb6 sp 00007fff8c9a17f8 error 4 in libc-2.18.so[7fda95dfd000+1a5000]
Logging out is not sufficient, I really need to reboot the machine
when that happens to get mobile broadband to work again.
Is GNOME Shell really a monolithic mega process that allows one aspect
of it to tear down the entire desktop environment when GNOME 2 would
handle a pkill gnome-shell very satisfactorily? The primary question
is this, though: How can I provide input for someone to have a reasonable
chance of fixing it?
Gerald
--
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
Does anyone here use i3 window manager regularly with gnome-shell ?
How is the experience ?
--
Sankar P
http://psankar.blogspot.com
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org