when out of diskspace, licq continuously creates windows

[petere78]

The following bug has been reported by a Debian user to the Debian bug tracking system. I confirmed it in 1.2.7 and today's CVS snapshot. -- If the filesystem that licq stores the user directory on (i.e. /home) runs out of space, licq pops up an error box _each_ time that it is unable to write to the history file for incoming messages, and unable to write to the users files for status changes. This causes a practically infinite number of error dialogs to have been displayed when I return to my computer; the only option is to xkill licq rather than close all the error windows. I think licq should just display a dialog the first time disk space has been exhausted, in order to warn the user that history events and updates to users info are potentially being lost; or else just exit when it notices that it is unable to write to the file due to -ENOSPC or whatever. Why spam the user like that?

[emostar]

I have a patch for this from Juan, from quite a long time ago. I've never implemented it due to the fact that I thought there was a better way of doing it. But I'll post it here if it helps.

[emostar]

Patch for this bug

[erijo]

Crossreference to the duplicate bug #198.

[erijo]

What about taking the suggestion from onemodal.diff and extend it a bit:

1. Max one message box visible (as in the patch).
2. Group identical messages and display "message repeated x times" when showing that message.
3. Have a button to "skip all pending messages".
4. Show more than one message in a qlistview or something?
5. Make it possible to ignore message for the duration of the session?

Comments?

[emostar]

Replying to erijo:

What about taking the suggestion from onemodal.diff and extend it a bit: 1. Max one message box visible (as in the patch).

OK.

2. Group identical messages and display "message repeated x times" when showing that message.

3. Have a button to "skip all pending messages".

Skip all pending messages, or how about "Skip all repeat messages"? Messages of the same type, or messages of all the same text (But UINs will be different, so that may be too much work).

4. Show more than one message in a qlistview or something?

I think this is better than the above item. Perhaps a "View All" button to show the list, if we decide to not show it as the default.

5. Make it possible to ignore message for the duration of the session?

That can be implemented with a check box in the message dialog. (We can't use standard built-in classes anyways, due to the above items)

Well, that's a lot of changes for this, but I really want to see this fixed before 1.3.4. I'm not gonna be around this weekend, so we can either delay the release another week or put it off... which I already said I would prefer not to do.

[emostar]

Fixed and seems to work after some small bugs were fixed.

[Real Estate for Beginners]

b62bc8c562e018d

[anonymous]

Milestone 1.3.4 deleted