Bug#996730: Certain menus don't work right when chrome is in the Normal Layer

Package: icewm Version: 2.8.0-1 Severity: grave Are there any other users who can confirm https://github.com/ice-wm/icewm/issues/62 ?

Bug#953032: Please import fix

Can you please update so we can see if https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/137 really fixes the problem? My disks are reaching the breaking point.

Bug#992867: root cause found

https://gitlab.freedesktop.org/xorg/proto/xorgproto/-/issues/35#note_1045802

Bug#992867: Stop flooding syslog! You will fill up the disk.

Package: x11-xkb-utils Version: 7.7+5 Severity: grave Did anybody take a look at syslog recently? It is flooded with Internal error: Could not resolve keysym ... So much so that the disk will fill up.

Bug#992411: Just use clearer message

OK, instead of saying /usr/bin/which: this version of 'which' is deprecated and should not be used.* please say /usr/bin/which: The 'which' utility will be removed in the future. Please use 'command -v' instead. For more info, see ... *Else you mean "tell the maintainer he

Bug#953032: Bug is back, filling up disks like crazy

# ls -l /var/log/syslog* -rw-r- 1 root adm 23119076 08-21 03:15 /var/log/syslog -rw-r- 1 root adm 542530 08-16 01:01 /var/log/syslog.1 -rw-r- 1 root adm 136476 08-08 19:03 /var/log/syslog.2.gz -rw-r- 1 root adm 309712 08-01 11:46 /var/log/syslog.3.gz -rw-r- 1 root adm

Bug#992411: not fixed

reopen 992411 found 992411 5.3-1 thanks All I know is the bug was to make /usr/bin/which keep working. All I see that was 'fixed' was making a news item. There are hundreds of cgi etc. scripts that are now emitting errors.

Bug#992411: Warnings coming out of everywhere

https://en.wikipedia.org/wiki/Which_(command) Please make sure /usr/bin/* stuff keeps working.

Bug#982857: All pages cut off due to IFRAME closing tag bungle

Package: imagemagick-6-common Version: 8:6.9.11.60+dfsg-1 Severity: grave In $ rgrep 'iframe.*/>' /usr/share/doc/imagemagick-6-common|wc -l 127 pages like file:///usr/share/doc/imagemagick-6-common/html/www/command-line-processing.html please replace

Bug#975752: view from aptitude

The following packages have unmet dependencies: android-libadb : Depends: android-libbase (= 1:8.1.0+r23-8) but 1:10.0.0+r36-1~stage1.1 is to be installed The following actions will resolve these dependencies: Keep the following packages at their current version: 1) android-libbase

Bug#970076: Update to work with systemd-resolved

Package: ppp Version: 2.4.7-2+4.1+deb10u1+b1 Severity: grave In https://github.com/paulusmack/ppp/issues/167 > "PM" == Paul Mackerras writes: PM> It seems like the debian packaging of pppd has not been updated to use PM> whatever the "correct" way to supply new DNS servers to PM>

Bug#968194: WNPP

OK I made a WNPP, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969021

Bug#968194: Upgrade to getmail6 which uses python3

Please use new upstream https://github.com/getmail6 release. It uses python3. Without upgrading, the getmail package is no longer installable on sid.

Bug#966696: emacs Segmentation fault

Regarding https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42676 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42677 etc. Well if this is an libx11-6 bug, then patching just emacs won't fix the (many more?) other packages this affects... > "c" == cufalo writes: c> Reported also for libx11-6 at

Bug#966696: emacs Segmentation fault

Package: libx11-6 Version: 2:1.6.10-1 Severity: critical $ emacs -Q Fatal error 11: Segmentation fault Backtrace: emacs[0x5111be] emacs[0x4f6ead] emacs[0x50f63e] emacs[0x50f86d] emacs[0x50f8e9] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14140)[0x7fb642ee6140] emacs[0x4d94b0] emacs[0x4d9897]

Bug#958450: 83 available upstream

Upstream is asking me to use version 83 when reporting bugs.

Bug#956159: Package depends on python-glade2 python-gtk2, which are no longer in sid

Package: wicd-gtk Severity: critical Version: 1.7.4+tb2-6 Package depends on python-glade2 python-gtk2, which are no longer in sid.

Bug#946995: No sound

Well I have given up on webm due to #951451 and will now just download in mp4 format.

Bug#946995: No sound

Do you have sound? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946995

Bug#947208: Need new version

As noted in #946995, sound is stripped.

Bug#946648: crashes within a few minutes

Package: chromium Version: 79.0.3945.79-1 Severity: grave Too bad. It was good while it lasted. But this new version today... within a few minutes... Received signal 11 SEGV_MAPERR #22 0x564ff676a0c6 #23 0x564ff3c983e5 ChromeMain #24 0x7f94706cfbbb __libc_start_main #25

Bug#935753: Not all hardware affected

Affected: product: 2nd Generation Core Processor Family Integrated Graphics Controller capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 Not affected: product: Wani [Radeon R5/R6/R7 Graphics]

Bug#931379: Arrow functions

http://es6-features.org/#ExpressionBodies

Bug#931379: => operator becomes = > thus creating syntax errors

X-Debbugs-Cc: fayl...@gmail.com Package: libjavascript-beautifier-perl Version: 0.25-1 Severity: grave File: /usr/bin/js_beautify js_beautify changes the => operator into = > thus creating syntax errors, making one's code unusable. fetch('https://example.com/').then(resp =

Bug#929887: Dependencies not tightened up

OK, # aptitude -t sid install qgis fixed it. That means there are dependency issues. Reproduce with # cat /etc/apt/sources.list deb ... experimental ... deb ... unstable ...

Bug#929887: /usr/lib/qgis/crssync: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot open shared object file: No such file or directory

Package: qgis-providers Version: 3.4.8+dfsg-1 Severity: critical Setting up qgis-providers (3.4.8+dfsg-1) ... /usr/lib/qgis/crssync: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot open shared object file: No such file or directory dpkg: error processing package

Bug#927913: Really bad

Causes loss of data, dropped sessions, hung-up conference calls, Other programs calling $BROWSER becomes equivalent to calling kill(1).

Bug#929100: decompressing archive member: lzma error: compressed data is corrupt

Package: gcc-9-base Version: 9.1.0-2 Severity: critical E: Invalid archive member header... E: Prior errors apply to /var/cache/apt/archives/gcc-9-base_9.1.0-2_amd64.deb E: Prior errors apply to /var/cache/apt/archives/cpp-9_9.1.0-2_amd64.deb E: Prior errors apply to

Bug#927913: As we see upstream has no such problem

As we see in the comments above upstream has no such problem. So I cannot file the bug upstream.

Bug#853016: here is more polite libpam0g dialog

See how this other package takes a more cautions approach: ──┤ Configuring libpam0g:amd64 ├─── │ Most services that use PAM need to be restarted to use modules built for this new version of libpam. Please review the following space-separated │ │ list of init.d scripts for services to be

Bug#922730: cannot browse anything

AG> Attached is a backtrace Glad you found the bug.

Bug#922730: cannot browse anything

I'm instead going to give up on 32 bit completely, and buy a new computer. So feel free to close this bug (if you confirm you can't reproduce it on 32 bit.)

Bug#853016: No such release notes

Well, a fix would be to take the cautions route of: If pidof nodm is found, that means they currently running it, so abandon all attempts to restart it. If the user is so smart that they want to restart it, they can do it themselves. (Equivalent of them rebooting the system themselves.)

Bug#853016: No such release notes

P.S., there are no such "release notes", $ dlocate --filename-only -L nodm|xargs grep -ic 'not upgrade' 2>&- and even if there were... don't you think it is silly if one cannot upgrade a package when using the package lest disaster. Does upgrading the kernel trigger reboot?

Bug#922730: cannot browse anything

https://www.google.com/search?q=gobject/gtype.c:4265:+type+id+'0'+is+invalid

Bug#922730: cannot browse anything

Here's the situation on i686. Be sure to test on i686, not amd64, where it works fine. libwebkit2gtk-4.0-37: Installed: 2.23.91-1 epiphany-browser: Installed: 3.31.91-2 $ mkdir /tmp/p; HOME=/tmp/p epiphany-browser You'll see it just shows it is loading about:overview, and it just loops

Bug#922730: i686 only

i686 only. Works fine on x86_64.

Bug#922730: cannot browse anything

Package: epiphany-browser Version: 3.31.91-2 Severity: grave $ mkdir /tmp/p $ HOME=/tmp/p epiphany /etc/motd ** (epiphany:11842): WARNING **: 06:53:40.412: Web process crashed (WebKitWebProcess:12106): GLib-GObject-WARNING **: 06:53:41.133: ../../../gobject/gtype.c:4265: type id '0' is invalid

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

Thanks but one still must forbid # aptitude search ~U iFA libilmbase23 iFA libopenexr23 if gimp is to start on experimental.

Bug#919036: libopenexr24 botched upload issue also affects libopenexr23 and libilmbase23

Package: libopenexr23 Version: 2.3.0-3 Severity: grave Please replace these. I had to Marking version 2.3.0-3 of package libopenexr23 as forbidden Marking version 2.3.0-3 of package libilmbase23 as forbidden and install libopenexr23=2.2.1-4 libilmbase23=2.2.1-2 else gimp won't start, etc.

Bug#918382: closed by Mathieu Malaterre (Bug#918382: fixed in openexr 2.3.0-5)

Does your fix help the aptitude forbid-version I have placed? The following packages will NOT be UPGRADED: libilmbase23{a} libopenexr23{a} (R: libopenexr22) I don't think so.

Bug#918382: broken upload

I had to do # aptitude purge gimp # aptitude -t sid install gimp # aptitude forbid-version libilmbase23 libopenexr23 libpoppler-glib8 Marking version 2.3.0-3 of package libilmbase23 as forbidden Marking version 2.3.0-3 of package libopenexr23 as forbidden Marking version 0.71.0-1 of package

Bug#918382: broken upload

As you can see in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918382 gimp is relying (Depending) on a broken upload. Perhaps you could make it Depend on libopenexr24 instead of libopenexr23.

Bug#918382: trying to overwrite '/usr/lib/x86_64-linux-gnu/libIlmImf-2_3.so.24.0.0', which is also in package libopenexr23:amd64 2.3.0-3

Package: libopenexr24 Version: 2.3.0-4 X-Debbugs-Cc: 917...@bugs.debian.org Severity: grave # aptitude install libopenexr24 Selecting previously unselected package libopenexr24:amd64. Unpacking libopenexr24:amd64 (2.3.0-4) ... dpkg: error processing archive

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

retitle 917130 libIlmImf-2_2.so.23: cannot open shared object file thanks On my other machine gimp starts, but is in an ugly grey color. Let's clean up these warnings first, # su - nobody -c "DISPLAY=$DISPLAY HOME=/tmp/ gimp"& GEGL-Message: 00:12:37.527: Module

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

Indeed with G_SLICE=debug-blocks it starts, but still says GEGL-Message: 15:02:47.435: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory GEGL-Message: 15:02:47.499: Module

Bug#917130: crashs at start

Package: gimp Version: 2.10.8-1 Severity: grave Gimp crashes at startup. GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc

Bug#913116: apt-cache show chromium|grep sand

Shouldn't the message also mention "or install a chromium-sandbox package if available."? Tell upstream.

Bug#913116: apt-cache show chromium|grep sand

chromium should Depend or at least Suggest chromium-sandbox.

Bug#913116: why stack trace?

Also a stack trace shouldn't really be produced as the message already says it all. No?

Bug#912695: apt-show-versions workarounds

Alas I found it isn't too simple to make a drop in replacement to get plain $ apt-show-versions output using dpkg, aptitude, etc. And I have embedded apt-show-versions into too many scripts. OK I submitted Bug#913039: Acknowledgement (add --no-cache) but that won't fix the cronjob error though...

Bug#912695: /etc/cron.daily/apt-show-versions errors

Also every day: > "A" == Anacron writes: A> /etc/cron.daily/apt-show-versions: A> Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux-gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. A> run-parts: /etc/cron.daily/apt-show-versions exited

Bug#912695: apt-show-versions perhaps shouldn't force caching in the first place

Maybe if the caching behavior was made non-default, then I wouldn't need su -c apt-show-versions nobody to avoid the error, and also no more daily errors from cron too.

Bug#912817: ALSA lib conf.c:4013:(snd_config_update_r) hooks failed, removing configuration

Package: alsa-utils Version: 1.1.7-1 Severity: grave $ alsamixer ALSA lib conf.c:3639:(config_file_open) cannot access file /etc/alsa/conf.d/10-rate-lav.conf ALSA lib conf.c:3559:(snd_config_hooks_call) function snd_config_hook_load returned error: No such file or directory ALSA lib

Bug#912709: Max. recursion depth with nested structures exceeded

Package: apt-show-versions Version: 0.22.8 Severity: grave # apt-show-versions Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux-gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. Works fine when non-root though. P.S., # apt-show-versions

Bug#910015: message wrong

It turns out this message is totally wrong. It should just say "check your device for a permissions confirmation screen." (And no the user is not always online to be able to access web explanations.)

Bug#910015: User is in the plugdev group

Package: adb Version: 1:8.1.0+r23-1~stage1.2 Severity: grave $ id uid=1000(jidanni) gid=1000(jidanni) groups=1000(jidanni),20(dialout),29(audio),46(plugdev),121(netdev),130(adb) $ adb shell error: insufficient permissions for device: user jidanni is not in the plugdev group See

Bug#900533: bug not fixed in v68

The browser won't let people switch back from 68 to 67 anyway, they would have to rip up their whole profile.

Bug#900533: bug not fixed in v68

reopen 900533 found 900533 68.0.3440.7-1 thanks Bug still there in 68.0.3440.7-1 $ chromium /var/tmp/Devo\ Big\ Mess-CvKP3_1PL5c.webm [9096:9096:0622/085518.510602:ERROR:sandbox_linux.cc(378)] InitializeSandbox() called with multiple threads in process gpu-process. Created new window in

Bug#901575: ln: '/usr/share/emacs/site-lisp/dictionaries-common/debian-ispell.el' and './debian-ispell.el' are the same file

Package: dictionaries-common Version: 1.27.5 Severity: grave Setting up dictionaries-common (1.27.5) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install dictionaries-common for emacs install/dictionaries-common: Byte-compiling for emacsen flavour

Bug#901185: OK downgraded bash

OK downgraded to bash4, restored /etc/exim4/update-exim4.conf.conf from backups, and was able to upgrade exim4.

Bug#901185: remove unlisted bash dependecy

Why use bash at all if e.g., $ checkbashisms /usr/sbin/update-exim4.conf.template could not find any possible bashisms in bash script /usr/sbin/update-exim4.conf.template means one can just use #!/bin/sh ?

Bug#901185: Checkbashisms

I also note /etc/exim4/update-exim4.conf.conf got overwritten without asking the user Y/N. I also note exim4-config contains #!/bin/bash scripts without Depends: bash. D> Be sure the package passes Checkbashisms! JN> Which package? Is there a particular bashism you noticed? All the shell

Bug#901185: Checkbashisms

Be sure the package passes Checkbashisms!

Bug#901185: me too

Oops. I mean just: Setting up exim4-config (4.91-5) ... /etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command not found

Bug#901185: me too

Setting up exim4-config (4.91-5) ... /var/lib/dpkg/info/exim4-config.postinst: line 330: export: `dc_eximconfig_configtype dc_other_hostnames dc_local_interfaces dc_readhost dc_relay_domains dc_minimaldns dc_relay_nets dc_smarthost CFILEMODE dc_use_split_config dc_hide_mailname

Bug#900984: fails with latest ssl

Package: w3m Version: 0.5.3-36+b1 Severity: grave No problem with wget. Problem with w3m. $ w3m -dump https://wiki.debconf.org SSL error: error:1414D172:SSL routines:tls12_check_peer_sigalg:wrong signature type w3m: Can't load https://wiki.debconf.org. $ wget https://wiki.debconf.org/

Bug#900982: fails with latest ssl

Package: libwww-perl Version: 6.33-1 Severity: grave File: /usr/bin/lwp-request No problem with wget. Problem with GET. $ GET https://wiki.debconf.org/ Can't connect to wiki.debconf.org:443 (SSL connect attempt failed error:1414D172:SSL routines:tls12_check_peer_sigalg:wrong signature type)

Bug#899338: WTFCrash

I can confirm that the problem doesn't occur on amd64 2.21.2-1, only i386. Do you have a i386 machine you can test /usr/lib/*-linux-gnu/webkit2gtk-4.0/MiniBrowser https://www.couchsurfing.com/dashboard on? I only use my i386 machine once a week and it is really underpowered for testing purposes.

Bug#899348: java.net.UnknownHostException: api.openstreetmap.org

Package: josm Version: 0.0.svn13710+dfsg-1 Severity: grave Cannot open files. Please upgrade. > "J" == JOSM writes: J> #16308: java.net.UnknownHostException: api.openstreetmap.org J> --+ J> Reporter: jidanni |

Bug#899338: workaround

Here's how I successfully was able to browse finally again: Remove the following packages: 1) libwebkit2gtk-4.0-37-gtk2 [2.21.2-1 (experimental, now)] Downgrade the following packages: 2) libwebkit2gtk-4.0-37 [2.21.2-1 (experimental, now) -> 2.20.2-1+b1 (unstable)]

Bug#899338: WTFCrash

Package: libjavascriptcoregtk-4.0-18 Version: 2.21.2-1 Severity: grave 1 0xb37f73a4 /usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(WTFCrash+0x14) [0xb37f73a4] 2 0xb340f325

Bug#898465: symbol lookup error: /usr/lib/libmapnik.so.3.0: undefined symbol

Package: viking Version: 1.6.2-3+b1 Severity: grave $ viking viking: symbol lookup error: /usr/lib/libmapnik.so.3.0: undefined symbol: _ZNK5boost16re_detail_10620031icu_regex_traits_implementation12do_transformEPKiS3_PKN6icu_578CollatorE -- System Information: Debian Release: buster/sid APT

Bug#890954: upload 65.0.3325.146-2

Please upload 65.0.3325.146-2 to experimental so we can test. Thanks.

Bug#890954: closed by Michael Gilbert <mgilb...@debian.org> (Bug#890954: fixed in chromium-browser 65.0.3325.146-2)

reopen 890954 found 65.0.3325.146-1 thanks Reproduce by: Start chromium. Try to install an extension.

Bug#891570: [Bug#891570: SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available

Here is all you need to reproduce it: $ mech-dump https://mbasic.facebook.com/ POST https://mbasic.facebook.com/login.php?refsrc=https%3A%2F%2Fmbasic.facebook.com%2F=100=8 Now upgrade libssl1.1:amd64 1.1.0g-2 1.1.1~~pre1-1 $ mech-dump https://mbasic.facebook.com/ Error GETing

Bug#891626: ModuleNotFoundError: No module named 'apt'

Package: reportbug Version: 7.1.9 Severity: grave $ reportbug Traceback (most recent call last): File "/usr/bin/reportbug", line 44, in from reportbug import utils File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 42, in import apt ModuleNotFoundError: No module named

Bug#891625: no ciphers available

X-debbugs-Cc: 891...@bugs.debian.org, k...@roeckx.be Package: liblwp-protocol-https-perl Version: 6.07-2 Severity: grave In Bug#891570 "KR" == Kurt Roeckx writes: KR> See https://www.openssl.org/blog/blog/2018/02/08/tlsv1.3/ about KR> the cipher suites. KR> Work is already on

Bug#891570: SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available

WWW::Mechanize: 500 Can't connect to mbasic.facebook.com:443...

Bug#891570: SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available

Package: libssl1.1 Version: 1.1.1~~pre1-1 Severity: grave SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available

Bug#886510: OK now I installed libelf-dev, but...

OK now I did, # aptitude install libelf-dev The following NEW packages will be installed: libelf-dev The following packages will be REMOVED: linux-headers-4.14.0-1-amd64{pu} linux-headers-4.14.0-1-common{pu} (D: linux-headers-4.14.0-1-amd64) And now the error is gone, # aptitude reinstall

Bug#882247:

As there is no United States version $ apt-cache search firefox|grep English firefox-l10n-en-gb - English (United Kingdom) language package for Firefox firefox-l10n-en-za - English (South Africa) language package for Firefox I'll just wait.

Bug#884823: trying to overwrite '/usr/bin/qtchooser', which is also in package qtchooser-bin 64-ga1b6736-1

Package: qtchooser Version: 64-ga1b6736-4 Severity: critical Unpacking qtchooser (64-ga1b6736-4) ... dpkg: error processing archive /tmp/apt-dpkg-install-qbTiWx/05-qtchooser_64-ga1b6736-4_amd64.deb (--unpack): trying to overwrite '/usr/bin/qtchooser', which is also in package qtchooser-bin

Bug#883996: Could not import PyQt4 on Linux systems

Package: electrum Version: 2.9.3-1 Severity: grave # aptitude install electrum $ electrum Error: Could not import PyQt4 on Linux systems, you may try 'sudo apt-get install python-qt4' Exception in thread Thread-9 (most likely raised during interpreter shutdown): Traceback (most recent call

Bug#882387: also kaput on amd64

Also kaput on amd64.

Bug#882247: can't even close it

Maintainer: can you even close it with CTRL+Q or CTRL+W?

Bug#882387: totally kaput on i386

Package: libwebkit2gtk-4.0-37 Version: 2.19.2-1 Severity: grave Cannot browse anything on i386. The browser just loops, eating CPU. Downgrading -ii libjavascriptcoregtk-4.0-18 2.19.2-1 +ii libjavascriptcoregtk-4.0-18 2.19.1-1 -ii libwebkit2gtk-4.0-37 2.19.2-1 +ii

Bug#882247:

Package: firefox Version: 58.0~b4-1 Severity: grave Firefox just starts in the corner of the screen with a . Unusable.

Bug#870363: not fixed by 868308

I am not trying to install sane-backends. I am just trying to do aptitude full-upgrade without any error messages. This is the only package on the entire Debian that is making such error messages.

Bug#870363: not fixed by 868308

Please tell me what steps will make the error messages go away.

Bug#870363: not fixed by 868308

Note all these problems are still currently present: The following packages have unmet dependencies: libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed libsane : Depends: libsane-common (= 1.0.25-4.1) but 1.0.27-1~experimental2 is to be installed

Bug#875800: double free or corruption (!prev)

The reason you are getting 401s is that you have an invalid oauth_client_key= oauth_client_secret= pair in .flickcurl.conf . In order to reproduce the bug you need to repeat these steps: 1. Visit http://www.flickr.com/services/api/keys/ to get an and . 2. Create

Bug#875800: double free or corruption (!prev)

And no, the same problem occurs on amd64, and with libc6 2.24-17. $ flickcurl oauth.create *** Error in `flickcurl': double free or corruption (fasttop): 0x55b02e930c40 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f1d1de88bfb]

Bug#875800: 5 steps

Starting clean, how far do you get with the five steps listed when using just $ flickcurl ? Thanks.

Bug#875800: double free or corruption (!prev)

Package: flickcurl-utils Version: 1.26-2 Severity: grave File: /usr/bin/flickcurl $ flickcurl oauth.create *** Error in `flickcurl': double free or corruption (!prev): 0x0176b510 *** === Backtrace: = /lib/i386-linux-gnu/libc.so.6(+0x698aa)[0xb72e18aa]

Bug#875425: Unknown symbol init_mm (err 0)

Package: nvidia-legacy-304xx-driver Version: 304.135-4 Severity: grave Please install the changes like https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1711758 Else 4.12 kernel is unusable.

Bug#873275: always segfaults at start due to QSslSocket

Glad to have found the bug for you early. I only use qgis offline, so was dismayed that I couldn't even start it even if never planning to use SSL over the network. I mean even researchers in some offline arctic lab will find the copy of qgis they brought with them is unusable even without ever

Bug#873275: always segfaults at start due to QSslSocket

Package: qgis Version: 2.14.18+dfsg-1 Severity: grave # apt-get install qgis $ qgis Warning: QSslSocket: cannot resolve CRYPTO_num_locks Warning: QSslSocket: cannot resolve CRYPTO_set_id_callback Warning: QSslSocket: cannot resolve CRYPTO_set_locking_callback Warning: QSslSocket: cannot resolve

Bug#872532: w3m bricked: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch

X-Debbugs-Cc: dic...@invisible-island.net, yama...@jpl.org Package: w3m Version: 0.5.3-34 Severity: grave With the latest upgrade of its dependencies, w3m is now 100 unusable on Debian. $ w3m w3m: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch We read in

Bug#867737: Do not use this package. It will lock your screen.

Package: arora Version: 0.11.0+qt5+git2014-04-06-1 Severity: grave All I did was $ arora then after it finished rendering its initial screen, I hit CTRL+Q and CTRL+W or maybe the other way around. Next thing you know my entire screen was locked up. The clock in the corner of icewm stopped. I

  1   2   3   >