Bug 363473 - Warring massage "disk is full" when run software manager
Summary: Warring massage "disk is full" when run software manager
Status: RESOLVED FIXED
: 328864 363693 (view as bug list)
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 10.3
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michael Meeks
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-20 23:29 UTC by Andrey Gankov
Modified: 2008-02-28 17:21 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Screen shot (65.35 KB, image/png)
2008-02-20 23:30 UTC, Andrey Gankov
Details
Yast log (402.62 KB, application/zip)
2008-02-21 22:45 UTC, Andrey Gankov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Gankov 2008-02-20 23:29:20 UTC
I install OpenSUSE by default, and i agree with proposal configuration of partition.
At present, i run software manager and always see massage "disk is full". Suspect what cause in boot partition because this partition is small.
That very inconveniently.
Screen shot in attachment.
Comment 1 Andrey Gankov 2008-02-20 23:30:08 UTC
Created attachment 196131 [details]
Screen shot
Comment 2 Cyril Hrubis 2008-02-21 17:48:12 UTC
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 3 Andrey Gankov 2008-02-21 22:45:49 UTC
Created attachment 196450 [details]
Yast log
Comment 4 Jozef Uhliarik 2008-02-22 12:26:04 UTC
Lado could you check it please?
Comment 5 Ladislav Slezák 2008-02-25 12:21:03 UTC
The warning is displayed by the package selector widget, reassigning to yast2-gtk maintainers...
Comment 6 Forgotten User h13THG8RK1 2008-02-25 22:31:42 UTC
I believe this was fixed on a Patch Update to yast2-gtk (do you apply those?). I was pretty sure Boyd Timothy fixed this, but neither bugzilla or the change log is of any help, so perhaps I am wrong.

The disk indicator is currently disabled on the 11.0 code, but will fix that...
Comment 7 Forgotten User h13THG8RK1 2008-02-25 22:32:38 UTC
*** Bug 363693 has been marked as a duplicate of this bug. ***
Comment 8 Forgotten User h13THG8RK1 2008-02-25 22:33:26 UTC
*** Bug 328864 has been marked as a duplicate of this bug. ***
Comment 9 Forgotten User h13THG8RK1 2008-02-27 21:49:05 UTC
Alright, so I added a disk indicator for 11.0, and it should have your issue fixed: similarly to yast-qt, the bell rings only when the space gets less than 500 Mb *and* less than 10%. It only used to have the first, absolute limit, so it rules out small partitions now.

In any case, it also won't popup a dialog at start, just if the space limit is crossed when installing packages. It does show a warning icon which is something the user may not have noticed while operating, but should be noticeable at start.
Comment 10 Forgotten User h13THG8RK1 2008-02-27 21:53:18 UTC
Also, I understand that the dialog can be as irritating as an army of flees, but I really don't think you could convince anyone that its a Major issue. That level has a clear definition of Major Loss of Functionality. They are very strict on what they send as an Update, so no way this could made it through on its own.

I don't have a fix for your system, but it is pretty easy to upgrade your yast-gtk. Checkout bug 352206, comment 10.
Comment 11 Andrey Gankov 2008-02-28 08:01:20 UTC
Ricardo Cruz, thanks.
Comment 12 Andrey Gankov 2008-02-28 13:27:56 UTC
Cruz please help.
I try update yast-gtk from SVN, but i have error:
angel:/home/admin/yast-gtk # make -f Makefile.cvs
y2tool y2autoconf
y2autoconf: Generating toplevel configure.in
y2tool y2automake
y2automake: Copying automakefiles for inclusion
y2automake: Generating toplevel Makefile.am
autoreconf --force --install
configure.in:155: warning: macro `AM_PROG_LIBTOOL' not found in library
configure.in:153: error: possibly undefined macro: AC_DISABLE_STATIC
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:154: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.in:155: error: possibly undefined macro: AM_PROG_LIBTOOL
autoreconf: /usr/bin/autoconf failed with exit status: 1
make: *** [all] Ошибка 1

Please say to me what i need package.
Comment 13 Forgotten User h13THG8RK1 2008-02-28 17:21:18 UTC
Hi. So, I didn't write the build files for yast-gtk and I don't know much about automake & friends -- I use old, rough, bare Makefiles in my little projects.

However, some browsing seems to indicate you either not have libtool, automake or autoconf installed, or they're not functional (a possibility is that you have for instance, both automake-1.4 and automake-1.6 installed, and your libtool-1.6 is only finding the automake-1.4 version -- notice these tools form a chain, so there is a certain version combination that must be followed, otherwise it breaks).

If you say its a fresh system, surely it is that you don't have those development tools installed, so check bug 352206, comment 13.