Bug#610372: marked as done (chromium-browser: Failed to open debug file $HOME/tmp/mozdebug)
Your message dated Tue, 14 Sep 2021 19:06:28 +0000
with message-id <[🔎] E1mQDlE-0003fn-Jd@fasolo.debian.org>
and subject line Bug#987539: Removed package(s) from unstable
has caused the Debian Bug report #610372,
regarding chromium-browser: Failed to open debug file $HOME/tmp/mozdebug
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 owner@bugs.debian.org
immediately.)
--
610372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610372
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: chromium-browser: Failed to open debug file $HOME/tmp/mozdebug
- From: "Marc J. Driftmeyer" <mjd@reanimality.com>
- Date: Mon, 17 Jan 2011 18:19:05 -0800
- Message-id: <20110118021905.16082.35864.reportbug@localhost.localdomain>
Package: chromium-browser
Version: 9.0.597.45~r70550-1
Severity: normal
chromium-browser is attempting to attach a debug session [mozdebug] to output all it's log information
under a tmp direction from the user home directory. By creating $HOME/tmp/mozdebug under my username account
the application responds to all expected transactions and page rendering.
This information should be under /tmp/mozdebug in the filesystem, should it not and not from $HOME/tmp/mozdebug?
If I purge that $HOME/tmp/mozdebug file the application is caught in a permanent wait state.
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages chromium-browser depends on:
ii chromium-browser-ins 9.0.597.45~r70550-1 page inspector for the chromium-br
ii libasound2 1.0.23-2.1 shared library for ALSA applicatio
ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co
ii libc6 2.11.2-8 Embedded GNU C Library: Shared lib
ii libcairo2 1.10.2-1 The Cairo 2D vector graphics libra
ii libcups2 1.4.5-2 Common UNIX Printing System(tm) -
ii libdbus-1-3 1.4.1-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst
ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification
ii libexpat1 2.0.1-7 XML parsing C library - runtime li
ii libfontconfig1 2.8.0-2.1 generic font configuration library
ii libfreetype6 2.4.2-2.1 FreeType 2 font engine, shared lib
ii libgcc1 1:4.4.5-10 GCC support library
ii libgconf2-4 2.32.1-2 GNOME configuration database syste
ii libgcrypt11 1.4.6-3 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.27.91-1 The GLib library of C routines
ii libgtk2.0-0 2.23.90-1 The GTK+ graphical user interface
ii libicu44 4.4.2-2 International Components for Unico
ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG
ii libnspr4-0d 4.8.7-1 NetScape Portable Runtime Library
ii libnss3-1d 3.12.9-1 Network Security Service libraries
ii libpango1.0-0 1.28.3-4 Layout and rendering of internatio
ii libpng12-0 1.2.44-1 PNG library - runtime
ii libspeex1 1.2~rc1-1 The Speex codec runtime library
ii libstdc++6 4.4.5-10 The GNU Standard C++ Library v3
ii libvpx0 0.9.5-1 VP8 video codec (shared library)
ii libx11-6 2:1.4.1-1 X11 client-side library
ii libxdamage1 1:1.1.3-1 X11 damaged region extension libra
ii libxext6 2:1.2.0-1 X11 miscellaneous extension librar
ii libxml2 2.7.8.dfsg-2 GNOME XML library
ii libxrender1 1:0.9.6-1 X Rendering Extension client libra
ii libxslt1.1 1.1.26-6 XSLT 1.0 processing library - runt
ii libxss1 1:1.2.1-1 X11 Screen Saver extension library
ii libxtst6 2:1.2.0-1 X11 Testing -- Record extension li
ii xdg-utils 1.1.0~rc1-1 desktop integration utilities from
ii zlib1g 1:1.2.5.dfsg-1 compression library - runtime
chromium-browser recommends no packages.
Versions of packages chromium-browser suggests:
ii chromium-browser-l10 9.0.597.45~r70550-1 chromium-browser language packages
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 189206-done@bugs.debian.org,453956-done@bugs.debian.org,519832-done@bugs.debian.org,570989-done@bugs.debian.org,603604-done@bugs.debian.org,609215-done@bugs.debian.org,610372-done@bugs.debian.org,614003-done@bugs.debian.org,619897-done@bugs.debian.org,631431-done@bugs.debian.org,637841-done@bugs.debian.org,659868-done@bugs.debian.org,668727-done@bugs.debian.org,680708-done@bugs.debian.org,692782-done@bugs.debian.org,752759-done@bugs.debian.org,818638-done@bugs.debian.org,841192-done@bugs.debian.org,865351-done@bugs.debian.org,907767-done@bugs.debian.org,710999-done@bugs.debian.org,
- Cc: mozplugger@packages.debian.org
- Subject: Bug#987539: Removed package(s) from unstable
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Tue, 14 Sep 2021 19:06:28 +0000
- Message-id: <[🔎] E1mQDlE-0003fn-Jd@fasolo.debian.org>
Version: 1.14.5-2+rm
Dear submitter,
as the package mozplugger has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/987539
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)
--- End Message ---
Reply to: