I'm using Kubuntu 7.10 (just intalled) and i have the same bug
--
[apport] restricted-manager crashed with IOError in generate_restricted_list()
https://bugs.launchpad.net/bugs/103625
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
The bug has returned.
** Changed in: restricted-manager (Ubuntu)
Status: Fix Released = Confirmed
--
[apport] restricted-manager crashed with IOError in generate_restricted_list()
https://bugs.launchpad.net/bugs/103625
You received this bug notification because you are a member of Ubuntu
Can someone confirm this bug with the latest Ubuntu Gutsy kernel? You
can do this by updating your system and then trying Restricted Manager
again. Thank you.
** Changed in: restricted-manager (Ubuntu)
Status: Confirmed = Incomplete
--
[apport] restricted-manager crashed with IOError in
It appears to have stopped happening to me since the last update.
--
[apport] restricted-manager crashed with IOError in generate_restricted_list()
https://bugs.launchpad.net/bugs/103625
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Because of the two people reporting that the bug stopped appearing, I am
closing it. Feel free to reopen it if restricted-manager crashes for you
this way.
** Changed in: restricted-manager (Ubuntu)
Status: Incomplete = Fix Released
--
[apport] restricted-manager crashed with IOError in
This bug is still happening on my gutsy tribe3 installation.
--
[apport] restricted-manager crashed with IOError in generate_restricted_list()
https://bugs.launchpad.net/bugs/103625
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Please, ignore my previous comment. It occurred while running a badly
configured 2.6.20 kernel. It does not happen with the fresh installed
2.6.22 kernel downloaded today.
--
[apport] restricted-manager crashed with IOError in generate_restricted_list()
https://bugs.launchpad.net/bugs/103625
You
This is indeed a new bug, haven't seen this type of crash before. Weird
that modules.dep does not exist, it should be generated at the time when
l-r-m is installed/upgraded.
** Changed in: restricted-manager (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Confirmed
--
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7177815/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/7177816/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://librarian.launchpad.net/7177817/ProcStatus.txt
** Attachment
