Activity log for bug #390591

Date Who What changed Old value New value Message
2009-06-22 09:46:32 Dave Martin bug added bug
2009-06-22 09:47:05 Dave Martin bug added subscriber Loïc Minier
2009-06-22 14:04:12 Loïc Minier bug added subscriber Canonical Mobile Team
2009-06-22 14:05:53 Loïc Minier f-spot (Ubuntu): assignee Canonical Mobile Team (canonical-mobile)
2009-06-22 14:06:18 Pedro Villavicencio f-spot (Ubuntu): importance Undecided Medium
2009-06-22 14:06:18 Pedro Villavicencio f-spot (Ubuntu): assignee Canonical Mobile Team (canonical-mobile)
2009-06-22 14:07:25 Pedro Villavicencio f-spot (Ubuntu): assignee Canonical Mobile Team (canonical-mobile)
2009-06-22 15:23:34 Michael Casadevall f-spot (Ubuntu): status New Confirmed
2009-06-22 17:45:23 Michael Casadevall nominated for series Ubuntu Jaunty
2009-06-22 17:45:23 Michael Casadevall nominated for series Ubuntu Karmic
2009-06-22 18:35:47 Michael Casadevall summary f-spot seems wrongly packaged / unusable for armel mono segfaults on ARM
2009-06-22 18:36:25 Michael Casadevall affects f-spot (Ubuntu) mono (Ubuntu)
2009-06-22 18:40:23 Michael Casadevall description Binary package hint: f-spot Installing f-spot on armel installs a load of Win32 PE executables (.exe, .dll) and seems to rely on executing these to work. dpkg prints out a load of "illegal instruction" errors when trying to configure the package, but the package is erroneously marked as successfully configured after installation. It looks like f-spot and related packages (*mono* etc.) should not be packaged for armel at all, or ARM-targeted binaries need to be built (if this is supported by the source packages; apparently, mono can support ARM but I don't have much experience of these packages). The affected binary packages seem to be: f-spot libart2.24-cil libflickrnet2.1.5-cil libgconf2.24-cil libglade2.0-cil libglib2.0-cil libgnome2.24-cil libgnome-keyring1.0-cil libgnome-vfs2.24-cil libgtk2.0-cil libmono2.0-cil libmono-addins0.2-cil libmono-addins-gui0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil libmono-data2.0-cil libmono-data-tds2.0-cil libmono-getoptions2.0-cil libmono-i18n2.0-cil libmono-posix2.0-cil libmono-security2.0-cil libmono-sharpzip2.84-cil libmono-sqlite2.0-cil libmono-system2.0-cil libmono-system-data2.0-cil libmono-system-web2.0-cil libndesk-dbus1.0-cil libndesk-dbus-glib1.0-cil mono-2.0-gac Mono on ARM currently appears to be unusable. Installing any *-cli package causes a large number of segfaults, as well as running any installed mono application (such as f-spot). At the very least, installation of *-cli packages should not succeed if the installation of the assembly fails. Test Case: 1. Install f-spot on ARM (it is not a part of ubuntu-desktop on ARM) 2. Obverse of the series of segfaults installing the mono stack 3. Run f-spot Original Bug Report: Binary package hint: f-spot Installing f-spot on armel installs a load of Win32 PE executables (.exe, .dll) and seems to rely on executing these to work. dpkg prints out a load of "illegal instruction" errors when trying to configure the package, but the package is erroneously marked as successfully configured after installation. It looks like f-spot and related packages (*mono* etc.) should not be packaged for armel at all, or ARM-targeted binaries need to be built (if this is supported by the source packages; apparently, mono can support ARM but I don't have much experience of these packages). The affected binary packages seem to be: f-spot libart2.24-cil libflickrnet2.1.5-cil libgconf2.24-cil libglade2.0-cil libglib2.0-cil libgnome2.24-cil libgnome-keyring1.0-cil libgnome-vfs2.24-cil libgtk2.0-cil libmono2.0-cil libmono-addins0.2-cil libmono-addins-gui0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil libmono-data2.0-cil libmono-data-tds2.0-cil libmono-getoptions2.0-cil libmono-i18n2.0-cil libmono-posix2.0-cil libmono-security2.0-cil libmono-sharpzip2.84-cil libmono-sqlite2.0-cil libmono-system2.0-cil libmono-system-data2.0-cil libmono-system-web2.0-cil libndesk-dbus1.0-cil libndesk-dbus-glib1.0-cil mono-2.0-gac
2009-06-22 18:40:23 Michael Casadevall tags armel armel f-spot
2009-06-22 18:40:23 Michael Casadevall name arm-mono-segfaults
2009-06-22 22:37:19 Loïc Minier bug task added mono (Ubuntu Jaunty)
2009-06-22 22:37:28 Loïc Minier bug task added mono (Ubuntu Karmic)
2009-06-22 23:33:35 Michael Casadevall mono (Ubuntu Jaunty): importance Undecided Medium
2009-06-22 23:33:35 Michael Casadevall mono (Ubuntu Jaunty): status New Confirmed
2009-06-22 23:33:35 Michael Casadevall mono (Ubuntu Jaunty): milestone jaunty-updates
2009-06-22 23:33:35 Michael Casadevall mono (Ubuntu Jaunty): assignee Canonical Mobile Team (canonical-mobile)
2009-06-22 23:33:55 Michael Casadevall mono (Ubuntu Karmic): status Confirmed Fix Released
2009-06-23 13:19:42 Dave Martin attachment added Output from installing and running f-spot on armel, with CONFIG_OABI_COMPAT enabled http://launchpadlibrarian.net/28247634/f-spot-install-and-run_jaunty_armel.txt
2009-06-23 13:20:18 Dave Martin attachment added Debug output from f-spot, with backtrace http://launchpadlibrarian.net/28247662/f-spot-debug_jaunty_armel.txt
2009-06-23 13:29:00 Dave Martin description Mono on ARM currently appears to be unusable. Installing any *-cli package causes a large number of segfaults, as well as running any installed mono application (such as f-spot). At the very least, installation of *-cli packages should not succeed if the installation of the assembly fails. Test Case: 1. Install f-spot on ARM (it is not a part of ubuntu-desktop on ARM) 2. Obverse of the series of segfaults installing the mono stack 3. Run f-spot Original Bug Report: Binary package hint: f-spot Installing f-spot on armel installs a load of Win32 PE executables (.exe, .dll) and seems to rely on executing these to work. dpkg prints out a load of "illegal instruction" errors when trying to configure the package, but the package is erroneously marked as successfully configured after installation. It looks like f-spot and related packages (*mono* etc.) should not be packaged for armel at all, or ARM-targeted binaries need to be built (if this is supported by the source packages; apparently, mono can support ARM but I don't have much experience of these packages). The affected binary packages seem to be: f-spot libart2.24-cil libflickrnet2.1.5-cil libgconf2.24-cil libglade2.0-cil libglib2.0-cil libgnome2.24-cil libgnome-keyring1.0-cil libgnome-vfs2.24-cil libgtk2.0-cil libmono2.0-cil libmono-addins0.2-cil libmono-addins-gui0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil libmono-data2.0-cil libmono-data-tds2.0-cil libmono-getoptions2.0-cil libmono-i18n2.0-cil libmono-posix2.0-cil libmono-security2.0-cil libmono-sharpzip2.84-cil libmono-sqlite2.0-cil libmono-system2.0-cil libmono-system-data2.0-cil libmono-system-web2.0-cil libndesk-dbus1.0-cil libndesk-dbus-glib1.0-cil mono-2.0-gac Mono on ARM currently appears to be unusable. Installing any *-cli package causes a large number of segfaults, as well as running any installed mono application (such as f-spot). At the very least, installation of *-cli packages should not succeed if the installation of the assembly fails. Test Case: 1. Install f-spot on ARM (it is not a part of ubuntu-desktop on ARM) 2. Obverse of the series of segfaults installing the mono stack 3. Run f-spot Original Bug Report: Binary package hint: f-spot [ dave-martin-arm removed his original incorrect description text; see the original description for details. ]
2009-06-24 07:58:05 Dave Martin attachment added SVC instructions from /usr/bin/mono (mono-jit 2.0.1-4) http://launchpadlibrarian.net/28274312/mono_2.0.1-4_svcs.txt
2010-10-18 18:08:53 riki removed subscriber riki
2010-11-17 16:20:29 Curtis Hovey removed subscriber Registry Administrators
2010-12-05 04:17:12 Curtis Hovey mono (Ubuntu): assignee Registry Administrators (registry)
2010-12-05 04:17:17 Curtis Hovey mono (Ubuntu Jaunty): assignee Registry Administrators (registry)
2010-12-05 04:17:20 Curtis Hovey mono (Ubuntu Karmic): assignee Registry Administrators (registry)
2012-03-13 05:29:40 JC Hulce mono (Ubuntu Jaunty): status Confirmed Invalid