You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the OEM Kernel alert dialog is implemented directly into the one-liner command:
Which is counter-intuitive, lacks transparency, and hard to troubleshoot problems like #24.
We also need to hack through the escaping requirements introduced by The Exec key | Desktop Entry Specification which increases the difficulty in maintaining a working solution for the users.
I suggest moving the logic into a separate shell script file and instructing the user to install it to a proper location and write the autostart configuration file to execute it instead.
I've read through and made a sample script(installed in ~/.local/bin/check-oem-kernel-update) as the following:
#!/usr/bin/env bash# Check whether an updated OEM kernel package is installed, and notify# the user to also update the default boot entry of the GRUB bootloaderset \
-o errexit \
-o nounset
latest_oem_kernel=$( ls /boot/vmlinuz-* \| grep '6.5.0-10..-oem' \| sort -V \| tail -n1 \| awk -F'/''{print $NF}' \| sed 's/vmlinuz-//')
current_grub_kernel=$( grep '^GRUB_DEFAULT=' /etc/default/grub \| sed \ -e 's/GRUB_DEFAULT=\"Advanced options for Ubuntu>Ubuntu, with Linux //g' \ -e 's/\"//g')iftest"${latest_oem_kernel}"!= "${current_grub_kernel}";then
zenity_opts=(
--text-info
# No longer works on Ubuntu >=23.10, see #25.#--html
--width=300
--height=200
--title="Kernel Update Notification"
)
zenity "${zenity_opts[@]}" \
--filename=<(echo -e \"A newer OEM D kernel is available than what is set in GRUB. Open the following URL in the web browser to learn more:"echoecho" https://github.com/FrameworkComputer/linux-docs/blob/main/22.04-OEM-D.md")fi
I've modified the autostart script as the following and can verify the alert dialog is properly triggered after login:
The text was updated successfully, but these errors were encountered:
brlin-tw
changed the title
Consider implement the OEM Kernel alert using separate script file
Consider implement the OEM Kernel alert using a separate script file
Mar 20, 2024
Currently, the OEM Kernel alert dialog is implemented directly into the one-liner command:
Which is counter-intuitive, lacks transparency, and hard to troubleshoot problems like #24.
We also need to hack through the escaping requirements introduced by The
Exec
key | Desktop Entry Specification which increases the difficulty in maintaining a working solution for the users.I suggest moving the logic into a separate shell script file and instructing the user to install it to a proper location and write the autostart configuration file to execute it instead.
I've read through and made a sample script(installed in ~/.local/bin/check-oem-kernel-update) as the following:
I've modified the autostart script as the following and can verify the alert dialog is properly triggered after login:
The text was updated successfully, but these errors were encountered: