August 2014 - openSUSE GNOME - openSUSE Mailing Lists

[opensuse-gnome] adjusting ctrl-w setting
by Olaf Hering 11 Aug '15

11 Aug '15

Many months (or years?) ago someone made GNOME3 usable by providing a knob to control the result of ctrl-w. Instead of closing the window it wipes the just typed word, as expected. I think it used to be in control-center,details. Now with SLE12 I can not find this knob anymore. What happend to it, how do I get a usable ctrl-w? Olaf -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org

3 5

[opensuse-gnome] GNOME laptop power-management is practically missing
by Marco Calistri 16 Nov '14

16 Nov '14

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

2 3

[opensuse-gnome] Scattered folders in Nautilus
by lists＠seablues.net 29 Aug '14

29 Aug '14

I'm having problems with the nautilus and file dialog displays. The sidebar is cluttered with folders from the main window. A screenshot for visual reference: http://postimg.org/image/54mnw5we9/ It doesn't happen every time, but more often than not. It's been this wy since I got this computer several weeks ago, an ASUS M51BC, 32GB RAM, AMD FX-8300, Radeon R9 270 2GB. Have you seen this before? Appreciate any help. Thanks, Jon Cosby -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org

3 2

[opensuse-gnome] Heads up for GNOME:Factory users
by Dimstar / Dominique Leuenberger 22 Aug '14

22 Aug '14

Hi geekos, Just a quick heads up! GNOME is getting closer to 3.14 release. By now, we have the (full?) GNOME 3.13.90 stack ready in GNOME:Next. After some fun bugs (<super> status was inverted) this is back in good shape. As announced earlier, we are still planning on merging this all into openSUSE:Factory as soon as 3.14.0 hits the shelves. For this to be realistic, we have to get some preliminary staging runs and openQA runs on Factory... And before that, we throw it at users of GNOME:Factory... which is, why you get this mail: I just submitted all packages from GNOME:Next to their respective 'homes' (mostly GNOME:Factory - some GNOME:Apps) and Bjorn is doing a fabulous job reviewing my work (send him an aspiring and some alcoholic beverages; he's in desperate need). Once this is all done as well, the packages will be checked in and rebuilt in GNOME:Factory - so far, all without risking your install: the repository does not publish at this moment. We do want to see a good build status first. Next steps? Submits towards openSUSE:Factory (without accepting checkins; we purely want the staging and openQA runs), followed by the updates to GNOME 3.13.91 (~Sept 3), GNOME 3.13.92 (Sept 17) and GNOME 3.14.0 (Sept 24). At that point, we should have sufficient Staging runs and openQA coverage to 'simply move this forward to openSUSE:Factory. Tight schedule, but we'll make sure to get there as painfree as possible. Cheers, -- Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org> -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org

1 0

[opensuse-gnome] Re: 13.2 freeze
by Dominique Leuenberger 08 Aug '14

08 Aug '14

Hi Stephan, Quoting Stephan Kulow <coolo(a)suse.de>: in http://lists.opensuse.org/opensuse-packaging/2014-08/msg00013.html > We don't have an official roadmap for 13.2, but the experimental roadmap > I made has a Beta1 release on September 18th. Taking user feedback on the -factory mailing list and release dates of upstream into account, I would like to move that 'back' by abut 2 weeks. * Factory users expect 'released' software in Factory now, no longer betas/RCs * GNOME 3.14.0 release is scheduled for Sep 22; OBS power allowing, we are generally 'on the day ready' with the packaging part as well; so on Sep 23 I can 'submit' this all towards Factory Background processes already running: * GNOME:Next is kept up-to-date (currently 3.13.4) and is being run by the GNOME Team plus, looking at the feedback we get, a couple users as well (the repo structure was announced) * starting with the GNOME 3.13.90 release, we will start forwarding this to GNOME:Factory - to get one step closer * I 'envision' (coolo, please let me know if realistic) that we 'submit' 3.13.90 to openSUSE:Factory 'for staging', but not for actual checkin; so we would get Reviews, Staging fallouts as well as openQA runs. * The same we keep up for .91 (Release 3. Sep 2014), .92 (Release Sep 15 2014 - just 'the freeze date'). * By the time 3.14.0 (Sep 24 2014) are out, we should have a good overview of fallouts due to the previous staging/openQA cycles and should thus be able to 'rather quickly submit' to Factory) But all together, I can't be 'in time for the freeze on Sep 18' The alternative is, of course, to ship openSUSE 13.2 with GNOME 3.12.x (as is in current Factory) What is everybody's view on that one? I'm sure opinions will be heard - let's collect them and see what the 'right thing to do(tm)' will look like. Best regards, Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org

2 1

[opensuse-gnome] How to avoid GNOME shutting down due to battery (allegedly) running low?
by Gerald Pfeifer 06 Aug '14

06 Aug '14

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

10 43