New Buster issue: "Can't roll back Pillow; was not uninstalled" #259
Comments
|
Ok, just did a fresh install on a Pi4 myself. Building wheels for collected packages: Pillow The headers or library files could not be found for jpeg, Please see the install instructions at: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): The headers or library files could not be found for jpeg, Please see the install instructions at: Failed building wheel for Pillow Can't roll back Pillow; was not uninstalled |
|
Try this: apt-get install libjpeg-dev zlib1g-dev pip3 install Pillow Does this work? |
|
I had to add sudo for the first command.
|
|
Can we update the |
|
Does it work now? |
|
Yes. |
|
This seems more a Pillow problem. I'm using 9.0.1 and everything was fine. 1st of April 9.1.0 was released. Guess there is nothing we can do on our side. As a workaround one could run pip install Pillow==9.0.1 before installing picframe |
|
Or change the line in That was basically the error I got the other day (2nd of Apr!!) which I referred to as a complaint about a missing jpeg header for pillow As I said, I assumed it was because I had missed out or mistyped one of @thomasedoff console inputs. To patch over it I just used |
|
It would be nice to include it in the |
|
Hello, I am not a seasoned Python user, but I don't think that Pillow is broken, so there should be no need to "hardcode" the version. As I understand it, pip will check for- and download precompiled binaries from piwheels.org if available. Otherwise pip will compile the necessary binaries locally, which requires "some" (I don't know exactly which) additional header files. Without these headers, pip will throw errors. Currently, there is a notice over at piwheels.org stating that "piwheels does not currently support aarch64". So the headers are required for all Model 4 owners running a 64-bit OS. Assuming that sapho is running a 64-bit OS and has not installed the headers, this would explain the issue. @paddywwoof, the issue you got the other day - regardless of 64- or 32-bit - was most likely because of piwheels.org being offline for several hours that day. I made a small note of it here: As I see, you have the following options:
|
|
Looks like there is this python-pillow/Pillow#5797 (comment) issue with v9.1.0 so we might have to force setup to use v9.0.1 until we clear up both issues. |
|
Actually, looking closer at piwheels.org there does not seem to be a precompiled package of Pillow 9.1.0 for any platform. So if you're trying to install 9.1.0 at this point in time, you will need the headers, regardless of the architecture. |
|
@thomasedoff you are probably right about the piwheels being offline, and also about the aarch64 support, but I think I got the same multi-page error text about missing headers when I tried to setup bullseye with piOS32, which I did before testing the 64 bit, and I'm sure the headers didn't need to be installed previously. Of course they might have been a requirement of some other package that is no longer there in the latest piOS lite setup! EDIT - maybe we just need to give the wheel building robot a chance to catch up. I seem to remember it's running on several Raspberry Pi computers rather than attempting to cross compile, so probably takes quite a while to get through a back-log of compilation. But we need to see what the pillow devs say about the possible memory leak regression. |
|
Issue could be solved now. I just checked pinwheels.org and there are precompiled packages for Pillow 9.1.0 now available. @paddywwoof I installed |
|
Now that a precompiled Pillow 9.1.0 is available, my system (bullseye 32-bit) also appear to be free of immediate issues. pi@picframe:~ $ pip install Pillow --upgrade --no-cache-dir
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: Pillow in ./.local/lib/python3.9/site-packages (9.0.1)
Collecting Pillow
Downloading https://www.piwheels.org/simple/pillow/Pillow-9.1.0-cp39-cp39-linux_armv7l.whl (1.1 MB)
|████████████████████████████████| 1.1 MB 501 kB/s
Installing collected packages: Pillow
Attempting uninstall: Pillow
Found existing installation: Pillow 9.0.1
Uninstalling Pillow-9.0.1:
Successfully uninstalled Pillow-9.0.1
Successfully installed Pillow-9.1.0
pi@picframe:~ $ systemctl --user restart picframe
pi@picframe:~ $ systemctl --user status picframe
● picframe.service - PictureFrame
Loaded: loaded (/home/pi/.config/systemd/user/picframe.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-04-11 15:02:05 CEST; 10s ago
Main PID: 22184 (xinit)
Tasks: 5 (limit: 1170)
CPU: 7.145s
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/picframe.service
├─22184 xinit /usr/bin/python3 /home/pi/.local/bin/picframe /home/pi/picframe_data/config/configuration.yaml
├─22185 /usr/lib/xorg/Xorg :0
└─22192 /usr/bin/python3 /home/pi/.local/bin/picframe /home/pi/picframe_data/config/configuration.yaml
Apr 11 15:02:05 picframe xinit[22185]: to make sure that you have the latest version.
Apr 11 15:02:05 picframe xinit[22185]: Markers: (--) probed, (**) from config file, (==) default setting,
Apr 11 15:02:05 picframe xinit[22185]: (++) from command line, (!!) notice, (II) informational,
Apr 11 15:02:05 picframe xinit[22185]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Apr 11 15:02:05 picframe xinit[22185]: (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 11 15:02:05 2022
Apr 11 15:02:05 picframe xinit[22185]: (==) Using config directory: "/etc/X11/xorg.conf.d"
Apr 11 15:02:05 picframe xinit[22185]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Apr 11 15:02:06 picframe xinit[22185]: (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
Apr 11 15:02:12 picframe xinit[22192]: INFO:start.py:starting ['/home/pi/.local/bin/picframe', '/home/pi/picframe_data/config/configuration.yaml']
Apr 11 15:02:12 picframe xinit[22192]: INFO:model.Model:Open config file: /home/pi/picframe_data/config/configuration.yaml |
|
So we can close this issue now? |
|
Let me do a fresh install later today so that I can confirm that it works. |
|
Just did a fresh install. It works! Strange message but it works.
|
|
I close this, because this was a Pillow issue (already solved) |
I got two comments this last week that apparently there has been an OS Buster update on April 4 which messes up things:
This is with OS Buster, latest release on a Pi3. Did anything change with Pillow?
The text was updated successfully, but these errors were encountered: