Am Thursday 13 September 2007 schrieb Eberhard Moenkeberg:
Hi,
On Thu, 13 Sep 2007, Stephan Kulow wrote:
As the Beta3 Live CDs were hardly useful, I decided to delay it till we
have another build that works good enough, so here they are:
Hi,
On Fri, 14 Sep 2007, Stephan Kulow wrote:
Am Thursday 13 September 2007 schrieb Eberhard Moenkeberg:
On Thu, 13 Sep 2007, Stephan Kulow wrote:
As the Beta3 Live CDs were hardly useful, I decided to delay it till we
have another build that works good enough, so here they are:
Hi,
I just got this one and would have a few questions on that.
h_root wrote:
here is the log from the commit of package mozilla-nss
checked in at Fri Sep 14 00:46:19 CEST 2007.
--- GNOME/mozilla-nss/mozilla-nss.changes 2007-07-27 17:59:00.0
+0200
+++
M9. wrote:
(it is like this firewall does the opposite job..)
I don't really see how your net is configured.
My firewall is on the router/gateway, not on my desktop.
my desktop access is only managed by the ordinary permission system
(anyway all the ports are shut down except ssh)
jdd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
This morning i had to shut down the firewall to enter my Lan.
Printing was impossible, and also accessing the other pc's and laptops
in the network.
What i do not understand is why this firewall prevents me from entering
other pc's in the
Leonardo Chiquitto wrote:
I must say that this is kind of confusing, considering the help screen:
(...)
patches, pchList patches
list-updates, luList updates
xml-updates, xu List updates and patches in xml format
As we have list-updates
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Friday 2007-09-14 at 11:01 +0200, jdd wrote:
(it is like this firewall does the opposite job..)
I don't really see how your net is configured.
My firewall is on the router/gateway, not on my desktop.
my desktop access is only
On Sat, 8 Sep 2007, Andreas Vetter wrote:
On Sat, 8 Sep 2007, Bernhard Walle wrote:
* Andreas Vetter [EMAIL PROTECTED] [2007-09-08 12:25]:
I updated a x86_64 machine from beta1 to beta3. After the packages were
installed I found the machine in a reboot loop. The grub boot loader
Hi all,
on a fresh install I noticed the following Problems:
1.) there will be a file Desktop in the initial users home directory preventing
gnome to create a directory of the same name. This directory has to be removed
manually to get a working gnome desktop
This is true for x86_64 and x86
On Fri, 14 Sep 2007, Andreas Vetter wrote:
On Sat, 8 Sep 2007, Andreas Vetter wrote:
On Sat, 8 Sep 2007, Bernhard Walle wrote:
* Andreas Vetter [EMAIL PROTECTED] [2007-09-08 12:25]:
I updated a x86_64 machine from beta1 to beta3. After the packages were
installed I found
Am Mittwoch, 12. September 2007 schrieb Florin Samareanu:
use either iwl or ipw. if you use ipw, please install ipw3945d. if you
use iwl, make sure the firmware package is installed.
sorry for the delay, i just dont had the time to test this. So, iwl seems
not to work with my comp, it seems to
Am Samstag, 8. September 2007 schrieb Carlos Gonçalves:
Em Sexta, 7 de Setembro de 2007, o Jens Nixdorf escreveu:
Works now for me with some options in /etc/pm/config.d. For more
info look into the bugreport. In my case it is S2RAM_OPTS=-f -p,
but maybe you need other options, so you have
* Jens Nixdorf [EMAIL PROTECTED] [Sep 14. 2007 15:12]:
Am Mittwoch, 12. September 2007 schrieb Florin Samareanu:
use either iwl or ipw. if you use ipw, please install ipw3945d. if you
use iwl, make sure the firmware package is installed.
sorry for the delay, i just dont had the time to
On 9/14/07, Wolfgang Rosenauer [EMAIL PROTECTED] wrote:
So where is the bug number in that changelog entry? We are after beta3
so I'd expect a bugnumber here.
There is no bug number because nobody has used the functionality that
this supports. The second someone would try to use it there
jacob berkman wrote:
On 9/14/07, Wolfgang Rosenauer [EMAIL PROTECTED] wrote:
So where is the bug number in that changelog entry? We are after beta3
so I'd expect a bugnumber here.
There is no bug number because nobody has used the functionality that
this supports. The second someone would
On Fri, Sep 14, 2007 at 02:49:11PM +0200, Joachim Bremer wrote:
on a fresh install I noticed the following Problems:
1.) there will be a file Desktop in the initial users home directory
preventing
gnome to create a directory of the same name. This directory has to be removed
manually to
Hello,
Christoph Thiel wrote:
1.) there will be a file Desktop in the initial users home directory
preventing
gnome to create a directory of the same name. This directory has to be
removed
manually to get a working gnome desktop
This is true for x86_64 and x86
Please file a bug
On Fri, Sep 14, 2007 at 04:21:21PM +0200, Peter Czanik wrote:
Christoph Thiel wrote:
1.) there will be a file Desktop in the initial users home directory
preventing
gnome to create a directory of the same name. This directory has to be
removed
manually to get a working gnome desktop
On 9/14/07, Christoph Thiel [EMAIL PROTECTED] wrote:
On Fri, Sep 14, 2007 at 02:49:11PM +0200, Joachim Bremer wrote:
3.) After enabling desktop effects all windows on a gnome Desktop dont't
have a border. That means you not able to move (except with holding the
alt-key), resize or close
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jdd schreef:
M9. wrote:
(it is like this firewall does the opposite job..)
I don't really see how your net is configured.
My firewall is on the router/gateway, not on my desktop.
my desktop access is only managed by the ordinary
Hi,
2007/9/14, Christoph Thiel [EMAIL PROTECTED]:
On Fri, Sep 14, 2007 at 02:49:11PM +0200, Joachim Bremer wrote:
3.) After enabling desktop effects all windows on a gnome Desktop dont't
have a border. That means you not able to move (except with holding the
alt-key), resize or close the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carlos E. R. schreef:
The Friday 2007-09-14 at 11:01 +0200, jdd wrote:
(it is like this firewall does the opposite job..)
I don't really see how your net is configured.
My firewall is on the router/gateway, not on my desktop.
my desktop
Hello,
How do I configure 's2ram' and 's2disk' in 10.3-factory? I looked at the
config files, where it was in 10.2, but neither of them exist, and there
isn't any information about changes in /usr/share/doc/packages/suspend/
just some 10.1 related info, which does not seem to apply even to 10.2,
Am Freitag, 14. September 2007 schrieb Peter Czanik:
Hello,
How do I configure 's2ram' and 's2disk' in 10.3-factory? I looked at
the config files, where it was in 10.2, but neither of them exist, and
there isn't any information about changes in
/usr/share/doc/packages/suspend/ just some 10.1
M9. wrote:
I am talking about the SuSE-firewall... and the testing of it in 10.3
beta3..
me too. My router is an openSUSE box.
myconcern is to know how is your lan configured (what PC is used as
gateway, what is the internal network, what the external (precise,
with IP's, thanks)
and if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alberto Passalacqua schreef:
It is probably the old and never solved issue with samba high ports, if
you're using samba to share resources.
In the suse firewall configuration file, look for FW_SERVICES_ACCEPT_EXT
and set it to:
On Fri, 14 Sep 2007, Peter Czanik wrote:
BTW: good news: now both utilities work with my motherboard. In 10.2
only s2ram worked (with '-f'), now both of them work, but only from the
command line at the moment. Would be nice to get it working from
gnome/kde/xfce menu again...
It's interesting.
Am Freitag, 14. September 2007 schrieb Gerald Pfeifer:
It's interesting. After I updated FACTORY yesterday, the hotkeys
(both for s2d and s2r) stopped working for me under KDE.
This used to work all the time over the last couple of months, and
manually involving suspend still does.
Its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jdd schreef:
M9. wrote:
I am talking about the SuSE-firewall... and the testing of it in 10.3
beta3..
me too. My router is an openSUSE box.
myconcern is to know how is your lan configured (what PC is used as
gateway, what is the internal
Hi,
Just tried out the Live CD. Pretty much everything in the Live CD
itself works, the only thing I wonder is if it's worth launching
opensuse-updater-kde on the live session; it's really as if a user can
update things from in there.
I tried out the live installer, and it has a lot of rough
M9. wrote:
so, if I understand well you have only one lan (192.168.1.x) with all
the PC on it.
previously you said:
This morning i had to shut down the firewall to enter my Lan.
Printing was impossible, and also accessing the other pc's and laptops
in the network.
What i do not understand
31 matches
Mail list logo
