Dear core developers of Opensuse,
I woulod like to valuably and with highest respect ask You, why it is
not possible to include Brltty daemon to The Opensuse official repository?
Brltty is depend on libicui and other libraries and it is really not easy to
find compatible libraries to use brltty.rpm downloaded from The official
Brltty WEB site. Susbblinux screen reader, eventhough it can be downloaded
from repository, it supports only Com serial port and speech-dispatcher and
if visually impaired user want to constructively cooperate with Your
development team, without access to The console, it is not easy. For
example, setting The necessary new values by using gconf.
I would like to initiate constructive discussion about including Brltty to
The official Opensuse repository. I know, that console based screen readers
such as Yasr, Speakup are based on speech-dispatcher to be usable with sound
cart and with Espeak synthesizer.
Believe me, that i do not want to intrude You, but try to imagine, that
You are no sight and You want to access The Opensuse console. Not many new
computers are equipped with COM serial port and braille devices, which are
using COM ports will be ralely used in future.
If suseblinux is now more advanced and can use for example Tieman
Braille Voyager connected throught The USB port, please let me know.
By the way, i tested Suseblinux and i think, that it is one of The best
awailable console based screen readers for Linux in general. It is simple
and can reliably read many necessary information without user need to use
many complex functions, which can be inwoked by various hod keys.
But i found out, that Orca and Espeak are working reliably according to The
my attempts, when i executed Orca from The console. And somebody of You
modified Espeak and Pulseaudio, so The speech responsiveness is
approximately 50 or 60 percent better than while working with Opensuse 11.2
live CD Gnome.
So please, if it is not too expensive, would i please somebody of us to try
to prepare Brltty.rpm for Opensuse?
Here is direct download link for downloading latest .rpm Brltty package.
http://mielke.cc/brltty/releases/brltty-4.1-1.i386.rpm
Source .rpm can be downloaded by using
http://mielke.cc/brltty/releases/brltty-4.1-1.src.rpm
Please keep in mynd, that triing to use rpm -i --nodeps .rpm
Package file will not solve issues with dependencyes. I did not tried to
install Brltty by this way while working with Opensuse 11.3 milestone latest
version, but if YOu did not include necessary .so libraryes, on which Brltty
depends on, it will probably not work.
Thank You for any advice.
With kindness regards.
Janusz Chmiel
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hello,
In the days of fast boot and all that, I was wondering if many people
see the value of having tomboy added to the panel by default.
I, for one, always remove it from every new install I do.
Do a lot of people use it frequently enough to justify that it is added
by default?
Cheers,
Magnus
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Apologies if anyone gets this twice, i think it was rejected the first time:
Hey,
Personally, I use tomboy a lot. I'd use it even more if only I had a working
synchronisation method for my laptop and work desktop.
Now for something slightly more technical ;) The simplest way to decrease
startup time is to AOT the mono assemblies and also the tomboy assemblies.
This will also reduce memory usage if you have multiple mono applications
running at the same time (banshee + tomboy anyone?) as the AOT'ed data can
be shared exactly as if it were a standard native library.
If someone is interested in getting some hard figures about required startup
time they could benchmark:
1) Cold start tomboy (nothing is AOTed)
2) Cold start tomboy (AOT-ing all tomboy assemblies first)
3) Cold start tomboy (AOT-ing all .NET libraries as well as tomboy libraries
first)
4-6) Warm start of the above.
This is likely to be pretty time-consuming as the only way I know to
reliably 'cold start' an application is to reboot ;) It would also require
you to put in an "Application.Quit ()" inside tomboy so that as soon as
everything loads, it exits, thus allowing you to easily measure the startup
time.
Alan.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Guys,
I'm trying to build 2.30 on openSuSE 11.0 (latest build from openSuSE is the
three year old 2.22). After a crash course on dependency resolution with
jhbuild, I have made it to module 75/238 (libproxy) which relies on the mozilla
xulrunner jsapi.h header.
I have installed every version of mozilla mozilla-xulrunner192-devel I could
(contains jsapi.h), but no help. There was no help from the user list, so it was
suggested I try here. Any suggestions?
The current hangup is:
gcc -DPACKAGE_NAME=\"libproxy\" -DPACKAGE_TARNAME=\"libproxy\"
-DPACKAGE_VERSION=\"0.2.3\" "-DPACKAGE_STRING=\"libproxy 0.2.3\""
-DPACKAGE_BUGREPORT=\"nathaniel(a)natemccallum.com\" -DPACKAGE=\"libproxy\"
-DVERSION=\"0.2.3\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DSTDC_HEADERS=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STDLIB_H=1
-DHAVE_MALLOC=1 -I. -I../../src/lib -DXP_UNIX -DJS_THREADSAFE
-I/opt/gnome2/include/xulrunner-1.9.0.13/stable -I/opt/gnome2/include/nspr -g
-std=c99 -g -O2 -DPLUGINDIR=\"/opt/gnome2/lib64/libproxy/0.2.3/plugins\"
-DSYSCONFDIR=\"/opt/gnome2/etc\" -D_POSIX_C_SOURCE=1 -MT mozjs_la-mozjs.lo -MD
-MP -MF .deps/mozjs_la-mozjs.Tpo -c mozjs.c -fPIC -DPIC -o
.libs/mozjs_la-mozjs.o
mozjs.c:32:19: error: jsapi.h: No such file or directory
mozjs.c:35: error: expected '=', ',', ';', 'asm' or '__attribute__' before
'dnsResolve'
mozjs.c:70: error: expected '=', ',', ';', 'asm' or '__attribute__' before
'myIpAddress'
mozjs.c:83: error: expected specifier-qualifier-list before 'JSRuntime'
mozjs.c: In function 'ctxs_free':
mozjs.c:92: error: 'ctxStore' has no member named 'ctx'
mozjs.c:92: warning: implicit declaration of function 'JS_DestroyContext'
mozjs.c:92: error: 'ctxStore' has no member named 'ctx'
mozjs.c:93: error: 'ctxStore' has no member named 'run'
mozjs.c:93: warning: implicit declaration of function 'JS_DestroyRuntime'
mozjs.c:93: error: 'ctxStore' has no member named 'run'
mozjs.c:94: error: 'ctxStore' has no member named 'cls'
mozjs.c:94: error: 'ctxStore' has no member named 'cls'
<snip>
mozjs.c:185: error: 'rval' undeclared (first use in this function)
mozjs.c:185: warning: passing argument 1 of 'px_strdup' makes pointer from
integer without a cast
make[3]: *** [mozjs_la-mozjs.lo] Error 1
make[3]: Leaving directory `/home/david/apps/bld/gnome2/libproxy-0.2.3/src/plugins'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/david/apps/bld/gnome2/libproxy-0.2.3/src/plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/david/apps/bld/gnome2/libproxy-0.2.3/src'
make: *** [all-recursive] Error 1
*** Error during phase build of libproxy: ########## Error running make ***
[75/238]
I suspect in this situation, I don't have the correct version of xulrunner
installed, but I have installed 190, 191, 192 which are all the versions
available and I still get this error.
I would really like to get a newer version of gnome built on my laptop. Moving
to a later openSuSE release or another distro for this install is out of the
question due to the fglrx driver requirements for graphics (screwed by ATI/AMD
when they overnight made 'legacy' drivers out of all pre 2400 series hardware).
I had openSuSE 11.2 with gnome 2.28 on it, but had to downgrade to get
reasonable driver performance.
I also have another drive for this laptop with Arch Linux on it (I live without
the driver there). It has a current gnome on it, but my daily driver is this
openSuSE 11.0 setup and will be until a new laptop is purchased.
Aside from the immediate libproxy issue. If anyone knows a better way to update
gnome on this box, or any secret for meeting all the jhbuild dependencies before
kicking off the build, I am all ears :p
Thanks for any help you can give.
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Listmates,
On openSuSE 11.0 (gnome 2.20) on an x86_64 box, for some reason nautilus is
seeing all files as plain text. Including, .ps .pdf .odt .jpg, etc.. The only
other types it seems to know is 'folder' and 'unknown'. I haven't got a clue as
to what has caused this or how I can fix it. Here is a small screenshot:
(56k)
http://www.3111skyline.com/dl/bugs/gnome/mimetypeMessedUp.jpg
Any thoughts? What to check?
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Listmates,
Working to sort out why gnome died on my 11.0 install, I stumbled across some
absolutely killer gtk-2.0 & metacity themes that caught my eye. If you use
gnome, Xfce, etc.., give them a try and I guarantee you, you will be blown away.
They are available at gnome-look or Xfce-look.org sites or by googling the theme
name. Here is the short list:
Abstract-DarkGlow
Aero-ion3.1
Black Plastic V.2
** Blue-Joy
Correcamins
DarkVision
DiMurrineGTK
Dust (Dust Burnt, and the rest of the Dust ... themes)
Elegant Aurora (and the other Elegant....)
Glow Fire (Lava, Flower, Cinder ...)
Harvest
Industrial-Glacier (GONYX, Lighthouse, Charcoal, Zeta, ...)
Moomex
Nova-Blue (Gold, etc...)
Overglossed
Oxygen-Molecule
River
Shifte_Black
ShinyBlack
Silence
** SlicknesS-black
SphereCrystal
Tenebrific-BlueMods
Vision
Xfce-cadmium (many of the Xfce themes also have matching gtk themes)
Zniavre
** (top 2 for me - the rest are a close 3rd)
And the screenshot giving an example of Blue-Joy and SlicknesS-black:
(86k)
http://www.3111skyline.com/dl/ss/gnome/gnome-bling.jpg
P.S. also posted to the opensuse-gnome list due to relevance in a rare
cross-post... don't get your knickers in a twist :p
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Dear core developers of Opensuse Gnome,
Is there any command, which would enable me to install at-spi from The
console? But while i have read Yours last answer to my question, You are
very near to The latest version of Gnome, which You would probably like to
incorporate to Opensuse and this version will communicate with Orca by using
Dbus. I would like to kindly please You with The highest respect to Yours
development team, if You would try to do Yours best to enable visually
impaired users of Opensuse to use all administrative applications.
Opensuse has been one of The first Linux distribution, which enabled
visually impaired users of Orca to use applications with The root privileges
while running Opensuse Gnome live CD and even after installation. Also
Opensuse 11.2 Gnome enabled users this. What i Am appreciating very, very
much on Opensuse is The fact, that there are never at-spiregistry crashes.
Those random crashes are often occurring in ubuntu after terminating
application such as update manager. Opensuse did never crashed by this way.
But i found out one very bad think while using Opensuse 11.2 and 11.1. I
observed random crashes while terminating Yast control centre after
performing The Opensuse update. After pressing ALT+F4 i have received a
error message related to GTK and some memory conflict. I will try to exactly
reproduce The error and i will send it. But better will be to debug Opensuse
11.3 milestone 2, because new version of Gnome and other modules can
eliminate this errors.
Thank You for ammazing boot screen speaker, which can enable visually
impaired users of Opensuse to even select their wanted language while using
Opensuse boot screen.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hi Vincent,
I know, I should file a bug on bugzilla, but I am a bit tired now and my
wife is complaining for my abusing on time dedicated to computer, so
please find in attach the stack trace I collect for Evolution.
As side comment: I had to install a lot of debuginfo package, in order
to be able to launch gdb, without getting a lot of the missing packages
error.
Hope the file will be of some help.
Cheers,
Marco Calistri
---
linux-oSUSE-11-3.site 2.6.33-rc7-3-default #1 SMP 2010-02-12 17:37:20
+0100 i686 athlon i386 GNU/Linux Gnome 2.29.90
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Dear core developers of Opensuse 2 Milestone live CD GNome,
I Am very unhappy, because i would like to constructively participate in
The testing Orca support in Opensuse Milestone 2 live CD Gnome, but now, all
hod keys in Gnome are not working. For example, ALT+F2, ALT+F1 are not
awailable. Orca is speaking initial messages and is giving me setup
questions, i can answer to all Orca setup questions, but how to run Orca? I
even tried to activate The console, loggin as Linux user,
Then i used
sudo su
And i used gdm-stop
To terminate all Gnome related modules.
I run orca from The console and i answered to all Orca setup questions.
But when i typed startx, Gnome has been started successfully but Orca
did not start.
I Am ready to cooperate with Your development team by testing and debugging,
it seems to me, that Orca is not broken at all, but somethink with Gnome is
not OK. Is there any workaround to run Orca? Eventhough i answered The Orca
setup question Do YOu want to start Orca at login by answer yes, Gnome can
not start this screen reader. And because hod keys are not working, it is
inpossible for me to run Orca from Gnome.
I used DD command to transver Opensuse milestone 2 live CD Gnome to it,
thank You, that YOu are using complex techniques to prepare .iso images,
which can be burned to a CD or to be stored to The USB flash disks. This
technique is very good for testing milestone releases, because burning and
working with CD is overburning laser heads and servo mothors, which are
moving with The laser head inside CD Burner drive.
Thank You for any help.
Gnome is being started without issues, i do not have to even type linux and
pressing enter, support for sound carts is also working very well.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org
Hi,
Here's a list of features that I think we should try to implement for
11.3; those are mostly not-too-big tasks, so I think anybody could step
up and help. This list is in no way the complete stuff.
There are three categories in this list:
+ removing old stuff and migrating to the new "solutions"
+ trying to not install unneeded packages by default (that should help
with the livecd size too, and so we could add more useful apps)
+ offering a better user experience by tweaking various small things
Note that this list doesn't contain any very ambitious goal, and I'd
love if people would want to work on such goals (like improving the
login performance, or really solving the "install codecs in a legal way"
issue). So we can discuss other goals too :-)
Switch from beagle to tracker
https://features.opensuse.org/307899
=> Luis was working on this
Empathy as default IM client
https://features.opensuse.org/308281
=> again :-) Can we finally just do it?
archive mounter
https://features.opensuse.org/308344
=> really easy to implement. You can do it today, with a submission in
the build service.
at-spi2 by default
https://features.opensuse.org/308451
=> I think this is mostly implemented now, but this needs testing. Any
volunteer?
New notification theme
https://features.opensuse.org/308457
=> might be solved with the new notification-daemon release that will
be out at some point: there's a new theme there (slider) that we
could possibly use. Someone should investigate.
Only install a recommended subset of screensavers by default
https://features.opensuse.org/308474
=> the hardest part is that someone needs to decide which subset to
install. This doesn't require any technical knowledge.
Optimize preselection of games on GNOME livecd
https://features.opensuse.org/308477
=> this is similar to the screensaver thing. No technical knowledge
required. (Also, we can install games that are not part of
gnome-games!)
Drop glib/gtk/gnome 1.x stack
https://features.opensuse.org/308601
=> I was working on it at the beginning of January. It's nearly ready,
but there are 2 or 3 packages left to handle, and help would be
appreciated there. Ping me if you want to help.
GNOME LiveCD: look if we can remove qt
https://features.opensuse.org/308826
=> I had taken a look at this for 11.2, but this wasn't possible at
that time. It should be doable for 11.3, though. The first part is
some analysis that anybody can do by just launching the livecd. I
can help people start if needed.
Remove Hal by default on opensuse 11.3
https://features.opensuse.org/308762
=> I'd love to at least not have hal on the livecd
I'm publishing this list here so that people who were wondering what to
do can start actively working on something :-)
Vincent
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org