Bug#1041508: tex-common: fmutil fails to rebuild formats
Le samedi 02 septembre 2023 à 23:47 +0200, Preuße, Hilmar a écrit : > Control: block -1 by 1050807 > > On 02.09.2023 07:57, Emmanuel Charpentier wrote: > > Hi, > > > *** Reporter, please consider answering these questions, where > > appropriate *** > > > > * What led up to the situation? > > > > routine upgrade of testing's tex-common > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > > > I guess you run Debian testing right? Right. > The texlive-binaries recently migrated to testing, but the > texlive-base/texlive-extra/texlive-lang did not due to #1050807. > Therefore the fix for this issue did not enter testing yet. > > Sorry, for the trouble, I should have added a "Breaks" statement to > texlive-binaries. Maybe it makes sense to do that now? Yes, it does : that would avoid the same problem to other poor sods... -- Emmanuel Charpentier > > Hilmar > -- > sigfault >
Bug#1003045: libreoffice: Since testing update on Jan 2, 2021, libreoffice doesn't start.
Package: libreoffice Version: 1:7.2.4-3 Severity: grave Justification: renders package unusable * What led up to the situation? A routine update of Debian testing (bookworm) on Jan 2, 2021 led to a situation where clicking on LibreOffice's or LibreOffice apps' icons is ineffective ; similarly, launching an application from a console's command line returns after a few seconds. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to reinstall Libreoffice applications by : dpkg -l "*libre*office*" | grep -e "^ii" | sed -re "s/[ \t]+/ /g" | cut -d " " -f 2 | sudo xargs apt-get install --reinstall * What was the outcome of this action? Clicking on the gnome menu icons is ineffective (spinning cursor for a few seconds) ; starting an app from the command line initially started the document recovery dialog box ; after having cancelled that operation, starting a LibreOffice application returns after about one second. * What outcome did you expect instead? A normal function of libreoffice app. Possibly related : sudo apt dist-upgrade leaves libc++1 unupgraded, whereas sudo apt install -s wants to uninstall libc++1-11 and libc++abi1-11 and install libc++1-13 libc++abi1-13 libunwind-13. So far, I did **not** proceed. HTH ... -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (650, 'testing'), (60, 'unstable'), (50, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice depends on: ii libreoffice-base1:7.2.4-3 ii libreoffice-calc1:7.2.4-3 ii libreoffice-core1:7.2.4-3 ii libreoffice-draw1:7.2.4-3 ii libreoffice-impress 1:7.2.4-3 ii libreoffice-math1:7.2.4-3 ii libreoffice-report-builder-bin 1:7.2.4-3 ii libreoffice-writer 1:7.2.4-3 ii python3-uno 1:7.2.4-3 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-2.1 ii fonts-crosextra-carlito 20130920-1.1 ii fonts-dejavu2.37-2 ii fonts-liberation1:1.07.4-11 ii fonts-liberation2 2.1.5-1 ii fonts-linuxlibertine5.3.0-6 ii fonts-noto-core 20201225-1 ii fonts-noto-extra20201225-1 ii fonts-noto-mono 20201225-1 ii fonts-noto-ui-core 20201225-1 ii fonts-sil-gentium-basic 1.102-1.1 ii libreoffice-java-common 1:7.2.4-3 ii libreoffice-nlpsolver 0.9+LibO7.2.4-3 ii libreoffice-report-builder 1:7.2.4-3 ii libreoffice-script-provider-bsh 1:7.2.4-3 ii libreoffice-script-provider-js 1:7.2.4-3 ii libreoffice-script-provider-python 1:7.2.4-3 ii libreoffice-sdbc-mysql 1:7.2.4-3 ii libreoffice-sdbc-postgresql 1:7.2.4-3 ii libreoffice-wiki-publisher 1.2.0+LibO7.2.4-3 Versions of packages libreoffice suggests: ii cups-bsd 2.3.3op2-7 ii default-jre [java8-runtime] 2:1.11-72 ii firefox-esr 91.4.0esr-1 ii ghostscript 9.55.0~dfsg-3 ii gnupg2.2.27-2 ii gpa 0.10.0-3+b1 ii gstreamer1.0-libav 1.18.5-1 ii gstreamer1.0-plugins-bad 1.18.5-1+b4 ii gstreamer1.0-plugins-base1.18.5-1 ii gstreamer1.0-plugins-good1.18.5-1+b1 ii gstreamer1.0-plugins-ugly1.18.5-1 ii hunspell-en-us [hunspell-dictionary] 1:2020.12.07-1 ii hunspell-fr-classical [hunspell-dictionary] 1:7.0-1 ii hyphen-en-us [hyphen-hyphenation-patterns] 2.8.8-7 ii imagemagick 8:6.9.11.60+dfsg-1.3 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.3 ii libgl1 1.3.4-2+b1 ii libofficebean-java 1:7.2.4-3 ii libreoffice-gnome1:7.2.4-3 pn libreoffice-grammarcheck ii libreoffice-help-en-us [libreoffice-help]1:7.2.4-3 ii libreoffice-help-fr [libreoffice-help] 1:7.2.4-3 ii libreoffice-l10n-fr [libreoffice-l10n] 1:7.2.4-3 ii libreoffice-librelogo1:7.2.4-3 ii libsane1 1.0.32-4 ii libxrender1 1:0.9.10-1 pn myspell-dictionary ii mythes-en-us [mythes-thesaurus]
Bug#941782: Could you suggest a detailed rescue plan ?
I have been bitten by this one. Severely : one of my systems won't get to the Gnome login screen and stays on a black screen (with an (active) mouse pointer). * apt-get -t stable gir1.2-gnomedesktop-3.0 gnome-desktop3-data \ libgnome-desktop-3-17 won't do a thing. ditto with --allow-downgrades. * apt-get remove gir1.2-gnomedesktop-3.0 gnome-desktop3-data \ libgnome-desktop-3-17 wants to remove a lot of gnome and gnome-related packages. * I *suppose* that "the right use" of dpkg would allow this kind of surgery in the dependency system, allowing to replace a package by its predecessor while temporarily ignoring the dependencies. But I do not understand it well enough to divine the "right" set of operations. Since this happened during a routine update of testing, I suppose I am not alone to have to endure the consequences of an inadvertently missing dependency, and that this plan would be useful to a lot of people. Thanks in advance ! -- Emmanuel Charpentier
Bug#870099: latexdiff: Since some Perl update, latexdiff doesnt't even start
Package: latexdiff
Version: 1.1.1-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Trying to use latexdiff-git, I got :
$ latexdiff-git -r HEAD~1 Spectro1.tex
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in
m/\\zref\@newlabel{ <-- HERE DIFchgb(\d*)}{.*\\abspage{(\d*)}}/ at
/usr/bin/latexdiff-git line 451.
It turns out that I get the same error for *any* invocation of latexdiff :
$ latexdiff --help
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in
m/\\includeonly{ <-- HERE (.*?)}/ at /usr/bin/latexdiff line 1572.
* What exactly did you do (or not do) that was effective (or ineffective)?
Nothing : I can't think of any workaround...
A bit of googling leads to https://github.com/ftilmann/latexdiff/issues/43,
which hints that this bug is fixed in an upstream release not yet in Debian.
This issue also hints at a possible Perl-ish origin of the problem : indeed,
the issue appeared wit perl-5.22.1 and my current perl is :
$ perl --version
This is perl 5, version 26, subversion 0 (v5.26.0) built for x86_64-linux-gnu-
thread-multi
(with 51 registered patches, see perl -V for more detail)
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (650, 'testing'), (60, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.11.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages latexdiff depends on:
ii perl 5.26.0-4
Versions of packages latexdiff recommends:
ii texlive-generic-recommended 2017.20170629-1
ii texlive-latex-base 2017.20170629-1
ii texlive-latex-extra 2017.20170629-1
Versions of packages latexdiff suggests:
ii git 1:2.13.2-3
ii subversion 1.9.6-1+b2
-- no debconf information
Bug#803272: libreoffice-dev: apt-get dist-upgrade -u -f *HANGS* on libreoffice-dev 3a5.0.3~rc1-2
Package: libreoffice-dev Version: 1:5.0.2-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, * What led up to the situation? apt-get update # Then apt-get dist-upgrade -u -f results in a hung apt-get. From another terminal, ps axfw says : [ ... ] 3143 pts/0Ss 0:00 \_ bash 3149 pts/0S 0:00 | \_ sudo -i 3178 pts/0S 0:00 | \_ -bash 19191 pts/0S+ 0:09 | \_ apt-get dist-upgrade -u -f 20570 pts/1Ss+0:00 | \_ /usr/bin/dpkg --status-fd 107 --unpack --auto-deconfigure /var/cache/apt/archives/libreoffice- dev_1%3a5.0.3~rc1 20616 pts/1S+ 0:00 | \_ /bin/sh /var/lib/dpkg/tmp.ci/preinst upgrade 1:5.0.2-1 20617 pts/1S+ 0:00 | \_ /bin/sh /usr/bin/dpkg- maintscript-helper dir_to_symlink /usr/share/doc/libreoffice-dev /usr/share/doc/l 20625 pts/1S+ 0:00 | \_ find /usr/share/doc /libreoffice-dev -print0 20626 pts/1S+ 0:00 | \_ xargs -0 -n1 sh -c ??package="$1" ??file="$2" ??if ! dpkg-query -L "$package" | grep -q -x "$file" [ ... ] * What exactly did you do (or not do) that was effective (or ineffective)? sudo kill : unhangs the apt-get console. dpkg -C : shows libreoffice-dev to be in an incoherent state dpkg --configure --pending : dpkg state database locked by another process apt-get dist-upgrade -u -f : [ Can't get the lock ] rm /var/lib/dpkg/lock ; dpkg -C : [ Can't get the lock : no such file ] * What was the outcome of this action? ===> apt-get hosed. * What outcome did you expect instead? An uneventful update... -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates'), (60, 'unstable'), (55, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-dev depends on: ii libc6 2.19-22 ii libgcc1 1:5.2.1-22 ii libgl1-mesa-glx [libgl1] 10.6.8-1 ii libreoffice-core 1:5.0.3~rc1-2 ii libstdc++65.2.1-22 ii libx11-6 2:1.6.3-1 ii ucpp 1.3.2-1 ii uno-libs3 5.0.3~rc1-2 ii ure 5.0.3~rc1-2 Versions of packages libreoffice-dev recommends: ii default-jre [java5-runtime]2:1.7-52 ii g++4:5.2.1-4 ii libreoffice-java-common1:5.0.3~rc1-2 ii openjdk-6-jre [java5-runtime] 6b31-1.13.3-1 ii openjdk-7-jre [java5-runtime] 7u85-2.6.1-5 Versions of packages libreoffice-dev suggests: ii libmythes-dev2:1.2.4-1 ii libreoffice-dev-doc 1:5.0.2-1 pn libreofficekit-dev -- no debconf information
Bug#792558: zotero-standalone: Zotero-standalone no longer runs in testing
Package: zotero-standalone Version: 4.0.26.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Attempt to use zotero standalone in conjunction with Chromium. I alredy attemped this in the past, but went back to Iceweasel and Zotero for Firefox. For various reasons, I'd like to give Chromium another go. * What exactly did you do (or not do) that was effective (or ineffective)? Starting from the menu : nothing happens. Starting from a terminal : I see exactly this : charpent@SAP5057241:~$ zotero (process:7443): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Error: Platform version '24.5.0' is not compatible with minVersion = 31.0 maxVersion = 40.* * What was the outcome of this action? No functional Zotero * What outcome did you expect instead? A Zotero Window. Note : Google shows that similar problems have been reported, implying different version of xulrunner. the /usr/share/zotero- standalone/application.ini file specivies min and max version for *gecko*. I do not know what this refers to. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates'), (60, 'unstable'), (55, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zotero-standalone depends on: ii iceweasel 38.1.0esr-2 ii xulrunner-17.0 17.0.10esr-1~deb7u1 ii xulrunner-24.0 24.5.0esr-1 ii xulrunner-2929.0.1-2 zotero-standalone recommends no packages. zotero-standalone suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742169: firmware-linux: fimware-linux-free and firmware-linux-nonfree have common files == uninstallable
Package: firmware-linux Version: 0.41 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Trying to purge and reinstall firmwares after my boot being messed up by boot- repair rescue disk (necessary because Window 8 scratched my grub...) * What exactly did you do (or not do) that was effective (or ineffective)? I removed all firmware packages and tried to install firmware-linux * What was the outcome of this action? transcript : root@asus16-ec:~# apt-get install firmware-linux Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les paquets supplémentaires suivants seront installés : firmware-linux-free firmware-linux-nonfree intel-microcode iucode-tool Les NOUVEAUX paquets suivants seront installés : firmware-linux firmware-linux-free firmware-linux-nonfree intel-microcode iucode-tool 0 mis à jour, 5 nouvellement installés, 0 à enlever et 222 non mis à jour. Il est nécessaire de prendre 1 761 ko dans les archives. Après cette opération, 5 428 ko d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] o Réception de : 1 http://ftp.fr.debian.org/debian/ testing/main firmware- linux-free all 3.3 [19,1 kB] Réception de : 2 http://ftp.fr.debian.org/debian/ testing/non-free firmware- linux-nonfree all 0.41 [1 324 kB] Réception de : 3 http://ftp.fr.debian.org/debian/ testing/non-free firmware- linux all 0.41 [9 580 B] Réception de : 4 http://ftp.fr.debian.org/debian/ testing/contrib iucode-tool amd64 1.0.1-1 [29,3 kB] Réception de : 5 http://ftp.fr.debian.org/debian/ testing/non-free intel- microcode amd64 2.20140122.1 [379 kB] 1 761 ko réceptionnés en 4s (424 ko/s) (Lecture de la base de données... 419056 fichiers et répertoires déjà installés.) Preparing to unpack .../firmware-linux-free_3.3_all.deb ... Unpacking firmware-linux-free (3.3) ... dpkg: error processing archive /var/cache/apt/archives/firmware-linux- free_3.3_all.deb (--unpack): tentative de remplacement de « /lib/firmware/dsp56k/bootstrap.bin », qui appartient aussi au paquet linux-firmware 1.106 Preparing to unpack .../firmware-linux-nonfree_0.41_all.deb ... Unpacking firmware-linux-nonfree (0.41) ... dpkg: error processing archive /var/cache/apt/archives/firmware-linux- nonfree_0.41_all.deb (--unpack): tentative de remplacement de « /lib/firmware/matrox/g400_warp.fw », qui appartient aussi au paquet linux-firmware 1.106 dpkg-deb : erreur : le sous-processus coller a été tué par le signal (Relais brisé (pipe)) Sélection du paquet firmware-linux précédemment désélectionné. Preparing to unpack .../firmware-linux_0.41_all.deb ... Unpacking firmware-linux (0.41) ... Sélection du paquet iucode-tool précédemment désélectionné. Preparing to unpack .../iucode-tool_1.0.1-1_amd64.deb ... Unpacking iucode-tool (1.0.1-1) ... Sélection du paquet intel-microcode précédemment désélectionné. Preparing to unpack .../intel-microcode_2.20140122.1_amd64.deb ... Unpacking intel-microcode (2.20140122.1) ... Processing triggers for man-db (2.6.6-1) ... Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/firmware-linux-free_3.3_all.deb /var/cache/apt/archives/firmware-linux-nonfree_0.41_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) BTW, I managed to install the (necessary !) firmwares via dpkg -i --force- overwrite, but that's hardly a solution. * What outcome did you expect instead? A silent install ... *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates'), (60, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages firmware-linux depends on: pn firmware-linux-free none pn firmware-linux-nonfree none Versions of packages firmware-linux recommends: iu intel-microcode 2.20140122.1 ii linux-firmware [amd64-microcode] 1.106 firmware-linux suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717140: maxima: On testing (amd64), maxima crashes at startup
Package: maxima Version: 5.30.0-4 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Following testing... * What exactly did you do (or not do) that was effective (or ineffective)? -- Trying to launch maxima (in a gnome terminal) : charpent@SAP5057241:~$ maxima Maxima encountered a Lisp error: Error in INITIALIZE-RUNTIME-GLOBALS [or a callee]: Cannot open the file /usr/share/doc/maxima/info/./maxima-index.lisp. Automatically continuing. To enable the Lisp debugger set *debugger-hook* to nil. Error in CL-INFO::LOAD-PRIMARY-INDEX [or a callee]: The tag RETURN-FROM- DEBUGGER is undefined. Fast links are on: do (use-fast-links nil) for debugging Broken at CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER. Type :H for Help. 1 (Continue) Retry loading file /usr/share/doc/maxima/info/./maxima- index.lisp. 2 Maxima top-level 3 (Abort) Return to top level. dbl:MAXIMA -- * What was the outcome of this action? At this point, any attempt to get back to the toplevel results in another break : -- dbl:MAXIMA1 Maxima encountered a Lisp error: Error in INITIALIZE-RUNTIME-GLOBALS [or a callee]: Cannot open the file /usr/share/doc/maxima/info/./maxima-index.lisp. Automatically continuing. To enable the Lisp debugger set *debugger-hook* to nil. Error in CL-INFO::LOAD-PRIMARY-INDEX [or a callee]: The tag RETURN-FROM- DEBUGGER is undefined. Fast links are on: do (use-fast-links nil) for debugging Broken at CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER. Type :H for Help. 1 (Continue) Retry loading file /usr/share/doc/maxima/info/./maxima- index.lisp. 2 Maxima top-level 3 (Abort) Return to top level. dbl:MAXIMA2 Error in LISP:LAMBDA-CLOSURE [or a callee]: The tag #:G33007 is missing. Fast links are on: do (use-fast-links nil) for debugging Broken at GO. 1 (Abort) Return to debug level 1. 2 Retry loading file /usr/share/doc/maxima/info/./maxima-index.lisp. 3 Maxima top-level 4 Return to top level. dbl:MAXIMA4 Error in GO [or a callee]: The tag (NIL) is undefined. Fast links are on: do (use-fast-links nil) for debugging Broken at CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER. 1 (Abort) Return to debug level 2. 2 Return to debug level 1. 3 Retry loading file /usr/share/doc/maxima/info/./maxima-index.lisp. 4 Maxima top-level 5 Return to top level. dbl:MAXIMA -- The only way out I found was to killall maxima from another rerminal * What outcome did you expect instead? A working maxima :-)... I *think* that the problem might be lisp-related. Maxima is currently compiled wit gcl in Debian ; the Sage team has standardized on ECL, which, apparently, gives better performance. Time to reconsider ? Or better, to have a multi-lisp solution ? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages maxima depends on: ii gnuplot-x11 4.6.3-2 ii libc6 2.17-7 ii libgmp10 2:5.1.2+dfsg-2 ii libreadline6 6.2+dfsg-0.1 ii libx11-6 2:1.6.0-1 Versions of packages maxima recommends: ii maxima-share 5.30.0-4 Versions of packages maxima suggests: ii maxima-doc5.30.0-4 ii maxima-emacs 5.30.0-4 pn texmacs none ii tk8.5 [wish] 8.5.14-2 ii xmaxima 5.30.0-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622309: The problem has slipped into testing (yay !)...
Le lundi 18 avril 2011 à 05:31 +0200, Marco d'Itri a écrit : On Apr 17, Emmanuel Charpentier emm.charpent...@free.fr wrote: FYI, what I got installed via netinst was udev 671-1. 167-1 *is* buggy *if* you have /run. Currently you are not supposed to have /run on testing sistem, so rm -rf it. Thank you, that was enough to get a functional system back (a first attempt where I rm-Rf'd /run/udev was insufficient). Do you have an idea of the right package to file a (grave :renders the system unusable) bug against ? Thanks again, Emmanuel Charpentier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622309: The problem has slipped into testing (yay !)...
Dear all, I red this afternoon to install a testing (wheezy) system (amd64, FWIW) via netinst (on CD-ROM) and managed to get an (almost) unusable system : after boot, I have no keyboard, no mouse ; I see a failed ! message relative to udev scrolling (fast !) during the boot process. This led me to login through network (thanks to ssh), and to explore /var/log/messages (little help...) and the bug reports, where I found this bug. Current state : - I *do* have a /run/udev/ directory. removing it seems useless (gets re-created after reboot) - trying to /etc/init.d/udev start does *not* work : complains about a socket that it cannot create. - /etc/init.d/udev stop ; /etc/init.d/udev start *does* give me back keyboard and mouse. - I found no permanent (i. e. reboot-surviving) workaround. FYI, what I got installed via netinst was udev 671-1. This bug is highly annoying, and will annoy a lot of people now that it has found its way in testing : many of us peones tend to install testing rather than the (almost always outdated) stable distribution. HTH, Emmanuel Charpentier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594428: fwbuilder 4.1.0-1 uninstallable probably due to libfwbuilder-abi version discrepancy
Package: fwbuilder Version: 4.1.0-1 Severity: grave Justification: renders package unusable libfwbuilder-4.1.0-1 depends on libflwbuilder-abi-4.1.0, which is a virtual package provided by libfwbuilder9. On a testing system, installing libfwbuilder9-4.1.1-1 is *not* recognized as providing the said abi library, and fwbuilder remains unconfigured. Thus fwbuilder 4 is unavailable on this system. -- System Information: Debian Release: squeeze/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fwbuilder depends on: pn fwbuilder-commonnone (no description available) ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib pn libfwbuilder-abi-4.1.0 none (no description available) pn libfwbuilder9 none (no description available) ii libgcc1 1:4.4.4-8GCC support library ii libqt4-dbus 4:4.6.3-1Qt 4 D-Bus module ii libqt4-network 4:4.6.3-1Qt 4 network module ii libqtcore4 4:4.6.3-1Qt 4 core module ii libqtgui4 4:4.6.3-1Qt 4 GUI module ii libsnmp15 5.4.3~dfsg-1 SNMP (Simple Network Management Pr ii libstdc++6 4.4.4-8 The GNU Standard C++ Library v3 ii libxml2 2.7.7.dfsg-4 GNOME XML library ii libxslt1.1 1.1.26-5 XSLT 1.0 processing library - runt ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages fwbuilder recommends: pn fwbuilder-doc none (no description available) fwbuilder suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566189: Bug #566189 on testing (i386)
I have an (experimental) squeeze installation, which has been crippled by something suspiciously looking like this bug for a couple of weeks. The announced fix (packages update to 1.3.1.1-15) does not (yet ?) seem to be available on testing repositories, nor on the squeeze backports repositories. Can someone suggest a workaround for squeeze users ? (No, I'd rather *not* go for unstable. Been there, done that, got the T-shirt...). Sincerely, Emmanuel Charpentier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#320256: (kernel-image-2.4.27-2-k6: FTBFS on its intended target) : more info
I tried to build this kernel on a newer PIV. This dos *not* build with gcc 4.0 or gcc 3.4, but *does* build with gcc 3.3 I'll try this on the target machine, and let you know. -- Emmanuel Charpentier[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
