Perl upgrade breaks gnome system tools
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-tools-backends |
Fix Released
|
Medium
|
|||
gnome-system-tools (Debian) |
Fix Released
|
Unknown
|
|||
system-tools-backends (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: gnome-system-tools
I built Perl 5.10 from source and installed it in /usr/local/
tim@mrbun:~$ /usr/bin/perl -v | grep "This is perl"
This is perl, v5.8.8 built for i486-linux-
tim@mrbun:~$ /usr/local/bin/perl -v | grep "This is perl"
This is perl, v5.10.0 built for i686-linux
This broke system tools such as System-
The configuration could not be loaded
You are not allowed to access the system configuration.
this message. I believe the culprit was actually
/usr/
which has a shebang line of
#!/usr/bin/env perl
and, of course, that's now finding the wrong version of Perl
tim@mrbun:~$ /usr/bin/env perl -v | grep "This is perl"
This is perl, v5.10.0 built for i686-linux
I think it's a mistake to use env this way in system scripts. Changing it to /usr/bin/perl fixed everything.
tim@mrbun:~$ head -1 /usr/share/
#!/usr/bin/perl
ProblemType: Bug
Architecture: i386
Date: Thu Mar 6 08:59:22 2008
DistroRelease: Ubuntu 7.10
NonfreeKernelMo
Package: gnome-system-tools 2.20.0-0ubuntu2
PackageArchitec
SourcePackage: gnome-system-tools
Uname: Linux mrbun 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux
Related branches
Changed in gnome-system-tools: | |
status: | Unknown → New |
Changed in system-tools-backends: | |
status: | Unknown → Confirmed |
Changed in gnome-system-tools: | |
status: | New → Confirmed |
Changed in gnome-system-tools: | |
status: | Confirmed → Fix Released |
Changed in system-tools-backends: | |
status: | Confirmed → Fix Released |
Changed in system-tools-backends: | |
importance: | Unknown → Medium |
Changed in system-tools-backends: | |
importance: | Medium → Unknown |
Changed in system-tools-backends: | |
importance: | Unknown → Medium |
Thank you for your bug report