ion3 redraw problem; fixed by latest sid package

Bug #209987 reported by Reuben Thomas
8
Affects Status Importance Assigned to Milestone
ion3 (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: ion3

With hardy, ion3 has an odd problem whose exact source I can't track down where the screen blinks every minute or so. It seems to be drawing something then redrawing the screen as normal again.

Installing the current sid package fixes the problem; since ion3 went stable since the version in gutsy (and there's no version in hardy) it would be nice to have the current sid version in hardy multiverse.

ProblemType: Bug
Architecture: i386
Date: Tue Apr 1 00:43:22 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: ath_hal
Package: ion3 20080207-2
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/sbin:/usr/sbin:/usr/local/epocemx/bin:/home/username/bin:/home/username/local/i686/bin:/home/username/local/bin:/home/username/.luarocks/bin:/home/username/Work/Adsensus/svn/nancy/trunk:/home/username/Work/Adsensus/svn/adsensus/trunk:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
SourcePackage: ion3
Uname: Linux 2.6.24-12-generic i686
UnreportableReason: This is not a genuine Ubuntu package

Tags: apport-bug
Revision history for this message
Reuben Thomas (rrt) wrote :
Revision history for this message
Cesare Tirabassi (norsetto) wrote :

ion3 has been removed from hardy (see bug 177367).
If you have a good experience with the sid package, and since the reason for removal seems to have been resolved in the mean time, you may want to request a sync.
Note that we are pretty late in the hardy cycle, so if this request is not fully justified (see https://wiki.ubuntu.com/FreezeExceptionProcess) it may not be accepted for hardy.

Changed in ion3:
status: New → Incomplete
Revision history for this message
Reuben Thomas (rrt) wrote : Re: [Bug 209987] Re: ion3 redraw problem; fixed by latest sid package

On Tue, 1 Apr 2008, Cesare Tirabassi wrote:

> ion3 has been removed from hardy (see bug 177367).
> If you have a good experience with the sid package, and since the reason for removal seems to have been resolved in the mean time, you may want to request a sync.
> Note that we are pretty late in the hardy cycle, so if this request is not fully justified (see https://wiki.ubuntu.com/FreezeExceptionProcess) it may not be accepted for hardy.
>
> ** Changed in: ion3 (Ubuntu)
> Status: New => Incomplete

I'm unable to do this at the moment and I've not done it before, but I'd be
most grateful if you could.

--
http://rrt.sc3d.org/ | language, n. a dialect with an army (Max Weinreich)

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

I can do the paperwork but some evidence about the suitability of the application is needed. If we upload it now in Hardy this will not have undergone any testing whatsoever, in Ubuntu.
Perhaps, also Ben wants to tell us something about this?

Revision history for this message
Reuben Thomas (rrt) wrote :

On Tue, 1 Apr 2008, Cesare Tirabassi wrote:

> I can do the paperwork but some evidence about the suitability of the
> application is needed. If we upload it now in Hardy this will not have
> undergone any testing whatsoever, in Ubuntu. Perhaps, also Ben wants to
> tell us something about this?

I'm afraid I can't give any evidence other than anecdotal: I have loaded the
sid package, I have had it running for a few days, and it both cured the bug
I was experiencing, and has in every other way behaved as it should. There
are some differences relative to the last version, as the current sid
version is stable, and I think the last Ubuntu version was pre-rc, though I
could be wrong; in any case, there are bug fixes.

Most importantly, the current version is stable, and therefore both fixes
bugs and, I believe, resolves the difficulties with upstream about putting
ion3 in Debian and Ubuntu, as you mentioned. I believe the only reason it's
not in Debian testing is because this has not yet been formally resolved;
but I guess you're in contact with the Debian maintainer.

If there's anything else specific I can test or document, please say.

--
http://rrt.sc3d.org/ | wit, n. educated insolence (Aristotle)

Revision history for this message
Ben Hutchings (benh-debian) wrote :

Currently ion3 is not transitioning into Debian testing because it has not been auto-built on most architectures since it became non-free. However, I'm resolving that. So far as I know, the current version is good enough to release, though it will not have upstream support for the duration of a Debian release or Ubuntu LTS release.

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

Thanks Ben,

I'm subscribing motu-release and Emmet to seek their advice on this.

What do you guys think, should we sync ion3 now that the blocking issue has been resolved, or should we postpone it to Intrepid?

Changed in ion3:
status: Incomplete → New
Revision history for this message
Emmet Hikory (persia) wrote :

Based on the update to Debian bug #415287, I no longer believe ion3 should not be in Ubuntu. Whether it belongs in hardy or intrepid is a harder question, but I don't remember there being any reverse dependencies from my investigation of the removal.

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

Here are the build and install logs. Having seen the positive feedback from Reuben and Ben, the assurance from Emmet about the suitability for Ubuntu, no open bugs on this version in Debian, no rdepends, I'm ready to give my ack.

root@norsetto:/root/debian# apt-get install ion3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  liblua5.1-0
Suggested packages:
  docker ion3-doc ion3-scripts
The following NEW packages will be installed:
  ion3 liblua5.1-0
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
48 not fully installed or removed.
Need to get 86.3kB/848kB of archives.
After this operation, 2306kB of additional disk space will be used.
Do you want to continue [Y/n]?
WARNING: The following packages cannot be authenticated!
  ion3
Install these packages without verification [y/N]? y
Get:1 http://archive.ubuntu.com hardy/universe liblua5.1-0 5.1.2-4 [86.3kB]
Fetched 86.3kB in 1s (75.3kB/s)
Preconfiguring packages ...
Selecting previously deselected package liblua5.1-0.
(Reading database ... 243294 files and directories currently installed.)
Unpacking liblua5.1-0 (from .../liblua5.1-0_5.1.2-4_amd64.deb) ...
Selecting previously deselected package ion3.
Unpacking ion3 (from ..././ion3_20080207-2_amd64.deb) ...
Setting up liblua5.1-0 (5.1.2-4) ...

Setting up ion3 (20080207-2) ...

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

root@norsetto:/root/debian# apt-get install ion3-doc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  dwww doc-central dhelp
The following NEW packages will be installed:
  ion3-doc
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
Need to get 0B/120kB of archives.
After this operation, 700kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  ion3-doc
Install these packages without verification [y/N]? y
Selecting previously deselected package ion3-doc.
(Reading database ... 243400 files and directories currently installed.)
Unpacking ion3-doc (from ..././ion3-doc_20080207-1_all.deb) ...
Setting up ion3-doc (20080207-1) ...

Revision history for this message
StefanPotyra (sistpoty) wrote :

hm... we have it in gutsy, so not having it in hardy would be a regression.

OTOH I'm not too sure, if hunting for it that late in the cycle would be the best thing; likewise, it hasn't entered testing yet.

My current weak preference is to wait for intrepid.

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

I forgot to add that ion3 is in featurefreeze since May 2007 (the gutsy version).
I wasn't very convinced at the beginning, but now, after having used it (albeit for just a day) I think we really would do a service to the community by making this available in Hardy.
Perhaps a backport, even though not ideal, could be a good solution.

Revision history for this message
Martin Pitt (pitti) wrote :

motu-release, please set this to "confirmed" if you want ion3 in hardy/multiverse, or to "wontfix"/"invalid" if not (it'll get autosynced in intrepid).

Changed in ion3:
status: New → Incomplete
Revision history for this message
Cesare Tirabassi (norsetto) wrote :

My fault Martin, in my subscribing frenzy I have incorrectly subscribed the archive. My apologies.
Will it get auto-synced? I see this in the removal bug:

"Sync-blacklisted with the same rationale."

Changed in ion3:
status: Incomplete → New
Revision history for this message
StefanPotyra (sistpoty) wrote :

hm... I guess I'd like to see it in to not cause a regression. ACK #1 from me.

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

Thanks Stefan, setting this to Confirmed then.

Archive admins: can we sync ion3 20080207-2 from Debian unstable (non-free)?
We also need to remove it from the sync's blacklist.

Thanks.

Changed in ion3:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

Getting binaries for hardy...
[Updating] ion3 (0 [Ubuntu] < 20080207-2 [Debian])
 * Trying to add ion3...
  - <ion3_20080207-2.dsc: downloading from http://ftp.debian.org/debian/>
  - <ion3_20080207.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
  - <ion3_20080207-2.diff.gz: downloading from http://ftp.debian.org/debian/>

Changed in ion3:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.