Is there a simple way to upgrade from factory to beta3 and in the future
to the final release?
I'm not sure I always will want to live in factory land.
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Please read all the bug comments / clarifications :) this enhancement
request is not about "out of disk space" alert; it is about reporting
the total of bytes your going to install / remove. Now that total
bytes is showed when the installation step is already started (really
when starting to download the packages).
Other package management tools show the disk variation: SMART and
Synaptics, if I'm not wrong...
On 6/23/08, Michael Mientus <michael.mientus(a)gmail.com> wrote:
> On Wed, Jun 18, 2008 at 3:13 PM, Roberto Mannai <robermann(a)gmail.com> wrote:
> > https://bugzilla.novell.com/show_bug.cgi?id=399239
>
> I like the way YaST works now: it warns you if you are running out of
> disc space.
>
> Mike
>
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi!
As some of you've noticed, the bootloader configuration in openSUSE was not in
best shape for a couple of releases. Therefore, we plan to drop the support
for lilo bootloader from YaST (and thus installation) and leave grub as the
only supported bootloader on i386 and x86_64 in openSUSE 11.1.
The reason is that there are almost no technical advantages to keep both
bootloaders and it makes a lot of sense to focus on a single solution and
improve it. As part of this strategy, we also want to document bootloader
deployment strategies that are supported by the YaST code and where the users
should expect the code to work reliably.
The change will mean:
1) YaST bootloader code for lilo will be dropped
2) YaST installation will offer to not install any bootloader, so an
experienced user can use this to install lilo manually
3) kernel packages will be unable to adapt lilo configuration automatically,
this needs to be done manually after installing a new kernel package
Any feedback appreciated.
Stano
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi all!
I'd like to inform you about a new feature in Yast in openSUSE-11.1-Alpha1.
The feature allows you to configure role based access to yast. The current
implementation is limited only to some yast functionality (the SCR part), e.g.
it doesn't allow to install packages by a non-root user.
WARNING: the DBus support is still in development state, it may be buggy or
whatever else... I ask the brave people here to give it a try.
See http://en.opensuse.org/YaST/DBus_Integration for more details.
There is an example how to enable "time zone change" task for a non-root user.
If you find any problem with the DBus integration report it to
bugzilla.novell.com and assign the bug to me. Do not forget to attach also the
non-root log file (described in the link above).
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I did not know, why the yast2-ldap-server modification stayed on the top
of ChangeLog so long. Now I looked a bit more carefully:
------------------------------------------------------------------
------------------ 2016-6-2 - Jun 2 2016 -------------------
------------------------------------------------------------------
++++ yast2-ldap-server:
[...]
So it will stay on the top of ChangeLog for another eight years :-)
Bye,
CzP
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Synergy on 64 bit systems has been found to crash java quite a bit.
See http://forums.java.net/jive/thread.jspa?messageID=290594
A patch is available at
https://bugs.launchpad.net/ubuntu/+source/synergy/+bug/207057
The synergy project seems to be rather dead, are there any chances this
patch could be applied on the version distributed with os?
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
test
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Gentle readers,
please give me some hints for further investigation
Im using openSUSE 10.3 and MozillaFirefox-3.0.1-1.1
Everytime, I invoke the the home page of the company Renault Deutschland
(http://www.renault.de/) and I move the cursor over the menu (some
JavaScript code), Firefox crashes with a segfault.
I've invoked Firefox from gdb, but gdb complains about missing symbol
tables, and allows operation with very poor information output.
The MozillaFirefox-debuginfo package is installed, but I cannot find a
symbol table for Firefox himself, only for the extensions.
What I see, is this:
gdb /usr/lib/firefox/firefox
GNU gdb 6.6.50.20070726-cvs
Copyright (C) 2007 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/lib/firefox/firefox
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7ca46d0 (LWP 19665)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb5a74b90 (LWP 19785)]
[New Thread 0xb520ab90 (LWP 19799)]
[New Thread 0xb4811b90 (LWP 19800)]
[Thread 0xb4811b90 (LWP 19800) exited]
[New Thread 0xb4010b90 (LWP 19801)]
[Thread 0xb4010b90 (LWP 19801) exited]
[New Thread 0xb4010b90 (LWP 19802)]
[New Thread 0xb4811b90 (LWP 19816)]
[New Thread 0xb37ddb90 (LWP 19817)]
[New Thread 0xb2e73b90 (LWP 19818)]
[New Thread 0xb2672b90 (LWP 19819)]
[New Thread 0xb1e71b90 (LWP 19820)]
[Thread 0xb4010b90 (LWP 19802) exited]
[New Thread 0xb14ffb90 (LWP 19821)]
[Thread 0xb2672b90 (LWP 19819) exited]
[Thread 0xb1e71b90 (LWP 19820) exited]
[Thread 0xb14ffb90 (LWP 19821) exited]
[New Thread 0xb4010b90 (LWP 19835)]
[New Thread 0xb2672b90 (LWP 19836)]
[Thread 0xb4010b90 (LWP 19835) exited]
[Thread 0xb2672b90 (LWP 19836) exited]
[New Thread 0xb2672b90 (LWP 19852)]
[New Thread 0xb4010b90 (LWP 19853)]
[New Thread 0xb1e71b90 (LWP 19866)]
[New Thread 0xb14ffb90 (LWP 19867)]
[New Thread 0xacbebb90 (LWP 19868)]
[Thread 0xb2e73b90 (LWP 19818) exited]
[Thread 0xb1e71b90 (LWP 19866) exited]
[Thread 0xacbebb90 (LWP 19868) exited]
[Thread 0xb1e71b90 (LWP 19870) exited]
[New Thread 0xb1e71b90 (LWP 20149)]
[New Thread 0xb2e73b90 (LWP 20150)]
[Thread 0xb1e71b90 (LWP 20149) exited]
[Thread 0xb2e73b90 (LWP 20150) exited]
[New Thread 0xb2e73b90 (LWP 20185)]
[Thread 0xb2e73b90 (LWP 20185) exited]
[New Thread 0xb2e73b90 (LWP 20235)]
[New Thread 0xb1e71b90 (LWP 20238)]
[Thread 0xb2672b90 (LWP 19852) exited]
---Type <return> to continue, or q <return> to quit---
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7ca46d0 (LWP 19665)]
0xb65f6274 in gdk_window_get_toplevel () from /usr/lib/libgdk-x11-2.0.so.0
(gdb)
Thank You so much,
Yours sincerely
Christoph-Erdmann Pfeiler
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
---------- Forwarded message ----------
From: Andrew Joakimsen <joakimsen(a)gmail.com>
Date: Thu, Jul 24, 2008 at 6:52 PM
Subject: Asterisk & Zaptel Packages Maintainer
To: opensuse-buildservice(a)opensuse.org
Who is responsible for the Asterisk and Zaptel packges in the
network:telephony repo?
Or if that is not how it works how can someone correct errors with
these packages?
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Starting from the time of the below Bugzilla action, I have been unable,
logged in or not, with any browser on any OS to load any Bugzilla bug page,
eventually getting an error 504 (gateway time-out) with each attempt to do
so. Query pages, bug lists & other web sites still work. Is this happening to
anyone else?
On 2008/07/24 03:05 (GMT-0600) bugzilla_noreply(a)novell.com apparently typed:
> https://bugzilla.novell.com/show_bug.cgi?id=270229
>
> User werner(a)novell.com added comment
> https://bugzilla.novell.com/show_bug.cgi?id=270229#c8
>
>
> Dr. Werner Fink <werner(a)novell.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Resolution| |WONTFIX
>
>
>
>
> --- Comment #8 from Dr. Werner Fink <werner(a)novell.com> 2008-07-24 03:05:35 MDT ---
> Just do
>
> echo 'PS1="\h:\W # "' >> /root/.bashrc
>
>
--
"Do not let the sun go down while you are still angry."
Ephesians 4:26 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org