August 2011 - openSUSE GNOME - openSUSE Mailing Lists

[opensuse-gnome] GNOME Activity Journal
by Adam Tauno Williams 25 Nov '11

25 Nov '11

When I run gnome-activity-journal I see no events. Possibly this is because if I go to preferences / plugins I see nothing listed? Should I see plugins? Are they required? If so, where to they come from? /usr/bin/zeitgeist-daemon is running. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

3 14

[opensuse-gnome] GNOME:Factory at 3.1.5
by Dimstar / Dominique Leuenberger 29 Sep '11

29 Sep '11

Hi Gnomies! I just wanted to give you a heads up that last night, with the help of mighty Darix, GNOME:Factory has been updated to version 3.1.5, which is the latest release on the way to 3.2. As always, 3.1.x is considered 'unstable', but in my experience it works very well. We will keep the packages for a few days in GNOME:Factory and hope to hear of things breaking since the last update, sort those breaks out and will forward the stack to openSUSE:Factory after that. There are some changes on packaging level, coming from ABI and API breaks. The noteworthy ones are (Mails with more details will follow for each of them): * gnome-menus => Version 3.1.5 is ABI and API incompatible to the so far included version 3.0.1. A compatibility package called gnome-menus-legacy has been introduced. * python-gobject (this is currenlty in GNOME:Factory AND also already in devel:languages:python): python-gobject 2.90.x (on the road to 3.0) changed from the 'old' gobject bindings to pure gobject-introspection based bindings. Any application can only use one kind of binding at once. As a migration path, the old version has been renamed to python-gobject2 (as it was once in the past.. many packages still buildrequire python-gobject2-devel). python-gobject is the new gi-based binding. Let's get the test systems up and rolling.. let's make sure everything rocks our world! Greetings, Dominique / DimStar -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

5 24

[opensuse-gnome] GNOME Desktop: Why diversity on the "BLACK" tones
by Marco Calistri 01 Sep '11

01 Sep '11

Hi, I Noticed in the past and currently that GNOME is generally representing a "less dark" BLACK than KDE, when showing black text on the screen. Tonite I noticed other little detail: under GNOME 3.0.2 Desktop, Evolution is showing a TXT composed email as light-black/gray tone, while an HTML composed email appears with a better, brilliant, darker black. Wonder why this happens and if exists a way to set a "super dark" black, independently of the type of the desktop environment/application. Please see the attached pictures, to better understand what I mean: Evolution under GNOME 3.0.2 HTML Rendering: http://www.flickr.com/photos/amdturion/6074882873/sizes/l/in/photostream/ Evolution under GNOME 3.0.2 TXT Rendering: http://www.flickr.com/photos/amdturion/6074882749/sizes/l/in/photostream/ Cheers, -- Marco Calistri (amdturion) opensuse 11.4 Celadon - Linux 2.6.37.6-0.7-desktop x86_64 AMD Turion(tm) 64 Mobile Technology MK-36 - GeForce Go 6150 Gnome 3.0.2 -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

4 12

Re: [opensuse-gnome] RFC: Dropping xsane in favour of simple-scan from the default gnome pattern
by Atri 30 Aug '11

30 Aug '11

On Sat, 2011-08-27 at 09:11 -0500, william witt wrote: > Does simple scan still use the sane backend? The scanner setup in > yast still needs to work. Personally, I'm concerned with scqanning > via network. > > Will > > On Aug 27, 2011 8:40 AM, "Atri" <badshah400(a)aim.com> wrote: > > Hi! > > I would like to request considering dropping xsane (the scanning > > application so the default in openSUSE GNOME) from the default gnome > > pattern in openSUSE 12.1 in favour of simple-scan [1], which is (as > the > > name suggests) a much simpler and, in my opinion, more usable > scanning > > utility. Simple-scan is also a gtk3 app making it integrate nicely > in > > GNOME 3+. > Hi! Yes, it does use sane, similar to xsane. From the description of the utility: "Simple Scan is basically a frontend for SANE - which is the same backend as XSANE uses. This means that all existing scanners will work and the interface is well tested." Bye -- Atri -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

2 1

[opensuse-gnome] Banshee Update on GNOME:Apps
by Nelson Marques 29 Aug '11

29 Aug '11

Hi all, I've submitted today the update to Banshee 2.1.3 for GNOME:Apps (will update with the next 24 hours the Banshee repos with Banshee and banshee-community-extensions). SR: 80140. NM -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

1 0

[opensuse-gnome] ATI fglrx and GNOME3 soon...
by Nelson Marques 27 Aug '11

27 Aug '11

>From the bug report I've filled a long time ago, it seems that ATI users will soon be able to enjoy GNOME3 with fglrx driver (catalyst). Here's a hard copy of one of the replies I got on the bug report which suggests that the bug has been fixed and is on the 4 week internal test period by AMD: "--- Comment #65 from pierre.boudier(a)amd.com <pierre.boudier(a)amd.com> 2011-08-22 10:38:28 CDT --- hi all, I would like to clarify a little bit this discussion: - this bugzilla is not owned by AMD, and while we try to monitor it (along other sources), it is not possible for AMD to immediately detect and jump into reports - we actually noticed this when I wrote my first post (2011-08-10), and the fix was made internally on the 8/12 - the catalyst release cycle will branch our internal dev tree within 4 weeks, and will go into 4 weeks of QA before we make the driver public. - since engineering is not focused with release management, we usually can't commit to exact release data since that sometimes change (sometimes fixes are introduced earlier, sometimes deferred) - finally, the crux of the issue here is that gnome developers should have actually contacted AMD about this issue before releasing something which only works on nvidia. we do appreciate constructive feedback and are committed to fix issues; linux is an important Os for AMD. regards, Pierre B." Good news at last for some of us... NM -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

3 3

[opensuse-gnome] RFC: Dropping xsane in favour of simple-scan from the default gnome pattern
by Atri 27 Aug '11

27 Aug '11

Hi! I would like to request considering dropping xsane (the scanning application so the default in openSUSE GNOME) from the default gnome pattern in openSUSE 12.1 in favour of simple-scan [1], which is (as the name suggests) a much simpler and, in my opinion, more usable scanning utility. Simple-scan is also a gtk3 app making it integrate nicely in GNOME 3+. Please note that the request is to drop xsane from the default pattern alone, but not to have it removed from the OSS repo at all. Anyone who wants to use xsane instead could still do a "zypper install xsane" and with the default repositories enabled that would be that. For factory testers, simple-scan is already in Factory, and you can simply do "zypper in simple-scan" to install and start testing simple-scan. xsane should already be a part of your installation at the moment. Thanks and bye -- Atri [1]: http://ftp.gnome.org/pub/GNOME/sources/simple-scan/3.1/ https://launchpad.net/simple-scan -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

2 1

Re: [opensuse-gnome] ATI fglrx and GNOME3 soon...
by Damien Radtke 27 Aug '11

27 Aug '11

Apparently there was some miscommunication about where the line of contact was for Linux AMD users. The problem had reportedly been sent to them (I believe roughly around April), but it ended up being sent to a now defunct communication channel, despite it still being listed on their website. Either way, the light is finally at the end of the tunnel. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

1 0

[opensuse-gnome] gnome-phone-manager error
by Marco Calistri 20 Aug '11

20 Aug '11

Hello, I tried to configure Broadband mobile on my Nokia E63 connecting it true Bluetooth to access Internet and it succeed, however the only way I found to disconnect this connection is by roughly switch off the Bluetooth, apparently there are not any additional controls available. If I try to start gnome-phone-manager I get this error: marco@linux-turion64:~> date sab 20 ago 2011, 15.09.08, BRT marco@linux-turion64:~> uname -a Linux linux-turion64.homelinux.org 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux marco@linux-turion64:~> gnome-phone-manager Gtk-ERROR **: GTK+ 3 symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported aborting... Any suggestions? -- Marco Calistri (amdturion) opensuse 11.4 Celadon - Linux 2.6.37.6-0.7-desktop x86_64 AMD Turion(tm) 64 Mobile Technology MK-36 - GeForce Go 6150 Gnome 3.0.2 -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

1 0

[opensuse-gnome] gdmflexiserver and LightDM
by Guido Berhoerster 15 Aug '11

15 Aug '11

Hi, as of recently LightDM (http://www.freedesktop.org/wiki/Software/LightDM) has started shipping a gdmflexiserver compatibility script which potentially conflicts with the gdmflexiserver binary delivered by the gdm package. Currently, I'm not including it in the package since putting it in a different path or renaming it pretty much defeats its purpose. The best way that I can think of to let both coexist and allow it work as intended would be to rename /usr/bin/gdmflexiserver in both gdm and lightdm and to create a separate package with a wrapper script that calls the correct gdmflexiserver based on the currently running display manager (e.g. test for GDMSESSION and a LightDM-specific environment variable). Any opinions on this or different suggestions? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

1 0