[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#985562: marked as done (libclutter-imcontext-0.1-bin: post-installation script subprocess - error exit status 1)

Your message dated Thu, 24 Jul 2025 02:25:04 +0200
with message-id <aIF9YHGBoS7Rfxmg@per.namespace.at>
and subject line Re: Bug#985562: libclutter-imcontext-0.1-bin: post-installation script subprocess - error exit status 1
has caused the Debian Bug report #985562,
regarding libclutter-imcontext-0.1-bin: post-installation script subprocess - error exit status 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
985562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985562
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: upgrade-reports
Severity: normal
Tags: d-i

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

My previous release is: buster
I am upgrading to: bullseye
Archive date: not applicable
Upgrade date: 2021-03-19  13:11:52 (GMT+1)
uname -a before upgrade: <The result of running uname -a on a shell prompt>
uname -a after upgrade: <The result of running uname -a on a shell prompt>
Method: 1. clear all lines in sources.list and use only: "deb
http://deb.debian.org/debian/ bullseye contrib non-free main"
        3. sudo apt update
        4. sudo apt upgrade

Contents of /etc/apt/sources.list:
the following line only:
deb http://deb.debian.org/debian/ bullseye contrib non-free main

- Were there any non-Debian packages installed before the upgrade?  If
  so, what were they?
        non free firmwares 20190114-2 (required by installer: firmware intel-
wimax/stable,  iwlwifi/stable)
        virtualbox 6.1 (Oracle, non-free, but from Debian buster repo)

- Was the system pre-update a pure sarge system? If not, which packages
  were not from sarge?
        Cannot answer to the question as I don't know what a "pure sarge"
system is.

- Did any packages fail to upgrade?
        Yes but not completely - Configuration time errors during like:
FYI: "Paramétrage" ~= "Setting up"

Paramétrage de libclutter-imcontext-0.1-bin (0.1.4-3.1) ...
Cannot load module /usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-
ibus.so: GModule (/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-
ibus.so) initialization check failed: GLib version too old (micro mismatch)
/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-ibus.so does not
export Clutter IM module API: GModule (/usr/lib/x86_64-linux-gnu/clutter-
imcontext/immodules/im-ibus.so) initialization check failed: GLib version too
old (micro mismatch)
dpkg: erreur de traitement du paquet libclutter-imcontext-0.1-bin
(--configure) :
 installed libclutter-imcontext-0.1-bin package post-installation script
subprocess returned error exit status 1

        apt upgrade last lines:
FYI:    "Des erreurs ont été rencontrées pendant l'exécution"  ~= "errors
encountered during execution"

        Des erreurs ont été rencontrées pendant l'exécution :
        libclutter-imcontext-0.1-bin
        ibus-clutter:amd64
        Log ended: 2021-03-19  13:39:05


- Were there any problems with the system after upgrading?

        In an attempt to finalize upgrade, I ran "sudo apt dist-upgrade" right
after the end of "sudo apt update" execution.
        At +/- 30% of "dist-upgrade" execution, display went "off", then "on"
(like in a power-off power-on cycle, there was no backlight and display was not
"greyish") showing a dash on top replaced by an arrow in the center of the
screen. Arrow and dash were alternatively blinking at a cycle of approx 3/sec
(if unclear, I've got a 10 sec video clip of the incident). As there was still
disk activity, I decided to wait for the disk to become quiet, not interrupting
a possible still working execution. After 10 min (or so, as 10 min ss the
session auto-lock inactivity delay, read further) the display went back to
life. Lightdm greeter lock screen was on, asking for password. I could log back
on flawlessly and installation process was at 82% this time. Installation went
fine, no errors. I rebooted the system and got a bullseye working without
critical error.

Further Comments/Problems:


Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
depending on your shell) from before and after the upgrade so that we
know what packages were installed on your system.

Attachment: requested-dpkg-l.tar.gz
Description: application/gzip

Attachment: bugreport-additional-info.tar.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- 
On Thu, Mar 25, 2021 at 10:39:47PM +0100, Paul Gevers wrote:
> Control: clone -1 -2
> Control: reassign -2 libclutter-imcontext-0.1-bin 0.1.4-3.1
> Control: severity -2 serious
> 
> Dear libclutter-imcontext-0.1-bin maintainer,
[..]
> > Paramétrage de libclutter-imcontext-0.1-bin (0.1.4-3.1) ...
> > Cannot load module /usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-
> > ibus.so: GModule (/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-
> > ibus.so) initialization check failed: GLib version too old (micro mismatch)
> > /usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/im-ibus.so does not
> > export Clutter IM module API: GModule (/usr/lib/x86_64-linux-gnu/clutter-
> > imcontext/immodules/im-ibus.so) initialization check failed: GLib version too
> > old (micro mismatch)
> > dpkg: erreur de traitement du paquet libclutter-imcontext-0.1-bin
> > (--configure) :
> >  installed libclutter-imcontext-0.1-bin package post-installation script
> > subprocess returned error exit status 1

Apparently this was fixed in ibus-client-clutter (0.0+git20090728.a936bacf-7).

Closing.

--- End Message ---
Reply to: