Your message dated Wed, 15 Oct 2014 21:21:57 -0400 with message-id <CANTw=MMsNj6WYQYq6FmL+nXsCgAS2agP_SPcuvM1J=6hvu_...@mail.gmail.com> and subject line Re: [Pkg-chromium-maint] Bug#765537: chromium: Silent change: java plugin no longer works has caused the Debian Bug report #765537, regarding chromium: Silent change: java plugin no longer works to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 765537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765537 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: chromium Version: 38.0.2125.101-2 Severity: important Tags: upstream Dear Maintainer, After a routine apt-get upgrade, chromium java support stopped. There was no changelog entry to suggest this would happen -- apparently upstream has removed support for the NPAPI that the java plugin uses. I'd appreciate at least a changelog entry, or a warning or something, so that I could avoid upgrading chromium beyond version 37. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 armhf Kernel: Linux 3.16.0 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages chromium depends on: ii libasound2 1.0.28-1 ii libc6 2.19-11 ii libcairo2 1.12.16-5 ii libcap2 1:2.24-6 ii libcups2 1.7.5-4 ii libdbus-1-3 1.8.8-2 ii libexpat1 2.1.0-6 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2 ii libglib2.0-0 2.42.0-2 ii libgnome-keyring0 3.12.0-1 ii libgtk2.0-0 2.24.25-1 ii libharfbuzz0b 0.9.35-1 ii libjpeg8 8d1-2 ii libnspr4 2:4.10.7-1 ii libnspr4-0d 2:4.10.7-1 ii libnss3 2:3.17.1-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpci3 1:3.2.1-3 ii libspeechd2 0.8-6 ii libspeex1 1.2~rc1.2-1 ii libsrtp0 1.4.5~20130609~dfsg-1.1 ii libstdc++6 4.9.1-16 ii libudev1 215-5+b1 ii libx11-6 2:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1 ii libxdamage1 1:1.1.4-2 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2 ii libxi6 2:1.7.4-1 ii libxml2 2.9.1+dfsg1-4 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxslt1.1 1.1.28-2+b1 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-7.1 chromium recommends no packages. Versions of packages chromium suggests: ii chromium-inspector 38.0.2125.101-2 pn chromium-l10n <none> -- Configuration Files: /etc/chromium/default changed: CHROMIUM_FLAGS="--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" -- no debconf information
--- End Message ---
--- Begin Message ---control: forwarded -1 http://crbug.com/363053 On Wed, Oct 15, 2014 at 8:00 PM, Peter Chubb wrote: > After a routine apt-get upgrade, chromium java support stopped. > There was no changelog entry to suggest this would happen -- > apparently upstream has removed support for the NPAPI that the > java plugin uses. Unfortunately upstream decided this. A fix depends on someone writing a PPAPI interface for the java plugin. Best wishes, Mike
--- End Message ---
