Bug#755947: libquvi: error: server response code 403 (conncode=0)

Package: cclive Version: 0.7.16-2+b1 Severity: grave $ cclive http://www.youtube.com/watch?v=CvKP3_1PL5c Checking ... ... .libquvi: error: server response code 403 (conncode=0) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe.

Bug#750605: screen goes berserk, had to downgrade

found 750605 2:2.99.914-1~exp1 thanks ma == maximilian attems m...@stro.at writes: ma On Thu, Jun 05, 2014 at 05:33:21PM +0800, 積丹尼 Dan Jacobson wrote: VC == Vincent Cheng vch...@debian.org writes: VC Section Device VC Identifier Intel Graphics VC Driver intel VC Option AccelMethod

Bug#756650: libgs9 : Depends: libtrio1 ( 1.14-0) which is a virtual package.

Package: libgs9 Severity: grave The following packages have unmet dependencies: ghostscript : Depends: libtrio1 ( 1.14-0) which is a virtual package. libgs9 : Depends: libtrio1 ( 1.14-0) which is a virtual package. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a

Bug#756818: update-rc.d: error: insserv rejected the script header

Package: qemu-system-x86 Version: 2.1+dfsg-1 Severity: grave Setting up qemu-system-x86 (2.1+dfsg-1) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults insserv: FATAL: service libvirt-bin has to exists for service libvirt-guests insserv: exiting

Bug#750605: UXA regression causes BENQ FP747 screen to go berserk upon xrandr --auto

retitle 750605 UXA regression causes BENQ FP747 screen to go berserk upon xrandr --auto thanks (Fixing title to match my discoveries which I have posted on the https://bugs.freedesktop.org/show_bug.cgi?id=82068 ) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a

Bug#742875: why doesn't the command do it for us

This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Why not do it for the user instead of having him type it in year after year? -- To

Bug#742875: why doesn't the command do it for us

Furthermore, the message assumes everybody has gdk-pixbuf-query-loaders on their $PATH! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#742875: why doesn't the command do it for us

MB It's done automatically, via a dpkg trigger I'm saying that instead of bothering the person doing the apt-get update, the script should just fix the problem itself. Being that this will never get fixed apparently. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a

Bug#762870: can't boot!

Me too, can't boot. trace.log Description: Binary data

Bug#762870: can't boot!

All I know is I couldn't boot with that thing at the top of # ls /boot/ -ltog -rw-r--r-- 1 2907647 09-26 08:46 initrd.img-3.16-2-686-pae drwxr-xr-x 54096 09-23 00:39 grub -rw-r--r-- 1 2726738 09-22 23:00 initrd.img-3.16-1-686-pae -rw-r--r-- 1 2089608 09-21 01:56 System.map-3.16-2-686-pae

Bug#764021: How are we going to boot with an empty etc/fstab?

Package: initramfs-tools Version: 0.117 Severity: critical File: /usr/share/initramfs-tools/hooks/fsck How are we going to boot with an empty etc/fstab? It is the only empty file in the whole initrd.img ! dd if=/boot/initrd.img-3.16-2-686-pae skip=6|zcat| cpio -vt|perl -anwle 'next if /^d/;

Bug#764021: 118 fails to boot to boot

Your 118 also fails to boot to boot. (Your 118 also fails to boot in addition.) It says rebooting in 5 seconds and indeed reboot in 5 seconds, too short for me to read what else it said. Even though I have panic=33 to give it more time. Maybe it has to do with the Warning: couldn't identify

Bug#764174: new _apt owner not ready for shared mounts

Package: apt Version: 1.1~exp3 Severity: grave # find /var/cache/apt/archives/ /var/lib/apt/lists/ -printf '%u %g\n'|sort|uniq -c 254 119 nogroup 2013 119 root 13 root root # grep _apt /etc/passwd _apt:x:111:65534::/home/_apt:/bin/false The problem is that those directories are

Bug#764174: workaround for sneakernet

OK I now do chown -R _apt:root /var/cache/apt/archives/ /var/lib/apt/lists/ chown root /var/cache/apt/archives/lost+found /var/lib/apt/lists/lost+found in one of my boot scripts, sort of like rc.local. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of

Bug#764174: workaround for sneakernet

Then after changing the owners, upon doing aptitude update I get # find /var/cache/apt/archives/ /var/lib/apt/lists/ -printf '%u %g\n'|sort|uniq -c 16 _apt nogroup 2257 _apt root 7 root root Just wanted to let you know. -- To UNSUBSCRIBE, email to

Bug#764275: downgrading 37.0.2062.120-4 to 37.0.2062.120-3 works

Had to downgrade 37.0.2062.120-4 to 37.0.2062.120-3 or else: Chrome_IOThread[18222]: segfault at 0 ip b081cefa sp a840b090 error 4 in libstdc++.so.6.0.20[b07d4000+e6000] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#764772: segfaults if ever logged in to chromium before

Package: chromium Version: 38.0.2125.101-1 Severity: grave I am guessing that chromium will segfault if one ever logged in to chromium before. [9195:9195:1011/062627:ERROR:account_tracker.cc(306)] OnGetTokenFailure: Invalid credentials. Segmentation fault 10月 11 06:25:54 jidanni5 kernel:

Bug#750605: screen goes berserk, had to downgrade

Package: xserver-xorg-video-intel Version: 2:2.99.911+git20140529-1~exp2 Severity: grave 2:2.99.911+git20140529-1~exp2 makes screen go berserk. 2:2.99.911+git20140529-1~exp1 works fine. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#750605: screen goes berserk, had to downgrade

On https://wiki.ubuntu.com/X/Testing/IntelSNA it seems to say that all I can expect to do is use your workaround VC Section Device VC Identifier Intel Graphics VC Driver intel VC Option AccelMethod uxa VC EndSection and forget about reporting bugs, on my jidanni3

Bug#750605: screen goes berserk, had to downgrade

VC == Vincent Cheng vch...@debian.org writes: VC Section Device VC Identifier Intel Graphics VC Driver intel VC Option AccelMethod uxa VC EndSection Indeed, that fixes it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe.

Bug#750605: screen goes berserk, had to downgrade

found 750605 2:2.99.912-1~exp1 thanks ma == maximilian attems m...@stro.at writes: ma Newer snapshat has sna fixes, please test 2:2.99.911+git20140607-1~exp1 ma (without uxa fallback) What package is that? Where can I get it? All I know is the installed # apt-cache policy $@

Bug#751359: /etc/chromium.d/README: line 1: Any: command not found

Package: chromium Version: 36.0.1985.49-1 Severity: grave /etc/chromium.d/README: line 1: Any: command not found /usr/bin/chromium: line 32: jessie/sid: No such file or directory ! ! ! ! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe.

Bug#752047: latter half of Chinese lines now injured suddenly

Anyway in all cases the final character of what does show is deformed. Still displays but is deformed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752047: latter half of Chinese lines now injured suddenly

Kool! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752047: latter half of Chinese lines now injured suddenly

Do add all those missing chars I mentioned in another bug one day too... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#743042: alternative path /usr/bin/compare-im6 doesn't exist

VF BTW, there was no need to reopen #709845: while the symptoms were VF the same, it was a different cause. OK. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#746330: dependency on virtual package makes package uninstallable

Package: chromium Severity: grave Version: 34.0.1847.116-1~deb7u1 # aptitude install chromium The following packages will be upgraded: chromium{b} (D: libudev0) The following packages have unmet dependencies: chromium : Depends: libudev0 (= 146) which is a virtual package. The following

Bug#746330: I use sid

chromium: Installed: 33.0.1750.152-1 Candidate: 34.0.1847.116-1~deb7u1 Version table: 34.0.1847.116-1~deb7u1 0 500 http://ftp.br.debian.org/debian/ unstable/main i386 Packages *** 33.0.1750.152-1 0 100 /var/lib/dpkg/status -- To UNSUBSCRIBE, email to

Bug#746330: still cannot install chromium on sid

Please be aware that this bug has not been solved still. # apt-cache policy chromium chromium: Installed: 33.0.1750.152-1 Candidate: 34.0.1847.116-1~deb7u1 Version table: 34.0.1847.116-1~deb7u1 0 500 http://ftp.br.debian.org/debian/ unstable/main i386 Packages ***

Bug#738775: insserv: FATAL: service libvirt-bin is missed in the runlevels 2 3 4 5 to use service libvirt-guests

Can't do anything now. # aptitude purge The following partially installed packages will be configured: initscripts No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 62 not upgraded. Need to get 0 B of archives. After unpacking 0 B will

Bug#757543: MUST NOT say ***** REBOOT LINUX ***** before safe to do so

Package: e2fsprogs Version: 1.42.11-2 Severity: grave File: /sbin/fsck.ext4 fsck MUST NOT say * REBOOT LINUX * before completely writing and syncing to disk! Simply kindly say that as the last thing before exiting. Otherwise: the user will assume the system has halted and it is time

Bug#757544: Don't say ***** FILE SYSTEM WAS MODIFIED ***** before actually finished modifying!

Package: e2fsprogs Version: 1.42.11-2 Severity: grave File: /sbin/fsck.ext4 fsck says * FILE SYSTEM WAS MODIFIED * but in fact, when it says it, the truth is * FILE SYSTEM IS BEING MODIFIED * and the user had better not be deceived otherwise and start pulling on his disks... Or

Bug#757544: write and sync first

Only say it after a full write and sync. Yes this could mean many minutes staring at a blank screen, you might add some progress messages if you want, but nothing that might fool the user into taking out his disk before it is safe to do so! -- To UNSUBSCRIBE, email to

Bug#757543: MUST NOT say ***** REBOOT LINUX ***** before safe to do so

forcemerge 757543 757544 thanks The main damage appears to be tons of missing .so files! Good thing I can use dpkg -V ! You probably want to use two messages BEGINNING TO DONE DOING ... YOU MAY NOW SAFELY REMOVE... Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org

Bug#757850: libjpeg-progs depends on libjpeg-turbo-progs (= 1:1.3.1-1); however...

Package: libjpeg-progs Severity: grave Setting up libopenvg1-mesa:i386 (10.2.5-1) ... dpkg: dependency problems prevent configuration of libjpeg-progs: libjpeg-progs depends on libjpeg-turbo-progs (= 1:1.3.1-1); however: Package libjpeg-turbo-progs is not installed. dpkg: error processing

Bug#757996: Illegal instruction

Package: imagemagick-6.q16 Version: 8:6.8.9.6-1 Severity: grave File: /usr/lib/i386-linux-gnu/ImageMagick-6.8.9/bin-Q16/import $ import /tmp/n.png Illegal instruction -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#758760: [Pkg-gmagick-im-team] Bug#758760: dpkg-maintscript-helper: error: original symlink target is not an absolute path

BR == Bastien ROUCARIES roucaries.bast...@gmail.com writes: BR Jidani could you retest ? Yes it installs with no errors now I recall. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#759757: symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main

Package: pavucontrol Version: 2.0-2 Severity: grave $ pavucontrol pavucontrol: symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#759757: downgrade helps

OK this works: Downgrade the following packages: 1) libpulse-mainloop-glib0 [5.0-10 (experimental, now) - 5.0-6 (unstable)] 2) libpulse0 [5.0-10 (now) - 5.0-6 (unstable)] 3) libpulsedsp [5.0-10 (experimental, now) - 5.0-6 (unstable)] 4) pulseaudio [5.0-10 (experimental, now) -

Bug#766448: 0.116 to 0.118 makes systems unbootable with 5 second message

Package: initramfs-tools Version: 0.118 Severity: grave On all my systems, 0.116 works fine, 0.118 just gives some message about rebooting in 5 seconds that is not enough time to read. I.e., the system becomes unbootable. 1. Please tell me what steps you would like me to take. Thanks. -- To

Bug#766448: root fstype auto in /etc/fstab guaranteed unbootable

reopen 766448 retitle root fstype auto in /etc/fstab guaranteed unbootable thanks Please try these simple steps: Change /etc/fstab making the type for / be auto, not ext4 etc. Now with initramfs-tools Ver: 0.118 installed, run update-initramfs -u and reboot. But first see also #766578. -- To

Bug#766448: root fstype auto in /etc/fstab guaranteed unbootable

For 0.118 not only did I discover setting the root fstype to auto in /etc/fstab and then running mkinitramfs -u make the system guaranteed unbootable, furthermore I found this code in /usr/share/initramfs-tools/hook-functions # check that fstype rootfs recognition if [ ${FSTYPE} =

Bug#766448: why one would want fstype auto for /

You might ask why one would want fstype auto for /. Well sometimes it is a lifesaver. E.g., when trying to boot with a older kernel that doesn't understand newer filesystems. I don't recall the exact details... but it gave me the flexibility to change something... -- To UNSUBSCRIBE, email to

Bug#766908: libpepflashplayer.so: cannot open shared object file: Operation not permitted

Package: pepperflashplugin-nonfree Version: 1.8 Severity: grave # set https://www.facebook.com/video.php?v=751699798232656 # su - nobody -c 'HOME=/tmp; chromium '$@ ATTENTION: default value of option force_s3tc_enable overridden by environment. failed to create drawable

Bug#768533: ImportError: cannot import name HTTPSConnection

Package: reportbug Version: 6.6.0 Severity: grave $ reportbug --template apt-show-versions Traceback (most recent call last): File /usr/bin/reportbug, line 38, in module from reportbug import utils File /usr/lib/python2.7/dist-packages/reportbug/utils.py, line 70, in module import

Bug#768543: ImportError: /usr/lib/python2.7/lib-dynload/_ssl.i386-linux-gnu.so: symbol SSLv3_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference

Package: libpython2.7 Severity: grave Version: 2.7.8-11 $ youtube-dl --version Traceback (most recent call last): File /usr/bin/youtube-dl, line 9, in module load_entry_point('youtube-dl==2014.10.30', 'console_scripts', 'youtube-dl')() File

Bug#768541: downgrading openssl doesn't help

# set openssl # apt-cache policy $@ openssl: Installed: 1.0.2~beta3-1 Candidate: 1.0.2~beta3-1 Version table: *** 1.0.2~beta3-1 0 990 http://ftp.tw.debian.org/debian/ experimental/main i386 Packages 100 /var/lib/dpkg/status 1.0.1j-1 0 500

Bug#768541: downgrading openssl doesn't help

OK thanks Salvatore! I am now back in business with # aptitude install libssl1.0.0/unstable The following packages will be DOWNGRADED: libssl1.0.0 dpkg: warning: downgrading libssl1.0.0:i386 from 1.0.2~beta3-1 to 1.0.1j-1 # aptitude forbid-version libssl1.0.0 -- To UNSUBSCRIBE, email to

Bug#769625: /usr/bin/midori: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory

Package: midori Version: 0.4.3+dfsg-0.2 Severity: grave $ midori /usr/bin/midori: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory -- System Information: Debian Release: jessie/sid APT prefers experimental APT policy: (990,

Bug#769740: compatibility patch for apt

Package: pepperflashplugin-nonfree Version: 1.8 Severity: grave --- /usr/sbin/update-pepperflashplugin-nonfree 2014-10-22 14:26:45.0 +0800 +++ /usr/sbin/update-pepperflashplugin-nonfree.NEW 2014-11-16 09:30:57.263926206 +0800 @@ -161,6 +161,7 @@ Dir .;

Bug#768543: libpython2.7-minimal vs. POODLE

reassign 768543 libpython2.7-minimal found 768543 2.7.8-11 thanks I am guessing that libpython2.7-minimal needs to be fixed to match the POODLE changes needed when upgrading libssl1.0.0:i386 from 1.0.2~beta2-1 to 1.0.2~beta3-1, or else it breaks many packages. -- To UNSUBSCRIBE, email to

Bug#769625: Unreproducible

A fresh reinstall still reproduces it on my j3 machine. No bug however on j2. NW Could this be related to a plugin or extension installed on the system? Here is a list of the different packages between j2 (left) and j3. mountpoint -q /cf/ set -xe; m=/cf/versions-$(hostname);\ if test $m -nt

Bug#769625: Unreproducible

Indeed installing libgcrypt11 makes the bug go away. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#770908: aptitude does not know about the new _apt user. Must use apt-get update as a workaround

Package: aptitude Version: 0.6.11-1+b1 Severity: grave aptitude does not know about the new _apt user in e.g., apt 1.1~exp8. Any use of aptitude update will leave filesystem permissions in an inconsistent state. Please use apt-get update as a workaround. Symptoms look like: E: Could not open

Bug#771739: could not start nodm with systemd 217-1 or 217-2

Package: systemd Version: 217-2 Severity: grave Could not start nodm with systemd 217-1 or 217-2. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#771739: could not start nodm with systemd 217-1 or 217-2

Using 217-2 says nodm is masked. Had to revert to 215-7 to get it to work. Give it a try and tell me what happens. # nodm configuration # Set NODM_ENABLED to something different than 'false' to enable nodm NODM_ENABLED=true # User to autologin for NODM_USER=jidanni # First vt to try when

Bug#771993: feh: relocation error: /usr/lib/i386-linux-gnu/libcurl.so.4: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference

Package: feh Version: 2.12-1 Severity: grave $ feh feh: relocation error: /usr/lib/i386-linux-gnu/libcurl.so.4: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org

Bug#771993: Versions of packages feh depends on

Versions of packages feh depends on: ii libcurl3 7.38.0-3 Can't even do feh --help. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#779717: FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file

Package: chromium Version: 41.0.2272.76-1 Severity: grave $ chromium [0304/210821:FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#768476: can't even do curl --version

All I know is on Debian curl is unusable, https://sourceforge.net/p/curl/bugs/1483/ but wget works fine. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#768476: can't even do curl --version

OK thanks. I have come up with a workaround: # aptitude purge libssl1.0.0 Choose: The following actions will resolve these dependencies: Downgrade the following packages: 1) libssl1.0.0 [1.0.2-1 (experimental, now) - 1.0.1k-1 (unstable)] 2) openssl [1.0.2-1 (experimental, now) -

Bug#784009: Segmentation fault

Package: wget Version: 1.16.3-2 Severity: grave $ wget Segmentation fault -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784009: want to back out to get wget working again

[DOWNGRADE] libgnutls-deb0-28:i386 3.3.15-3 - 3.3.15-2 Working! Then today: [UPGRADE] libgnutls-deb0-28:i386 3.3.15-2 - 3.3.15-4 Broken AGAIN! I guess aptitude forbid-version is not strong enough. Looks like I will need aptitude hold. -- To UNSUBSCRIBE, email to

Bug#784009: want to back out to get wget working again

I don't know how to get wget 1.16.3-2 working again. It is not clear which dpkg -i actions I should do. Debian Release: stretch/sid APT prefers experimental APT policy: (990, 'experimental'), (500, 'unstable') Architecture: i386 (i686) Versions of packages wget depends on: ii libc6

Bug#784009: want to back out to get wget working again

OK thanks. This worked, /var/log/aptitude: [REMOVE, NOT USED] libhogweed3:i386 [REMOVE, NOT USED] libnettle5:i386 [DOWNGRADE] libgnutls-deb0-28:i386 3.3.15-3 - 3.3.15-2 [DOWNGRADE] libgnutls-openssl27:i386 3.3.15-3 - 3.3.15-2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org

Bug#784009: Documenting which version works

Yes, anything after 3.3.15-2 is broken. FP == Francesco Poli invernom...@paranoici.org writes: FP Hello, FP if I understand correctly, libgnutls-deb0-28/3.3.15-2 is not affected FP by this bug. FP I am hence documenting this, by adding a fixed version to the BTS FP tracking info. This should

Bug#786943: installing android-libhost doesn't fix the problem either

Installing android-libhost doesn't fix the problem either. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#786943: aapt: error while loading shared libraries: libhost.so: cannot open shared object file: No such file or directory

Package: aapt Version: 21-2 Severity: grave File: /usr/bin/aapt $ aapt aapt: error while loading shared libraries: libhost.so: cannot open shared object file: No such file or directory -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#791696: emacs-w3m ruined. Nowadays half the time just get Something seems to be wrong with URL or this system.

X-debbugs-Cc: Katsumi Yamaoka yama...@jpl.org Package: w3m-el-snapshot Version: 1.4.548+0.20150510-1 Severity: grave Starting a few months ago, about half the time, URLs will produce Cannot retrieve URL: https://sources.debian.net/src/antiword/0.37-10/debian/patches/docx.patch/

Bug#794730: symbol lookup error: aptitude: undefined symbol: _ZN7cwidget7widgets5pager8set_textERKSsPKc

Package: libcwidget3 Version: 0.5.17-3+b1 Severity: grave # aptitude aptitude: symbol lookup error: aptitude: undefined symbol: _ZN7cwidget7widgets5pager8set_textERKSsPKc Downgrading to 0.5.17-3 fixes it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of

Bug#804101: Table 'phpmyadmin.pma__column_info' doesn't exist

Severity: grave Package: phpmyadmin Version: 4:4.5.1-1 X-debbusg-Cc: elb...@debian.org Even if one remembers to start the mysql server, the upgrade fails with: Table 'phpmyadmin.pma__column_info' doesn't exist.

Bug#809743: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'

Package: ifupdown Version: 0.8.5 Severity: grave Unpacking libpam-systemd:i386 (228-3) over (228-2+b1) ... dpkg: considering deconfiguration of ifupdown, which would be broken by installation of systemd ... dpkg: yes, will deconfigure ifupdown (broken by systemd) Preparing to unpack

Bug#809744: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'

Package: udev Version: 228-3 Severity: grave Package installation Race Condition? Also filed bug 809743. Unpacking libpam-systemd:i386 (228-3) over (228-2+b1) ... dpkg: considering deconfiguration of ifupdown, which would be broken by installation of systemd ... dpkg: yes, will deconfigure

Bug#809743: Also created bug #809744

Also created bug #809744 .

Bug#808563: better cover up this version fast

You really need to put something else it its place fast. Else users will end up with scrambled disks, and unable to boot. Treat it like a virus. Can't you just copy the previous kernel into a "4.3a" release? That way the damaging kernel won't be the default anymore.

Bug#809744: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'

> "MB" == Michael Biebl writes: MB> We can't unfortunately fix the existing udev.prerm of older versions, MB> only make sure the new one no longer has the problem. Well all I know is the user will get himself into my above state, which takes a # dpkg -i

Bug#809079: xargs: invalid number for -s option

Package: python3.5 Version: 3.5.1-2 Severity: serious Preparing to unpack .../python3.5_3.5.1-2_i386.deb ... xargs: invalid number for -s option Usage: xargs [OPTION]... COMMAND [INITIAL-ARGS]... Run COMMAND with arguments INITIAL-ARGS and more arguments read from input.

Bug#808563: really should be serious bug: data loss

Will try Wednesday. Actually better to have the raid people test. I only have one disk... too risky.

Bug#825918: Actually 1954 error message groups

reopen 825918 thanks There is actually 1954 error groups on my machine. A normal user would and should kill the seemingly runaway situation before hit computer locks up or disks get filled. # sort /tmp/apt_term_log.txt |uniq -c|sort -nr|head 1954 dpkg-query: package 'imagemagick' is not

Bug#825897: Fix-Missing

I'm turning APT::Get::Fix-Missing back on. One little missing package ruins my "sneakernet" offline safe-upgrades, plus I get this message anyway: E: Unable to fetch some packages; try '-o APT::Get::Fix-Missing=true' to continue with missing packages.

Bug#825918: dpkg enters infinite loop upon installing some packages

Package: dpkg Version: 1.18.7 Severity: grave Please try installing this version of imagemagick. Dpkg will enter an infinite loop. # dpkg -i imagemagick_8%3a6.9.2.10+dfsg-2_all.deb Selecting previously unselected package imagemagick. (Reading database ... 148492 files and directories currently

Bug#818540: fix for 818540 never made it into Debian?

I see Date: Fri, 13 May 2016 14:44:52 +0200 but the new package is nowhere to be found. Not in http://incoming.debian.org/debian-buildd/pool/contrib/ either.

Bug#818540: fix for 818540 never made it into Debian?

https://packages.debian.org/search?keywords=pepperflashplugin-nonfree shows you only updated non - i386 :-(

Bug#824133: No longer works at all. Cannot type one single word of Chinese any more

Package: scim-chewing Version: 0.5.0-1 Severity: grave CTRL-SPACE no longer brings up the box that shows what characters I am typing. Had to downgrade to 0.3.5-2 . config Description: my config -- System Information: Debian Release: stretch/sid APT prefers experimental APT policy: (990,

Bug#833419: crashes computer

severity 833419 normal retitle 833419 midori gives black screen on one of my couputers thanks OK I installed https://wiki.debian.org/NvidiaGraphicsDrivers # nvidia-detect Detected NVIDIA GPUs: 00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51G [GeForce 6100] [10de:0242] (rev a2)

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

Yes I can confirm that now I can run X windows on linux-image-4.9.0-1-amd64 Thank you! However at the same time my formerly working backup linux-image-4.8.0-2-amd64 is now broken. Please make sure your fixes don't "fix" more than was intended! Thanks.

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

And, on your Description be sure to say "Building the kernel module has been tested up to Linux ..." "But not necessarily running it (as we don't have all the same hardware as the user."

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

By the way, AB> What is the exact error you get from the kernel when loading the module? AB> You should find this in e.g. dmesg or the journald equivalent of AB> /var/log/messages. Well often important items just fly by on the screen, not logged anywhere. Bug#852229: failing to log output at

Bug#855175: add option to bypass security checks

Package: flashplugin-nonfree Version: 1:3.7 Severity: grave File: /usr/sbin/update-flashplugin-nonfree Please add an option to bypass downloadfile=fp.$upstream.sha512.i386.pgp.asc [ `dpkg --print-architecture` != "amd64" ] ||

Bug#851634: sh -n checks

I would add a sh -n test to the build scripts to avoid such errors getting sent out.

Bug#766884: validity error : ID already defined

Workaround for validity error : ID bottom already defined for libxml2: Installed: 2.9.4+dfsg1-1+b1 just remove the name="bottom" in the input.

Bug#840355: Failed to create spool file /var/spool/exim4//input//...-D: Permission denied

Package: exim4 Version: 4.88~RC2-1 Severity: grave Can't send mail, because: 2016-10-11 04:30:53 Failed to create spool file /var/spool/exim4//input//1bthDp-0002gq-Fy-D: Permission denied -- Package-specific info: Exim version 4.88 #2 built 09-Oct-2016 15:37:08 Copyright (c) University of

Bug#840355: Failed to create spool file /var/spool/exim4//input//...-D: Permission denied

> "AM" == Andreas Metzler writes: AM> Is this a fresh installation or an upgrade? Upgrade from Installed: 4.88~RC1-1 to Candidate: 4.88~RC2-1 AM> What does AM> ls -la /var/spool/exim4/ AM> say? Before: # ls -la /var/spool/exim4/ drwxr-x--- 5 Debian-exim Debian-exim

Bug#840355: Failed to create spool file /var/spool/exim4//input//...-D: Permission denied

Yes. Glad they found the bug.

Bug#846657: ImportError: No module named 'requests'

Severity: grave Package: reportbug Version: 7.0.0 $ reportbug Traceback (most recent call last): File "/usr/bin/reportbug", line 43, in from reportbug import utils File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 43, in from .urlutils import open_url File

Bug#849277: A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading

X-Debbugs-Cc: wink...@gnu.org Package: bbdb3 Version: 3.1.2-6 Severity: grave File: /etc/emacs/site-start.d/50bbdb3.el A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading. --- 50bbdb3.el 2016-07-21 15:21:11.0 +0800 +++ 50bbdb3.NEW.el 2016-12-24

Bug#856624: what happened to my conf file?

Why did you do this? diff -U0 /home/jidanni/.scim/config-old /home/jidanni/.scim/config --- /home/jidanni/.scim/config-old 2013-01-25 09:20:57.0 +0800 +++ /home/jidanni/.scim/config 2017-03-03 07:50:46.094513222 +0800 @@ -6,0 +7,2 @@ +/FrontEnd/ChangeFactoryGlobally = false

Bug#856624: damaged gtk too

Also now even after reverting to the previous version, the fonts are now too small, and hitting the Sans 18 button just causes the menu to collapse.

Bug#856624: pre-disaster set up

Pre-disaster: :: .scim/config :: /DefaultIMEngineFactory/en_US = fcff66b6-4d3e-4cf2-833c-01ef66ac6025 /DefaultIMEngineFactory/si_LK = IMEngine-M17N-si-wijesekera /DefaultIMEngineFactory/ta_IN = IMEngine-M17N-ta-tamil99 /DefaultIMEngineFactory/zh_CN =

Bug#856624: 勿更新！

Debian experimental, unstable 勿更新 scim and gtk stuff！ 會摧毀您的 configuration. 導致 everything becomes small. http://bugs.debian.org/856624 I replaced scim with the old one. At least I got HANYU PINYIN back. Now I have to replace all the gtk stuff (?) to get the font size 18 back instead of the tiny

  1   2   3   >