Hi,
To the maintainer of Tracker, can you please update the version to
0.8.2. This has a significant fix regarding memory leakage (it was
fixed in 0.8.1). More details at:-
http://mail.gnome.org/archives/tracker-list/2010-April/msg00061.html
Regards
Anshul
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
2010/4/30 Stephen Shaw <sshaw(a)decriptor.com>:
> On Fri, Apr 30, 2010 at 12:32, Atri Bhattacharya <badshah400(a)aim.com> wrote:
>>
>> Hi!
>> I installed the two packages gconf2-branding-openSUSE and
>> gtk2-branding-openSUSE plus dependencies and a log-out did it for me.
>> Except that I had to delete some configuration files to get back to the
>> one panel arrangement. Adding a new user might also do the trick.
>> --
>> Atri
>
> yeah, the way the gconf2-branding-openSUSE works is that it sets the
> default settings. So, once you have logged in its already set some of
> those defaults.
>
>
> Stephen
>
Thanks. Added to the most annoying bugs, just to be sure.
--
S pozdravom / Best regards,
Rasto
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
On Fri, Apr 30, 2010 at 12:32, Atri Bhattacharya <badshah400(a)aim.com> wrote:
>
> Hi!
> I installed the two packages gconf2-branding-openSUSE and
> gtk2-branding-openSUSE plus dependencies and a log-out did it for me.
> Except that I had to delete some configuration files to get back to the
> one panel arrangement. Adding a new user might also do the trick.
> --
> Atri
yeah, the way the gconf2-branding-openSUSE works is that it sets the
default settings. So, once you have logged in its already set some of
those defaults.
Stephen
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hi.
Is anything wrong with Gnome in M6?
Installation process uses Clearlooks theme (probably) [1]
No sonar theme is used by default (never mind, because i don´t like this
theme). By default is used Clearlooks. Although are Sonar and Gilouche
themes installed, they aren´t available in Appearance ->Theme.
Main menu (SLAB) is missing by default. Menu bar is used instead.
Two panels are used - top and bottom, not only one.
No network icon available in systray.
What does it mean? Can we expect some radical modifications? Or is it
just a bug?
Here you are screenshot [2], what i can see after boot from LiveCD and
after installation also.
[1] http://img576.imageshack.us/img576/4483/screenshotinstall.png
[2] http://img87.imageshack.us/img87/9649/screenshotm6gnome.png
--
S pozdravom / Best regards,
Rasto
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
>>> On 4/28/2010 at 13:23, <guido+opensuse.org(a)berhoerster.name> wrote:
>
> home:gberh:branches:GNOME:Factory/brasero -> GNOME:Factory/brasero
>
> https://build.opensuse.org/request/diff/38995
>
> Description: split off brasero-nautilus so that brasero does not depend on
> nautilus, this is needed in order for it to replace xfburn in the
> openSUSE-lxde pattern
no objection from my side regarding the change, it looks good. But I would like to see one addition:
Can you extend the -nautilus subpackage with:
Supplements: packageand(brasero:nautilus)
This would allow the package to automatically be triggered for installation if brasero and nautilus have been selected for installation (thus not
requiring the user to know about this split out package).
Dominique
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Ever since the updates in the last few weeks, I have had much distress
over the ability to use Gwibber. I'm currently at 2.31 now. It simply
doesn't start for me. I was reasonably happy with 2.0 and want to
downgrade back to 2.0, but it seems its not in any of the repositories
anymore.
This is preventing me from doing work-related tasks. Twitter isn't just
for play, you know? :-)
Here's the errors I get when I attempt to start up Gwibber.
Occasionally, I can start gwibber if I restart my computer, but not
every time. only about 25% of the time. :-(
Additionally, in the few times that I have been able to run Gwibber, it
does not save my settings. For example, I have two twitter accounts,
and any tweet I send goes to both accounts, which should not happen.
When I go into advanced settings, I uncheck "Send" in one of the
accounts to prevent it, but as soon as I close the settings, it reverts
back and checks "send".
** (gwibber:1340): WARNING **: Trying to register gtype
'WnckWindowState' as flags when in fact it is of type 'GEnum'
** (gwibber:1340): WARNING **: Trying to register gtype
'WnckWindowActions' as flags when in fact it is of type 'GEnum'
** (gwibber:1340): WARNING **: Trying to register gtype
'WnckWindowMoveResizeMask' as flags when in fact it is of type 'GEnum'
ERROR:dbus.proxies:Introspect error on
com.Gwibber.Service:/com/gwibber/Service: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
(timeout by message bus)
Traceback (most recent call last):
File "/usr/bin/gwibber", line 67, in <module>
client.Client()
File "/usr/lib64/python2.6/site-packages/gwibber/client.py", line 445,
in __init__
self.w = GwibberClient()
File "/usr/lib64/python2.6/site-packages/gwibber/client.py", line 26,
in __init__
self.model = gwui.Model()
File "/usr/lib64/python2.6/site-packages/gwibber/gwui.py", line 34, in
__init__
self.services = json.loads(self.daemon.GetServices())
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in
__call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in
__call__
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622,
in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply:
Message did not receive a reply (timeout by message bus)
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Dear milestone testers!
openSUSE 11.3 looks to be getting in good shape, and there are about two
months to go [1] before the first of the RC releases and three until the
final release. There are numerous things to be excited about with 11.3
as has been the case with every prior release. One of these is
definitely the gtk interface to YaST Sotware Management module [2,3],
much revamped since 11.2. It would be very nice of you to test this
thoroughly for bugs, but also for usability issues and suggest
improvements and peeves :) here and over at bugzilla [4]. In the
following I would like to run you through some of the more notable
changes in the interface. Please note that there is enough time yet to
make minor modifications in the design if required.
1. Main interface revamp: The package-list shown by default is now
categorised by (Packagekit) groups and further separation into
"Available", "Upgrades" and "Installed" tabs has been done away with.
Instead this has been implemented as a separate "Status" filter (below
the Category box). By default this filter is set to "Any Status".
Selecting the "Upgradeable" filter here for example shows all those
packages which have upgrades from the subscribed repositories and brings
out an "Upgrade all" button just below the package list. The
package-list can now show various columns like repositories, etc. The
columns shown by default are Tick-action, package-name, and
package-version.
Selecting a package for installation is now much easier. For packages
that are not installed, check the tick-box to the left of the
package-name in the main list and it is selected for installation.
Installed packages are already ticked, you have to un-check it to have
the package removed. The upgrade button appears just beside the version
column for every package that has an update candidate. For such packages
both the installed and latest available versions are shown in the
version column.
When one selects a package for installation/update/removal it brings
up a summary line in the status bar along with an Undo button (that
undoes this installation/removal request alone) and a link to a "Summary
of changes" box [see point 2].
There is a menu-bar at top that largely mirrors the menu-bar in the
qt version.
2. A "Summary of changes" box: that contains all the packages selected
during the session for installation/update/removal alongwith Undo
buttons for the manually selected packages. Selecting "undo" also
applies the changes to the corresponding dependencies pulled in
automatically by the dep-solver. This replaces the list of changes
sidebar implementation which was a part of the package-manager in its
11.2 and previous avatars. Also with a button to access the "History"
viewer [see point 3].
3. A "History of changes" box: that is accessible from either the
top-menu "Extras" or from the "Summary of changes" box. This shows the
entire history of installed/upgraded/uninstalled packages, and
subscribed/removed repositories, categorised conveniently by date (the
full history-viewer in all its glory has not made it into M5, it should
be in factory [5] soon however and you can already try it from svn [2]
if feeling adventurous :) ). You can select a package and hit the
"jump-to" button to switch to the package in the main interface and
uninstall/re-install a removed package from there. This is in response
to feature # 305859. It enables the user to look up a package installed,
say, recently that he/she does not like or finds unuseable and remove it
and the dependencies it pulled in easily. This should go extremely well
if the Unneeded packages group is implemented later [6].
4. When one switches to the "Repository" categorisation (left-sidebar,
select Repositories from drop-down header), the button "Switch all
packages to that from this repository" shows up just below the main
interface.
All the development work thanks to the yast2-gtk maintainers.
Discussions pertaining to all points have been taking place at
http://groups.google.com/group/yast2-gtk. There is enough time yet for
your suggestions regarding the design and usability of yast2-gtk to be
given thorough consideration for implementation. Please do use it and
let us know what you think of it and the changes you would like to see
to make yast2-gtk more useable. You may reply to this mail for general
feedback and/or put in a bugzilla report if you meet a crash, etc.
Better still you may subscribe to the above google-group and post your
suggestions there.
Happy testing!
Bye
--
Atri
[1] http://www.suse.de/~coolo/opensuse_11.3/
[2] http://en.opensuse.org/YaST2-GTKhttp://svn.opensuse.org/svn/yast/trunk/gtk/
[3] Installed and used by default on GNOME; KDE users may install the
package yast2-gtk using zypper
> sudo zypper install yast2-gtk
and use the interface by issuing the following command as root
> yast sw_single --gtk
[4] https://features.opensuse.org/305859
[5] http://download.opensuse.org/repositories/YaST:/Head/
look for yast2-gtk > 2.21.36
[6] https://features.opensuse.org/300758
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hi all.
I noticed and realized that the Control Center contains double items
in System module.
1) The first is Add/remove software - gnome-packagekit-application,
which is package manager for Gnome and the second is Install/remove
software - YaST software manager.
After overall review i can't see any benefit of package manager for
Gnome-gpk-application. So my question is, why do we have double
software/package manager in the system?
2) Detto for Software Sources. Do we need this item in Control Center,
forasmuch as we can manage repositories in YaST-Software repositories,
or in YaST-Software manager?
3) And the last items are Software update/Software updates. In the
first we can only install updates and the second is used for update
settings. Is it possible to merge these items in one? KDE users have
Kupdatepplet, which allows update and change software update
preferences. They need not use two different application, one for
updates and one for update settings.
4) Next things are Menu Bar (a custom menu bar) and Traditional Gnome
Main Menu. Honestly, these menus are big mess in openSUSE. I'm trying
Ubuntu nowadays, an i have to say that Ubuntu's Menu Bar is clean,
without double items. E.g. openSUSE's Menu Bar:
Click on Applications -> System -> Configuration and you can see a
batch/mixture of hardware, personal or system items. The same items
are available also in System -> Hardware, Personal or System.
Or, take a look in Applications -> Utilities -> Desktop and the same
is in System -> Look and feel.
For clarify what i mean, you can see it on screenshots in attachment.
--
S pozdravom / Best regards,
Rasto
I had a message a couple of days ago from Ryan Paul, lead developer on
Gwibber. He was apologising basically for the state of the Couch-based
Gwibber and telling me that he's dropping it as soon as that version (to
which, I think, Ubuntu are committed for their next release) is out the
door.
He's already started working on Gwibber 3.0 which uses SQLite as a
backend (and so, doesn't add any new esoteric requirements).
I've done a local build and what I have to say is that, although Ryan
says it's a couple of weeks (only a couple of weeks!) off being ready
for public consumption, it's already more stable and usable than the
Couch version.
I'm inclined to commit it to home:Riggwelter:GNOME for a bit more
testing. Given that it's already ahead of the Couch version, I'm also
inclined to propose it for 11.3 which would mean we could drop the whole
Couch stack too as I don't think anything else uses it (hence all the
pain in getting it sorted for Gwibber).
RFC before I commit.
--
James Ogley (riggwelter) openSUSE Member GNOME Team and Planet SUSE
e: riggwelter(a)opensuse.org w: http://opensuse.org/GNOME
t: @riggwelter w: http://www.planetsuse.org
openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org