New aksusbd i386 package pre installation script subprocess returned error exit status 8 - Исправление ошибок и поиск оптимальных решений проблем

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

drqxr

[SOLVED] nvidia errors during driver update

Hi,

For some time now I have issues with nvidia-driver-390, tried reverting to nvidia-340, or switching to open-source ones but in each case getting errors.
Currently logging in to rendering in software mode.

Suggested on similar topic — Safe Boot is disabled on my PC.

Error examples below, for full list please see the attached text file:
dpkg-divert: error: mismatch on package
when removing ‘diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390’
found ‘diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340’
dpkg: error processing archive /tmp/apt-dpkg-install-JMcCgJ/43-libnvidia-gl-390_390.77-0ubuntu0.18.04.1_i386.deb (—unpack):
new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2

dpkg: dependency problems prevent configuration of nvidia-driver-390:
nvidia-driver-390 depends on libnvidia-gl-390 (= 390.77-0ubuntu0.18.04.1); however:
Package libnvidia-gl-390:amd64 is not installed.

dpkg: error processing package nvidia-driver-390 (—configure):
dependency problems — leaving unconfigured

Any suggestions greatly appreciated.

Attachments

nVidia issues.odt: (16.99 KiB) Downloaded 681 times

Last edited by drqxr on Tue Nov 20, 2018 1:03 pm, edited 1 time in total.

trytip: Level 14; Posts: 5311; Joined: Tue Jul 05, 2016 1:20 pm

Re: nvidia errors during driver update

Post

by trytip » Tue Nov 20, 2018 12:46 pm

delete everything and start again,
apt purge nvidia-*
then run dkms status to see what you have reboot and install one driver from the driver manager

drqxr

Re: nvidia errors during driver update

Post

by drqxr » Tue Nov 20, 2018 12:59 pm

Thanks for the suggestion.
Did it:

Code: Select all

sudo apt purge *nvidia*
sudo apt autoremove

Then got this error:

Code: Select all

The following packages have unmet dependencies.
 libnvidia-ifr1-390 : Depends: libnvidia-gl-390 but it is not going to be installed
 libnvidia-ifr1-390:i386 : Depends: libnvidia-gl-390:i386 but it is not going to be installed
 nvidia-driver-390 : Depends: libnvidia-gl-390 (= 390.77-0ubuntu0.18.04.1) but it is not going to be installed
                     Recommends: libnvidia-gl-390:i386 (= 390.77-0ubuntu0.18.04.1)
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

Tried but failed to:

Then I found similar issue on Ubuntu forums, so I tried that solution:

Code: Select all

sudo su 
for FILE in $(dpkg-divert --list | grep nvidia-340 | awk '{print $3}'); do dpkg-divert --remove $FILE; done
exit

After that I was able to:

Code: Select all

sudo apt-get install -f
sudo apt-get update
sudo apt-get upgrade

Then rebooted my system and no errors also no «Rendering in software mode» message, so I am assuming it is fixed.

drqxr

Re: [SOLVED] nvidia errors during driver update

Post

by drqxr » Wed Nov 21, 2018 6:03 am

trytip wrote: ↑

Tue Nov 20, 2018 7:13 pm

what does dkms status say now? does your nvidia-settings work? or are you on nouveau now?

Thanks for checking trytip, yes my nvidia settings are working fine, and this is the dkms status:

Code: Select all

nvidia, 390.77, 4.15.0-39-generic, x86_64: installed

coolau

Re: [SOLVED] nvidia errors during driver update

Post

by coolau » Sat Aug 03, 2019 12:35 am

sudo apt purge nvidia-*
sudo apt autoremove

installing of nvidia-driver-430 SOLVED by above command.

removed error below (believe the problem is nvidia-driver-390 still existed)
he following packages have unmet dependencies:
nvidia-driver-430 : Depends: libnvidia-gl-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Depends: nvidia-dkms-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Depends: nvidia-kernel-source-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Depends: libnvidia-compute-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Depends: nvidia-compute-utils-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Depends: libnvidia-decode-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Depends: libnvidia-encode-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Depends: nvidia-utils-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Depends: libnvidia-ifr1-430 (= 430.40-0ubuntu0~gpu18.04.1) but it is not going to be installed
Recommends: libnvidia-compute-430:i386 (= 430.40-0ubuntu0~gpu18.04.1)
Recommends: libnvidia-decode-430:i386 (= 430.40-0ubuntu0~gpu18.04.1)
Recommends: libnvidia-encode-430:i386 (= 430.40-0ubuntu0~gpu18.04.1)
E: Unable to correct problems, you have held broken packages.

Zik_t: Level 1; Posts: 1; Joined: Tue Feb 25, 2020 4:01 am

Re: [SOLVED] nvidia errors during driver update

Post

by Zik_t » Tue Feb 25, 2020 4:07 am

I have the same issue on ubuntu. Tried following your answer above and here are the errors I got:
sudo apt purge *nvidia*…
The following packages have unmet dependencies.
libnvidia-ifr1-440:i386 : Depends: libnvidia-gl-440:i386 but it is not going to be installed
E: Unmet dependencies. Try ‘apt —fix-broken install’ with no packages (or specify a solution).

$ sudo apt autoremove
Reading package lists… Done
Building dependency tree
Reading state information… Done
You might want to run ‘apt —fix-broken install’ to correct these.
The following packages have unmet dependencies.
libnvidia-ifr1-440 : Depends: libnvidia-gl-440 but it is not installed
libnvidia-ifr1-440:i386 : Depends: libnvidia-gl-440:i386 but it is not installed
nvidia-driver-440 : Depends: libnvidia-gl-440 (= 440.59-0ubuntu0.18.04.1) but it is not installed
Recommends: libnvidia-gl-440:i386 (= 440.59-0ubuntu0.18.04.1)
E: Unmet dependencies. Try ‘apt —fix-broken install’ with no packages (or specify a solution).

How do I go about fixing this?

SuperMan1981: Level 1; Posts: 1; Joined: Thu May 21, 2020 10:26 am

Re: [SOLVED] nvidia errors during driver update

Post

by SuperMan1981 » Thu May 21, 2020 10:51 am

This is in response to Zik_t about the Nvidia-440 dependency error:

I had the Exact Same problem so i tried the code above but changed the grep nvidia-340 to grep nvidia-440 and it worked.

Copy and Paste each code line one by one into Terminal:
sudo su
(enter root password)
for FILE in $(dpkg-divert —list | grep nvidia-440 | awk ‘{print $3}’); do dpkg-divert —remove $FILE; done
(when code is finished working type: exit)

After that the system can be updated using:
sudo apt-get install -f
sudo apt-get update
sudo apt-get upgrade

Then finally the system can be cleaned using:
sudo apt-get autoclean
sudo apt-get clean
sudo apt-get autoremove

Using an Nvidia GeForce GT 730 graphics card in a Dell R410 server. After the correction the system runs better and Compiz Desktop Cube rotates better without any flicker.

trytip: Level 14; Posts: 5311; Joined: Tue Jul 05, 2016 1:20 pm

Re: [SOLVED] nvidia errors during driver update

Post

by trytip » Fri May 22, 2020 9:10 am

if you have issues with nvidia this is an old thread and solved. you need to open your own thread and post the proper information of your system and problem you need help with. and if you use this thread then by all means read all the posts and codes.

Источник

Неудовлетворённые зависимости

Устанавливал пакет nvidia-390 на Ubuntu (которая нормально, без лагов установилась при использовании телевизора, как монитора), установка прошла нормально. После перезагрузки решил установить другое приложение через терминал. Но тут получил такое:

$ sudo apt-get install guvcview Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово Возможно, для исправления этих ошибок вы захотите воспользоваться «apt-get -f install». Пакеты, имеющие неудовлетворённые зависимости: guvcview : Зависит: libguvcview-2.0-2 но он не будет установлен Рекомендует: uvcdynctrl но он не будет установлен libnvidia-ifr1-390 : Зависит: libnvidia-gl-390 но он не будет установлен libnvidia-ifr1-390:i386 : Зависит: libnvidia-gl-390:i386 но он не будет установлен nvidia-driver-390 : Зависит: libnvidia-gl-390 (= 390.87-0ubuntu0

gpu18.04.1) но он не будет установлен Рекомендует: libnvidia-gl-390:i386 (= 390.87-0ubuntu0

gpu18.04.1) E: Неудовлетворённые зависимости. Попытайтесь выполнить «apt —fix-broken install», не указывая имени пакета, (или найдите другое решение).

Ну пробовал прописывать «apt —fix-broken install» и «apt-get -f install» (через sudo конечно же), получал такое:

$ sudo apt-get -f install Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово Исправление зависимостей… Готово Следующие пакеты устанавливались автоматически и больше не требуются: lib32gcc1 libc6-i386 Для их удаления используйте «sudo apt autoremove». Будут установлены следующие дополнительные пакеты: libnvidia-gl-390 libnvidia-gl-390:i386 НОВЫЕ пакеты, которые будут установлены: libnvidia-gl-390 libnvidia-gl-390:i386 Обновлено 0 пакетов, установлено 2 новых пакетов, для удаления отмечено 0 пакетов, и 102 пакетов не обновлено. Установлено или удалено не до конца 3 пакетов. Необходимо скачать 0 B/29,1 MB архивов. После данной операции, объём занятого дискового пространства возрастёт на 147 MB. Хотите продолжить? [Д/н] y (Чтение базы данных … на данный момент установлено 134069 файлов и каталогов.) Подготовка к распаковке …/libnvidia-gl-390_390.87-0ubuntu0

gpu18.04.1_i386.deb … отклонение /usr/lib/i386-linux-gnu/libGL.so.1 в /usr/lib/i386-linux-gnu/libGL.so.1.distrib из-за nvidia-340 dpkg-divert: ошибка: несовпадение с пакетом при удалении «отклонение /usr/lib/i386-linux-gnu/libGL.so.1 из-за libnvidia-gl-390» найдено «отклонение /usr/lib/i386-linux-gnu/libGL.so.1 в /usr/lib/i386-linux-gnu/libGL.so.1.distrib из-за nvidia-340» dpkg: ошибка при обработке архива /var/cache/apt/archives/libnvidia-gl-390_390.87-0ubuntu0

gpu18.04.1_i386.deb (—unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Подготовка к распаковке …/libnvidia-gl-390_390.87-0ubuntu0

gpu18.04.1_amd64.deb … отклонение /usr/lib/x86_64-linux-gnu/libGL.so.1 в /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib из-за nvidia-340 dpkg-divert: ошибка: несовпадение с пакетом при удалении «отклонение /usr/lib/x86_64-linux-gnu/libGL.so.1 из-за libnvidia-gl-390» найдено «отклонение /usr/lib/x86_64-linux-gnu/libGL.so.1 в /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib из-за nvidia-340» dpkg: ошибка при обработке архива /var/cache/apt/archives/libnvidia-gl-390_390.87-0ubuntu0

gpu18.04.1_amd64.deb (—unpack): new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 При обработке следующих пакетов произошли ошибки: /var/cache/apt/archives/libnvidia-gl-390_390.87-0ubuntu0

gpu18.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

Ну и как удовлетворить зависимости? (как убрать большой текст в спойлер? cut не помогает)

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] Issue when installing nvidia-driver

Post by DaddyWesker » Tue Jun 29, 2021 7:55 am

I’m using Linux Mint 20.1. I’ve updated kernel to 5.11.0-22-generic today as suggested here https://forums.developer.nvidia.com/t/u . /167681/29 for making it happen to use my laptop with Ryzen 5800H and rtx 3070 normally since i’ve got black screen today at the morning after nvidia driver was updated using «apt upgrade» command (yes, i know, i shouldn’t have) and wasn’t able to beat it just by purging nvidia driver and reinstalling it through Driver manager (purging let me enter linux mint normally, but i need nvidia drivers for my work, and after installing it from driver manager i’ve got black screen again and again with nvidia-460 and nvidia-465). So, i’ve tried to update kernel and now i’m trying to install nvidia drivers. Unfortunately, i can’t do it since i’m receiving following through driver manager
«pk-client-error-quark: Error while installing package: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 (313)»

When i’m trying to install it using «sudo apt install nvidia-driver-460» i’m receiving following error:

Re: Issue when installing nvidia-driver

Post by DaddyWesker » Tue Jun 29, 2021 10:16 am

Well, fixed that by:
sudo apt install —reinstall linux-headers-$(uname -r)
sudo apt install —reinstall build-essential
sudo apt install —reinstall dkms
sudo apt install —reinstall linux-generic

then reboot. Then
sudo apt install nvidia-dkms-460
then
sudo apt install nvidia-driver-460
Then reboot.

Unfortunately, i’ve met black screen again. It seems, kernel update doesn’t helped here. Though, i’ve switched to discrete graphics only in bios and now i can finally login to the laptop (though it hadn’t worked at all previously before kernel update). Well, i wish i know how to fix that too, so i can use nvidia card only for computing and amd integrated card for screen. But, at least i can work again.

Re: Issue when installing nvidia-driver

Post by SMG » Tue Jun 29, 2021 1:55 pm

How did you «purge» the nvidia driver?

You have not yet provided the output of inxi -Fxxxrz as requested in Section 5 of READ: How To Get Help!, so we do not know the specifics of your laptop’s hardware or how Mint sees it. It makes it harder for anyone to be able to help without that information.

Re: Issue when installing nvidia-driver

Post by DaddyWesker » Fri Jul 02, 2021 7:02 am

. Currently, i’m using «only discrete» in BIOS so it could be the reason inxi doesn’t see nothing else than nvidia’s rtx card.

Unfortunately, i don’t remember was this switch was «switchable» or «only discrete» when i was installing linux mint since it was some time ago. Is it possible to check somehow?

Re: Issue when installing nvidia-driver

Post by SMG » Fri Jul 02, 2021 12:42 pm

That is how to purge them on a desktop system. When doing that on a laptop, that also removes the nvidia-prime and nvidia-prime-applet Mint files which are used for switchable graphics.

The switchable files were originally set up for systems with Intel-Nvidia combinations. There have been recent updates so the status of AMD-Nvidia combinations are registered in the applet. You can reinstall the applet with sudo apt-get install nvidia-prime-applet .

I helped someone two months ago in this thread [SOLVED] Random black screen on boot (nvidia) with what appears to be the same laptop as you have. At that time, the 5.11 kernel was not available in Update Manager. However, I do not know if one still needs to manually add the green sardine firmware in addition to the 5.11 kernel. Since you are still having issues, my guess would be that you do. (That person used the 5.10-oem kernel because that was the newest Ubuntu kernel in the Mint repositories at the time of that thread.)

Here is a post for adding green sardine firmware (which is the same one referenced in the [SOLVED] thread in the prior paragraph).

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] Generic package post-installation script subprocess returned error exit status 1

Post by hedgehoggy » Tue Oct 19, 2021 11:34 am

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by sleeper12 » Tue Oct 19, 2021 12:07 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by hedgehoggy » Tue Oct 19, 2021 12:16 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by sleeper12 » Tue Oct 19, 2021 12:22 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by hedgehoggy » Tue Oct 19, 2021 12:24 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by sleeper12 » Tue Oct 19, 2021 12:31 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by hedgehoggy » Tue Oct 19, 2021 12:33 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by rene » Tue Oct 19, 2021 12:47 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by hedgehoggy » Tue Oct 19, 2021 12:49 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by sleeper12 » Tue Oct 19, 2021 12:56 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by rene » Tue Oct 19, 2021 1:00 pm

Well, no, that would not be better. And, arr, crap, yes, it would have that issue; that reinstall triggers the very same postinst. And as far as I can quickly find you can’t in fact skip that postinst either. Typically apt.

It was in any case not likely and especially given your equal CRC32. Err, arr, let me think.

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by hedgehoggy » Tue Oct 19, 2021 1:00 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by hedgehoggy » Tue Oct 19, 2021 1:01 pm

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by rene » Tue Oct 19, 2021 1:11 pm

Plymouth is the splash screen, and it fails to install onto the initramfs. But what type exactly.

It’s going to be the set -e in /usr/share/initramfs-tools/hooks/plymouth that has the script exit after «something else» bugs out but unfortunately we don’t get t see what said something else in fact is, making this hard to pin down non-locally.

Are you at all script-savvy? If I’d have had this issue I’d start instrumenting /usr/share/initramfs-tools/hooks/plymouth by e.g. putting «echo 1» (and 2,3,4, . so on) statements before every if, for and case statement to see where it fails.

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Post by hedgehoggy » Tue Oct 19, 2021 1:18 pm

Источник

Неудовлетворённые зависимости

gpu18.04.1) но он не будет установлен Рекомендует: libnvidia-gl-390:i386 (= 390.87-0ubuntu0

Ну пробовал прописывать «apt —fix-broken install» и «apt-get -f install» (через sudo конечно же), получал такое:

gpu18.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

Ну и как удовлетворить зависимости? (как убрать большой текст в спойлер? cut не помогает)

Источник

Печать

Страницы: [1] Вниз

Тема: Ошибки с пакетами установки. Неудовлетворённые зависимости. (Прочитано 1408 раз)

0 Пользователей и 1 Гость просматривают эту тему.

de-nos

Пытался установить драйвер на видеокарту GTX550Ti. При манипуляциях в какой-то момент при перезагрузке компа ни одна видюха не захотела работать с монитором, пришлось комп выключить вслепую кнопкой питания. Отключил внешнюю видеокарту, сейчас на встроенной. После этого повылезали ошибки с пакетами.

sudo apt-get -f install

sudo apt-get update
sudo apt-get upgrade

sudo apt —fix-broken install

sudo dpkg —configure -a

Наверняка я не первый с такими ошибками, подскажите в каком направлении двигаться.

ТС не появлялся на Форуме более трех месяцев по состоянию на 13/02/2020 (последняя явка: 30/09/2019). Модератором раздела принято решение закрыть тему.
—zg_nico

« Последнее редактирование: 13 Февраля 2020, 00:10:03 от zg_nico »

andytux

Наверняка я не первый с такими ошибками

Ты примерно стопицотый.

в каком направлении двигаться.

1. Вариант самый бытрый и надежнвй. Восстановить иэ бэкапа.
2. Немного медленней. Переустановить систему.
3. Все остальные варианты намного сложней, медленней и не гарантирую восстановления даже при наличии опыта.

de-nos

1. Вариант самый бытрый и надежнвй. Восстановить иэ бэкапа

Эмм… Где этот бэкап взять?

2. Немного медленней. Переустановить систему.

Это моя основная система, много всего установлено и настроено, я бы не сказал, что немного медленней.

Morisson

Удали nvidia- драйвер, удали, если генерировал конфиг

sudo rm /etc/X11/xorg.conf

« Последнее редактирование: 22 Февраля 2019, 09:07:23 от Morisson »

Morisson

DimanBG

de-nos, прежде чем устанавливать другую версию драйвера, нужно удалить предыдущую.
Удаляй 340-ю, потом устанавливай 390-ю.

de-nos

Удали nvidia- драйвер, удали, если генерировал конфиг
sudo rm /etc/X11/xorg.conf

Как сам драйвер удалить?

Пользователь добавил сообщение 22 Февраля 2019, 17:31:36:

de-nos, прежде чем устанавливать другую версию драйвера, нужно удалить предыдущую.
Удаляй 340-ю, потом устанавливай 390-ю.

Как именно 340-й найти.
quote author=Morisson link=topic=303335.msg2375873#msg2375873 date=1550815553]
Откуда драйвер ставил?
[/quote]
Через настройки «обновление приложений» во вкладке «дополнительные драйверы». Выбрал из предложенных.

« Последнее редактирование: 22 Февраля 2019, 17:31:36 от de-nos »

Morisson

sudo apt purge nvidia*Только смотрите, что удаляться будет.

de-nos

sudo apt purge nvidia*

Один фиг…

Morisson

с сайта драйвер устанавливать пробовали?

de-nos

с сайта драйвер устанавливать пробовали?

Пробовал. Первое с чего начал. Но тот поругался на уже установленный. Потом в обновлениях приложений выбрал проприетарный 340-й, но с ним у меня кое-что из графики не пошло. Выбрал свободный 390-й заработало. Решил тесты погонять, а для проверки переключил моник на встроенную, и у меня при загрузки ОС не показывал монитор, комп выключил вслепую. И тут понеслась вся эта хрень с зависимостями и поврежденными пакетами.

alang

Решил тесты погонять, а для проверки переключил моник на встроенную, и у меня при загрузки ОС не показывал монитор, комп выключил вслепую. И тут понеслась вся эта хрень с зависимостями и поврежденными пакетами.

Ты забыл кое-что рассказать. А именно: что делал между выключением компа вслепую и тем, как «понеслась вся эта хрень». А ты что-то делал. Само ничего не ломается. Изображение должно было появиться сразу, как только ты бы переключил монитор снова на nvidia.

de-nos

Решил тесты погонять, а для проверки переключил моник на встроенную, и у меня при загрузки ОС не показывал монитор, комп выключил вслепую. И тут понеслась вся эта хрень с зависимостями и поврежденными пакетами.

Ты забыл кое-что рассказать. А именно: что делал между выключением компа вслепую и тем, как «понеслась вся эта хрень». А ты что-то делал. Само ничего не ломается. Изображение должно было появиться сразу, как только ты бы переключил монитор снова на nvidia.

Последовательность: поставил драйвер 390-й (на GTX550Ti), прогнал несколько простых графических тестов. Переткнул моник. Не смог нормально загрузиться. Вытащил из мамки GTX (на всякий случай). Загрузился. Запустил снова тесты, один из них написал — ** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control! ** Failed to set swap interval. Results may be bounded above by refresh rate. Поставил обратно GTX, моник в неё воткнул. При загрузке (GRUB и логотип «ubuntu») разрешение экрана стало значительно меньше (640х480 наверное). Попытался запустить тест, но сообщение было похожим (или то же самое). В «Обновлении приложений» попытался сменить драйвер, но оно что-то там делало, но ничего не менялось. Далее это же «обновление приложений» само предложило обновить «NVIDIA OpenGL/GLX/EGL/GLES libraries and the Vulkan ICD.» но не смогло. А далее инет, форумы и безобидные попытки типа apt autoremove, apt clean, apt install -f, dpkg —configure -a, apt —fix-broken install, udate-upgrade. В принципе всё.

Пользователь добавил сообщение 23 Февраля 2019, 12:49:01:

Из файла

/var/lib/dpkg/statusпоудалял все блоки, начинающиеся со строк «Package: …. nvidia ….». Их вышло около 20-ти.

Потом выполнил снова

sudo apt-get install -f sudo apt update sudo apt upgrade Без ошибок.

Появилась возможность обновляться и пропал «кирпич в трее» (ошибка обновления), который всё это время висел там.
Поставил в комп видеокарту, тест показывает скорость на уровне плинтуса. Сменить драйвер теперь не дает.

А ведь до принудительного выключения компа всё работало.
Что можно сделать?

« Последнее редактирование: 23 Февраля 2019, 12:49:01 от de-nos »

Печать

Страницы: [1] Вверх

Источник

I used Docker to set up an Ubuntu 18.04 container, and then tried to install the .deb file with an error as shown below.

root@hashirama:/sc5xx_dev/lib/toolchain# dpkg -i  adi-CrossCoreEmbeddedStudio-linux-x86-2.7.0.deb 
(Reading database ... 52942 files and directories currently installed.)
Preparing to unpack adi-CrossCoreEmbeddedStudio-linux-x86-2.7.0.deb ...
dpkg: error processing archive adi-CrossCoreEmbeddedStudio-linux-x86-2.7.0.deb (--install):
 new adi-cces-2.7.0:i386 package pre-installation script subprocess returned error exit status 2
Errors were encountered while processing:
 adi-CrossCoreEmbeddedStudio-linux-x86-2.7.0.deb

Output of sudo apt install ./adi-CrossCoreEmbeddedStudio-linux-x86-2.7.0.deb:

dpkg: error processing archive /sc5xx_dev/lib/toolchain/adi-CrossCoreEmbeddedStudio-linux-x86-2.7.0.deb (—unpack):
new adi-cces-2.7.0:i386 package pre-installation script subprocess returned error exit status 2
Errors were encountered while processing: /sc5xx_dev/lib/toolchain/adi-CrossCoreEmbeddedStudio-linux-x86-2.7.0.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

N0rbert

94.4k30 gold badges223 silver badges407 bronze badges

asked Nov 24, 2018 at 7:02

I find how to solve this question. It’s caused by the «ENV DEBIAN_FRONTEND=noninteractive» in Dockerfile.

To install the ubuntu-18.04 we should set the package in the mode of noninteractive
To install the adi_xxx.deb package we should set the event in the mode of interactive.

So The correct Dockerfile:

RUN apt-get -y update
RUN DEBIAN_FRONTEND=noninteractive apt-get -y -q install net-tools build-essential minicom tftpd-hpa git-all subversion openssh-server ncurses-dev php gawk g++ m4 libncurses5-dev texinfo flex bison php-cli vim php-xml python-setuptools python-dev unzip rsync cpio bc lib32z1 lib32stdc++6 lib32ncurses5

The wrong Dockerfile:

ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get -y update
RUN apt-get -y -q install net-tools build-essential minicom tftpd-hpa git-all subversion openssh-server ncurses-dev php gawk g++ m4 libncurses5-dev texinfo flex bison php-cli vim php-xml python-setuptools python-dev unzip rsync cpio bc lib32z1 lib32stdc++6 lib32ncurses5

Note:
Do not use the command «ENV DEBIAN_FRONTEND=noninteractive» in configuring the Dockerfile this is definitely not a reasonable default, and setting it via ENV should be actively discouraged, Refer to https://github.com/moby/moby/issues/4032

answered Nov 27, 2018 at 5:56

SullivanSullivan

431 gold badge1 silver badge4 bronze badges

For me it seems that it was broken download issue.
I have downloaded your file:

wget http://download.analog.com/tools/CrossCoreEmbeddedStudio/Releases/Release_2.8.0/adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb

and checked it size

$ ls -al adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb
-rw-rw-r— 1 user user 580754562 ноя 25 12:33 adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb

also I checked MD5 sum:

$ md5sum adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb
2814b42b1fdefa254701b2c802e35c1d adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb

It installs normally:

$ sudo apt-get install ./adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'adi-cces-2.8.0:i386' instead of './adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb'
The following NEW packages will be installed:
  adi-cces-2.8.0:i386
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/581 MB of archives.
After this operation, 1 644 MB of additional disk space will be used.
Get:1 /home/user/adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb adi-cces-2.8.0 i386 2.8.0 [581 MB]
Selecting previously unselected package adi-cces-2.8.0:i386.
(Reading database ... 215776 files and directories currently installed.)
Preparing to unpack .../adi-CrossCoreEmbeddedStudio-linux-x86-2.8.0.deb ...
Unpacking adi-cces-2.8.0:i386 (2.8.0) ...
Setting up adi-cces-2.8.0:i386 (2.8.0) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...

Also you need to install 32-bit libraries:

sudo apt-get install libc6:i386 libgtk-3-0:i386 libxtst6:i386

Consider to redownload the file.

answered Nov 25, 2018 at 9:45

N0rbertN0rbert

94.4k30 gold badges223 silver badges407 bronze badges

Источник

0

1

numerixlts@numerixlts-PC:~$ sudo apt-get install guvcview
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Возможно, для исправления этих ошибок вы захотите воспользоваться «apt-get -f install».
Пакеты, имеющие неудовлетворённые зависимости:
guvcview : Зависит: libguvcview-2.0-2 но он не будет установлен
Рекомендует: uvcdynctrl но он не будет установлен
libnvidia-ifr1-390 : Зависит: libnvidia-gl-390 но он не будет установлен
libnvidia-ifr1-390:i386 : Зависит: libnvidia-gl-390:i386 но он не будет установлен
nvidia-driver-390 : Зависит: libnvidia-gl-390 (= 390.87-0ubuntu0~gpu18.04.1) но он не будет установлен
Рекомендует: libnvidia-gl-390:i386 (= 390.87-0ubuntu0~gpu18.04.1)
E: Неудовлетворённые зависимости. Попытайтесь выполнить «apt —fix-broken install», не указывая имени пакета, (или найдите другое решение).

Ну пробовал прописывать «apt —fix-broken install» и «apt-get -f install» (через sudo конечно же), получал такое:

numerixlts@numerixlts-PC:~$ sudo apt-get -f install
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Исправление зависимостей… Готово
Следующие пакеты устанавливались автоматически и больше не требуются:
lib32gcc1 libc6-i386
Для их удаления используйте «sudo apt autoremove».
Будут установлены следующие дополнительные пакеты:
libnvidia-gl-390 libnvidia-gl-390:i386
НОВЫЕ пакеты, которые будут установлены:
libnvidia-gl-390 libnvidia-gl-390:i386
Обновлено 0 пакетов, установлено 2 новых пакетов, для удаления отмечено 0 пакетов, и 102 пакетов не обновлено.
Установлено или удалено не до конца 3 пакетов.
Необходимо скачать 0 B/29,1 MB архивов.
После данной операции, объём занятого дискового пространства возрастёт на 147 MB.
Хотите продолжить? [Д/н] y
(Чтение базы данных … на данный момент установлено 134069 файлов и каталогов.)
Подготовка к распаковке …/libnvidia-gl-390_390.87-0ubuntu0~gpu18.04.1_i386.deb …
отклонение /usr/lib/i386-linux-gnu/libGL.so.1 в /usr/lib/i386-linux-gnu/libGL.so.1.distrib из-за nvidia-340
dpkg-divert: ошибка: несовпадение с пакетом
при удалении «отклонение /usr/lib/i386-linux-gnu/libGL.so.1 из-за libnvidia-gl-390»
найдено «отклонение /usr/lib/i386-linux-gnu/libGL.so.1 в /usr/lib/i386-linux-gnu/libGL.so.1.distrib из-за nvidia-340»
dpkg: ошибка при обработке архива /var/cache/apt/archives/libnvidia-gl-390_390.87-0ubuntu0~gpu18.04.1_i386.deb (—unpack):
new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2
Подготовка к распаковке …/libnvidia-gl-390_390.87-0ubuntu0~gpu18.04.1_amd64.deb …
отклонение /usr/lib/x86_64-linux-gnu/libGL.so.1 в /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib из-за nvidia-340
dpkg-divert: ошибка: несовпадение с пакетом
при удалении «отклонение /usr/lib/x86_64-linux-gnu/libGL.so.1 из-за libnvidia-gl-390»
найдено «отклонение /usr/lib/x86_64-linux-gnu/libGL.so.1 в /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib из-за nvidia-340»
dpkg: ошибка при обработке архива /var/cache/apt/archives/libnvidia-gl-390_390.87-0ubuntu0~gpu18.04.1_amd64.deb (—unpack):
new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2
При обработке следующих пакетов произошли ошибки:
/var/cache/apt/archives/libnvidia-gl-390_390.87-0ubuntu0~gpu18.04.1_i386.deb
/var/cache/apt/archives/libnvidia-gl-390_390.87-0ubuntu0~gpu18.04.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Ну и как удовлетворить зависимости?
(как убрать большой текст в спойлер? cut не помогает)

Источник

This topic has 3 replies, 3 voices, and was last updated May 11-9:56 pm by anticapitalista.

Viewing 4 posts — 1 through 4 (of 4 total)

Posts
May 11, 2021 at 7:31 pm

#59262
Member

model99
I have a frugal install of antiX 19.3

The following text is from trying to do a sudo apt-get –fix-broken install
after having the same error message appear when I did a sudo apt-get dist-upgrade.
```
$ sudo apt-get --fix-broken install
[sudo] password for demo: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libexo-1-0 liblua5.2-0 libvulkan1
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libc6:i386
Suggested packages:
  glibc-doc:i386 locales:i386
Recommended packages:
  libidn2-0:i386
The following NEW packages will be installed:
  libc6:i386
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0 B/2,743 kB of archives.
After this operation, 11.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Preconfiguring packages ...
(Reading database ... 207973 files and directories currently installed.)
Preparing to unpack .../libc6_2.28-10_i386.deb ...
ERROR: Your kernel version indicates a revision number
of 255 or greater.  Glibc has a number of built in
assumptions that this revision number is less than 255.
If you've built your own kernel, please make sure that any
custom version numbers are appended to the upstream
kernel number with a dash or some other delimiter.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.28-10_i386.deb (--unpack):
 new libc6:i386 package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.28-10_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
```
Here is information about my computer:
```
System:
  Host: antix1 Kernel: 4.9.264-antix.1-amd64-smp x86_64 bits: 64 
  Desktop: IceWM 2.3.4 
  Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020 
Machine:
  Type: Laptop System: HP product: HP Notebook v: Type1ProductConfigId 
  serial: <root required> 
  Mobo: HP model: 81EB v: 61.38 serial: <root required> UEFI: Insyde v: F.21 
  date: 10/27/2016 
Battery:
  ID-1: BAT1 charge: 30.4 Wh condition: 30.4/31.1 Wh (98%) 
CPU:
  Dual Core: Intel Core i3-6100U type: MT MCP speed: 700 MHz 
  min/max: 400/2300 MHz 
Graphics:
  Device-1: Intel HD Graphics 520 driver: i915 v: kernel 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) 
  v: 4.5 Mesa 18.3.6 
Network:
  Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
  driver: r8169 
  Device-2: Intel Wireless 3165 driver: iwlwifi 
Drives:
  Local Storage: total: 931.51 GiB used: 10.14 GiB (1.1%) 
Info:
  Processes: 146 Uptime: 12m Memory: 7.76 GiB used: 515.0 MiB (6.5%) 
  Shell: bash inxi: 3.0.36 
```
May 11, 2021 at 7:40 pm

#59264

Member

Xecure

This is a problem already reported in the forum.
The recommendation is to install the latest 4.9.0-264 kernel using the package installer, reboot and select the kernel from the grub advanced boot menu.
When inside the system, check it is the correct kernel 4.9.0-264
uname .r
fix packages again. After this, REMOVE ALL 4.9.XXX kernels except for the 4.9.0-XXX one. This is important so that it automatically boots into this kernel in the future.

May 11, 2021 at 9:46 pm

#59273
Member

model99
As stated in my original post this is a frugal install and from my computer information
you can see kernel 4.9.0-264 is already installed and boots into that kernel.

But I did take your advice to remove any older kernels from the frugal install.

From Synaptics history log:
```
Completely removed the following packages:
linux-image-4.9.235-antix.1-amd64-smp

Removed the following packages:
codecs-antix
libgcc1:i386

Completely removed the following packages:
linux-image-4.9.261-antix.1-amd64-smp
```
After that I did another “sudo apt-get –fix-broken install” and it was clean.

That is a first for me in 15+ years using Linux that I had to remove a Linux kernel
to solve a dependency problem.
May 11, 2021 at 9:56 pm

#59274

Forum Admin

anticapitalista

It maybe a first for you, but the issue was documented.

New builds of 4.4 and 4.9 kernels

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit — leaner and meaner.
Author

Posts

Viewing 4 posts — 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit «Cookie Settings» to provide a controlled consent.

Источник

fathertom: Posts: 3; Joined: 2013-06-21 11:47

[solved] libc6 apt upgrade error on amd64 testing

Post

by fathertom » 2013-06-21 12:04

aptitude full-upgrade fails complaining about libc6 :

Code: Select all

reparing to replace libc6:i386 2.13-38 (using .../archives/libc6_2.17-3_i386.deb) ...
Checking for services that may need to be restarted...
Checking init scripts...

A copy of the C library was found in an unexpected directory:
  '/lib/i386-linux-gnu/ld-2.17.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/lib/i386-linux-gnu' and try again.

dpkg: error processing /var/cache/apt/archives/libc6_2.17-3_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.17-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
dpkg: error processing libc6:amd64 (--configure):
 package libc6:amd64 cannot be configured because libc6:i386 is not ready (current status 'half-installed')
dpkg: dependency problems prevent configuration of libc6-dev:amd64:
 libc6-dev:amd64 depends on libc6 (= 2.17-3); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing libc6-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc-dev-bin:
 libc-dev-bin depends on libc6 (>> 2.17); however:
  Package libc6:amd64 is not configured yet.
 libc-dev-bin depends on libc6 (<< 2.18); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing libc-dev-bin (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc6-i386:
 libc6-i386 depends on libc6 (= 2.17-3); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing libc6-i386 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of locales:
 locales depends on glibc-2.17-1; however:
  Package glibc-2.17-1 is not installed.
  Package libc6:amd64 which provides glibc-2.17-1 is not configured yet.

dpkg: error processing locales (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libc6:amd64
 libc6-dev:amd64
 libc-dev-bin
 libc6-i386
 locales

Here is the information I have been able to gather though I don’t know what to do to fix this issue.

Code: Select all

uname -a 
Linux satori 2.6.39-2-amd64 #1 SMP Wed Jun 8 11:01:04 UTC 2011 x86_64 GNU/Linux

Code: Select all

lsb_release --all   
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux testing (jessie)
Release:        testing
Codename:       jessie

Code: Select all

dpkg --audit 
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
 libc6-dev:amd64      Embedded GNU C Library: Development Libraries and Header 
 libc-dev-bin         Embedded GNU C Library: Development binaries
 libc6-i386           Embedded GNU C Library: 32-bit shared libraries for AMD64
 locales              Embedded GNU C Library: National Language (locale) data [
 libc6:amd64          Embedded GNU C Library: Shared libraries

The following packages are only half installed, due to problems during
installation.  The installation can probably be completed by retrying it;
the packages can be removed using dselect or dpkg --remove:
 libc6:i386           Embedded GNU C Library: Shared libraries

Code: Select all

dpkg --configure -a  
dpkg: error processing libc6:amd64 (--configure):
 package libc6:amd64 cannot be configured because libc6:i386 is not ready (current status 'half-installed')
dpkg: dependency problems prevent configuration of libc6-dev:amd64:
 libc6-dev:amd64 depends on libc6 (= 2.17-3); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing libc6-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc-dev-bin:
 libc-dev-bin depends on libc6 (>> 2.17); however:
  Package libc6:amd64 is not configured yet.
 libc-dev-bin depends on libc6 (<< 2.18); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing libc-dev-bin (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc6-i386:
 libc6-i386 depends on libc6 (= 2.17-3); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing libc6-i386 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of locales:
 locales depends on glibc-2.17-1; however:
  Package glibc-2.17-1 is not installed.
  Package libc6:amd64 which provides glibc-2.17-1 is not configured yet.

dpkg: error processing locales (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libc6:amd64
 libc6-dev:amd64
 libc-dev-bin
 libc6-i386
 locales

Code: Select all

apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  libc6:i386 libc6-i686:i386
Suggested packages:
  glibc-doc:i386 locales:i386
The following packages will be upgraded:
  libc6:i386 libc6-i686:i386
2 upgraded, 0 newly installed, 0 to remove and 710 not upgraded.
6 not fully installed or removed.
Need to get 0 B/5,414 kB of archives.
After this operation, 811 kB of additional disk space will be used.
Do you want to continue [Y/n]? 
Reading changelogs... Done
Preconfiguring packages ...
Selecting previously unselected package libc6:i386.
(Reading database ... 238897 files and directories currently installed.)
Preparing to replace libc6:i386 2.13-38 (using .../archives/libc6_2.17-3_i386.deb) ...
Checking for services that may need to be restarted...
Checking init scripts...

A copy of the C library was found in an unexpected directory:
  '/lib/i386-linux-gnu/libc-2.17.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/lib/i386-linux-gnu' and try again.

dpkg: error processing /var/cache/apt/archives/libc6_2.17-3_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.17-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Code: Select all

aptitude reinstall libc6
The following packages will be REINSTALLED:
  libc6{b} 
The following partially installed packages will be configured:
  libc-dev-bin libc6-dev libc6-i386 locales 
0 packages upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 712 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
The following packages have unmet dependencies:
 libc6 : Breaks: libc6:i386 (!= 2.17-3) but 2.13-38 is installed and it is kept back.
 libc6:i386 : Breaks: libc6 (!= 2.13-38) but 2.17-3 is installed.

Code: Select all

dpkg -l | grep libc6; apt-cache policy libc6 
iU  libc6:amd64                            2.17-3                             amd64        Embedded GNU C Library: Shared libraries
iH  libc6:i386                             2.13-38                            i386         Embedded GNU C Library: Shared libraries
iU  libc6-dev:amd64                        2.17-3                             amd64        Embedded GNU C Library: Development Libraries and Header Files
iU  libc6-i386                             2.17-3                             amd64        Embedded GNU C Library: 32-bit shared libraries for AMD64
ii  libc6-i686:i386                        2.13-38                            i386         Embedded GNU C Library: Shared libraries [i686 optimized]
libc6:
  Installed: 2.17-3
  Candidate: 2.17-3
  Version table:
 *** 2.17-3 0
        500 http://cdn.debian.net/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status

Last edited by fathertom on 2013-06-21 20:06, edited 1 time in total.

cynwulf

Re: libc6 apt upgrade error on amd64 testing with multilib

Post

by cynwulf » 2013-06-21 14:59

A few problems:

1) You are running an old kernel — older than the current stable kernel — 2 years old in fact.

2) You are trying to upgrade to a version of libc6 from the testing branch, which itself seems out of date.

3) You are trying to use aptitude for upgrades — use apt-get

Post the output of the following:

fathertom: Posts: 3; Joined: 2013-06-21 11:47

Re: libc6 apt upgrade error on amd64 testing with multilib

Post

by fathertom » 2013-06-21 19:22

I tried the upgrade before yes.

Usually I connect with ssh and run my upgrade in a byobu/tmux session but this time byobu was failing at launch for some reason, so I ran the upgrade directly in the ssh session and my internet connection dropped during the aptitude full-upgrade process, at the step where it ask about upgrading glibc6 or aborting the upgrade.

Upon reconnection and restarting the full-upgrade process I was hit by this unexpected error.

Code: Select all

ll /lib/i386-linux-gnu/ld*
-rwxr-xr-x 1 root root 117960 Dec 30 17:45 /lib/i386-linux-gnu/ld-2.13.so
-rwxr-xr-x 1 root root 134344 May 16 13:22 /lib/i386-linux-gnu/ld-2.17.so
lrwxrwxrwx 1 root root     10 May 16 13:22 /lib/i386-linux-gnu/ld-linux.so.2 -> ld-2.17.so
lrwxrwxrwx 1 root root     10 Jun 21 12:30 /lib/i386-linux-gnu/ld-linux.so.2.dpkg-tmp -> ld-2.13.so

My sources.list is empty, I use split files in sources.list.d which contains these repositories:

Code: Select all

##########################################################
## debian official repositories (mirrors) - testing
##########################################################
deb http://cdn.debian.net/debian testing main contrib non-free
deb-src http://cdn.debian.net/debian testing main contrib non-free

##########################################################
## debian security updates - testing
##########################################################
deb http://security.debian.org/ testing/updates main contrib non-free
deb-src http://security.debian.org/ testing/updates main contrib non-free

#samsung unified driver repo
deb http://www.bchemnet.com/suldr/ debian extra

# Opera .deb repository
deb http://deb.opera.com/opera/ stable non-free

## Sun virtualbox repository (www.virtualbox.org)
deb http://download.virtualbox.org/virtualbox/debian wheezy contrib## Sun virtualbox repository (www.virtualbox.org)
deb http://download.virtualbox.org/virtualbox/debian squeeze contrib

## zsh-lovers @ grml
deb     http://deb.grml.org/ grml-stable  main

1) this machine was upgraded and rebooted 41 days ago. isn’t the full-upgrade supposed to upgrade the kernel along ?
The box is in a remote location 800km away, so I’d rather not reboot the box unless I’m sure it will boot. I’d rather save myself a 1600km trip if I can.
Anyways I can’t install a newer kernel due to apt complaining about the libc6 mess.

2) the box runs testing but it’s weird that the branch seems out of date as I ran apt update before the upgrade as usual.
How can I fix this ?

3) aptitude was the recommended method in the official documentation when I installed lenny/testing and I read that it was better to stick either aptitude or apt-get but not mix use of both. apt-get dist-upgrade fails too.

fathertom: Posts: 3; Joined: 2013-06-21 11:47

Re: [solved] libc6 apt upgrade error on amd64 testing

Post

by fathertom » 2013-06-21 20:14

Thanks for your help guys. I fixed it.

It seems lithopsian was on the right track and something went fishy when the first upgrade attempt was killed.

Following instruction from this web page: http://shearer.org/Debugging_Dpkg_Problems

I moved the «unexpected» file out of the way ran apt-get -f install until the upgrade finally went through.

So the following files went from /lib/i386-linux-gnu to /lib/tmp

Code: Select all

May 16 13:22 ld-2.17.so
May 16 13:22 libc-2.17.so
May 16 13:22 libdl-2.17.so
May 16 13:22 libm-2.17.so
May 16 13:22 libpthread-2.17.so
May 16 13:22 librt-2.17.s

libc6 got upgraded and now I can use apt again.

I was missing the linux-image-amd64 package for some reasons which is why the kernel wasn’t upgraded along.

For the records, there is another possible solution I haven’t tried on the knoppix forums: http://knoppix.net/forum/threads/29465- … .?p=124943

Источник

The package’s .preinst script is failing for some reason.

To find out why, examine the script in /var/lib/dpkg/info/PACKAGENAME.preinst

If you want to see exactly which line the script is failing on, edit the .preinst script and add set -x immediately after the #! line. This turns on execution tracing in the script.

NOTE: This assumes that the .preinst script is a shell script (either posix sh or bash). Almost all .preinst (and .postinst, .prerm, and .postrm) scripts are shell scripts but they don’t have to be, they could be any executable. e.g. on my main desktop machine with 9104 packages installed, 14 are perl scripts, 1 is a compiled executable (bash’s preinst — it can’t assume there is a functioning shell already installed), and all of the rest are shell scripts…9041 are POSIX shell scripts, 63 are bash scripts. If the .preinst is perl or python or something else, you’ll have to figure out how to enable debugging or execution trace mode or similar in that language.

Then run dpkg --configure --pending.

This will cause dpkg to try to configure the half-installed package. DO NOT reinstall it with dpkg -i, that will overwrite your edited .preinst script with the version in the .deb package.

This may give you enough information to fix the problem. It may be something simple like an unexpected or uncaught exit code from a program (most .preinst etc scripts have set -e, to make them terminate on the first error), or assuming that a directory already exists (and this may be due to an undeclared dependency in the package’s debian/control file — i.e it should depend on foo but doesn’t. just install foo anyway)

Once it’s fixed, run dpkg --configure --pending again, and the package should be properly installed.

If the .preinst script is buggy, there’s a reasonable chance that the .postinst (and/or .prerm and .postrm) scripts will be too. You may need to fix them as well.

Don’t forget to submit a bug report to whoever made the package so they can fix it.

Источник

[SOLVED] nvidia errors during driver update

Re: nvidia errors during driver update

Re: nvidia errors during driver update

Re: [SOLVED] nvidia errors during driver update

Re: [SOLVED] nvidia errors during driver update

Re: [SOLVED] nvidia errors during driver update

Re: [SOLVED] nvidia errors during driver update

Re: [SOLVED] nvidia errors during driver update

Неудовлетворённые зависимости

Linux Mint Forums

[SOLVED] Issue when installing nvidia-driver

[SOLVED] Issue when installing nvidia-driver

Re: Issue when installing nvidia-driver

Re: Issue when installing nvidia-driver

Re: Issue when installing nvidia-driver

Re: Issue when installing nvidia-driver

Linux Mint Forums

[SOLVED] Generic package post-installation script subprocess returned error exit status 1

[SOLVED] Generic package post-installation script subprocess returned error exit status 1

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Re: Update problem: » . . . generic package post-installation script subprocess returned error exit status 1″

Неудовлетворённые зависимости

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> de-nos

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> andytux

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> de-nos

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> Morisson

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> Morisson

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> DimanBG

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> de-nos

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> Morisson

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> de-nos

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> Morisson

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> de-nos

alang

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> de-nos

[solved] libc6 apt upgrade error on amd64 testing

Re: libc6 apt upgrade error on amd64 testing with multilib

Re: libc6 apt upgrade error on amd64 testing with multilib

Re: [solved] libc6 apt upgrade error on amd64 testing

de-nos

andytux

de-nos

Morisson

Morisson

DimanBG

de-nos

Morisson

de-nos

Morisson

de-nos

de-nos