| Summary: | kde-base/akonadi-4.2.3 throws sandbox access violation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jean-Pierre de la Croix (jdelacroix) <ajpl.delacroix> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | vapier |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log for kde-base/akonadi-4.2.3 | ||
|
Description
Jean-Pierre de la Croix (jdelacroix)
2009-05-13 14:46:46 UTC
Created attachment 191160 [details]
build.log for kde-base/akonadi-4.2.3
Downgrading sandbox from 1.9 to 1.6-r2 makes no difference to outcome of the build. @sandbox-team: We in kde team cant reproduce this, so i am going ask you as experts for sandbox matter :] I worked around it by disabling sandbox (FEATURES="-sandbox" emerge =kde-base/akonadi-4.2.3), emerging the package, and then reenabling it. Now I can reemerge it just fine with sandbox enabled. The difference is that when I first attempted to emerge akonadi, it was while I was chrooted into the install. Now I am reemerging it on a running system and I no longer get the sandbox access violation. It may just work because .config et al. now exist from the previous build (when I used the workaround), but that is just my guess. i dont know what kind of insight you're looking for ... the error message seems pretty straight forward to me /usr/bin/nepomuk-rcgen is doing mkdir(/root/.config) when it shouldnt be. remove the dir on your system, remove userpriv/usersandbox from your FEATURES, then emerge akonadi with USE=semantic-desktop. (In reply to comment #5) > i dont know what kind of insight you're looking for ... the error message seems > pretty straight forward to me > > /usr/bin/nepomuk-rcgen is doing mkdir(/root/.config) when it shouldnt be. > remove the dir on your system, remove userpriv/usersandbox from your FEATURES, > then emerge akonadi with USE=semantic-desktop. > But isn't the point that we should be able to emerge the package with sanbox enabled, as opposed to having remove the feature just for that package? you missed the point. akonadi and/or nepomuk are broken. sandbox catching the error is sandbox doing the right thing. (In reply to comment #7) > you missed the point. akonadi and/or nepomuk are broken. sandbox catching the > error is sandbox doing the right thing. > I understood. That's why I filed a bug for akonadi to the KDE team, not for sandbox. I was just trying to provide as much information on the problem as possible. Please try to reproduce with 4.2.4 (In reply to comment #9) > Please try to reproduce with 4.2.4 > I did not have the problem with 4.2.4 closing since user reported it fixed with newer version |