| 1 |
On Saturday 20 August 2005 16:08, Zac Medico wrote: |
| 2 |
> Ian K wrote: |
| 3 |
> > --------------------------- ACCESS VIOLATION SUMMARY |
| 4 |
> > --------------------------- |
| 5 |
> > LOG FILE = |
| 6 |
> > "/tmp/sandbox-media-video_-_f4l-0.2-25033.log" |
| 7 |
> > |
| 8 |
> > open_wr: /usr/qt/3/etc/settings/.qtrc.lock |
| 9 |
> > open_wr: /usr/qt/3/etc/settings/.qtrc.lock |
| 10 |
> > ----------------------------------------------------------------------- |
| 11 |
> >--------- |
| 12 |
> |
| 13 |
> Ian, I got the same result here. I will post a comment on bug 82154. If |
| 14 |
> you don't care about the sandbox violation, you can temporarily disable |
| 15 |
> the sandbox to work around the problem like this: |
| 16 |
> |
| 17 |
> FEATURES="-sandbox" emerge f4l |
| 18 |
|
| 19 |
addpredict /usr/qt/3/etc/settings. It's a common problem with Qt apps. It's |
| 20 |
even in both qt.eclass and kde.eclass (although they both use addwrite |
| 21 |
rather than addpredict!?) |
| 22 |
|
| 23 |
-- |
| 24 |
Jason Stubbs |
Archives