On kubuntu 24.04, after_bootloader_context claims to fail to remove installaton icon

Bug #2061681 reported by Eugene San
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calamares-settings-ubuntu (Ubuntu)
Fix Released
Low
ԜаӀtеr Ⅼарсһуnѕkі

Bug Description

On Kubuntu 24.04 daily (up to 24.04.2) kubuntu/modules/after_bootloader_context.conf claims to fail to remove installation .desktop file:

2024-04-11 - 23:38:46 [6]: Starting job "Performing contextual processes' job…" ( 32 / 41 )
2024-04-11 - 23:38:46 [6]: .. Running ("/bin/sh", "-c", "rm //home/user/Desktop/kubuntu-calamares.desktop")
2024-04-11 - 23:38:46 [6]: .. Target cmd: ("/bin/sh", "-c", "rm //home/user/Desktop/kubuntu-calamares.desktop") Exit code: 1 output:
rm: cannot remove '//home/user/Desktop/kubuntu-calamares.desktop': No such file or directory
2024-04-11 - 23:38:46 [6]: Calamares::JobResult Calamares::CommandList::run()
2024-04-11 - 23:38:46 [6]: Error code 1 ignored by CommandList configuration.

It seems to try to remove it from live system instead of chroot.
But, since I don't see the icon on the target system I believe this module is redundant and can be removed.

Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

Confirmed, both for Kubuntu and Lubuntu.

For context, this does NOT cause the install to fail.

The desktop file in question exists in three places:
 1. On the Desktop of the live user
 2. In /usr/share/applications of the live system
 3. In /usr/share/applications of the squashfs
Can't find it at all in the installed system.

That said, it looks like removing this module will have no negative effect.

As an aside, it does seem to be doing this to the chroot (the user is `user` not `kubuntu` as it is with the live system), but even were the file to exist, I think it would fail anyways. Note that the path starts with "//home." The way the configuration file is written, it's supposed to be `${ROOT}/home` but inevitably that variable is expanded to "/" so we get "//home" and not "/home" as expected. The proper way to do this would be with `${ROOT}home`.

Changed in calamares-settings-ubuntu (Ubuntu):
status: New → Incomplete
status: Incomplete → Confirmed
Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

…furthermore I got out an old 20.04 Lubuntu and found it has the same situation: there's no desktop file on the Desktop of the installer user to remove and removing the module has no negative effect on the installed system.

Changed in calamares-settings-ubuntu (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
assignee: nobody → Lubuntu Developers (lubuntu-dev)
milestone: none → ubuntu-24.04
Changed in calamares-settings-ubuntu (Ubuntu):
assignee: Lubuntu Developers (lubuntu-dev) → ԜаӀtеr Ⅼарсһуnѕkі (wxl)
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.29

---------------
calamares-settings-ubuntu (1:24.04.29) noble; urgency=medium

  [ Aaron Rainbolt ]
  * Change Kubuntu's Calamares sidebar color.

  [ Walter Lapchynski ]
  * Remove after_bootloader contextual process. (LP: #2061681)

 -- Walter Lapchynski <email address hidden> Tue, 16 Apr 2024 01:10:47 +0000

Changed in calamares-settings-ubuntu (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.