Your message dated Wed, 12 Aug 2015 19:58:28 -0400
with message-id
<CANTw=MM=L_3ZHPSDBwxn7=hcois-2dejret962ngz2uyrd5...@mail.gmail.com>
and subject line Re: Bug#793761: chromium: freezes at startup in xfce4
has caused the Debian Bug report #793761,
regarding chromium: freezes at startup in xfce4
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 ow...@bugs.debian.org
immediately.)
--
793761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 44.0.2403.89-1
Severity: normal
Dear Maintainer,
When launching chromium in my xfce4 environment:
user@debian:~$ chromium
[14210:14210:0727/101720:ERROR:background_mode_manager_aura.cc(14)] Not
implemented reached in virtual void
BackgroundModeManager::EnableLaunchOnStartup(bool)
[14210:14332:0727/101731:ERROR:get_updates_processor.cc(243)]
PostClientToServerMessage() failed during GetUpdates
Then, the chromium window freezes with no data inside (just the xfce4 frame).
This seems to be a regression, given previous testing version worked fine.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii libasound2 1.0.29-1
ii libatk1.0-0 2.16.0-2
ii libc6 2.19-19
ii libcairo2 1.14.2-2
ii libcups2 2.0.3-6
ii libdbus-1-3 1.8.18-1
ii libexpat1 2.1.0-6+b3
ii libfontconfig1 2.11.0-6.3
ii libfreetype6 2.5.2-4
ii libgdk-pixbuf2.0-0 2.31.4-2
ii libglib2.0-0 2.44.1-1.1
ii libgnome-keyring0 3.12.0-1+b1
ii libgtk2.0-0 2.24.28-1
ii libharfbuzz0b 0.9.41-1
ii libjpeg62-turbo 1:1.4.0-7
ii libnspr4 2:4.10.8-2
ii libnss3 2:3.19.2-1
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
ii libpci3 1:3.2.1-3
ii libspeechd2 0.8-7
ii libspeex1 1.2~rc1.2-1
ii libsrtp0 1.4.5~20130609~dfsg-1.1
ii libstdc++6 5.1.1-14
ii libx11-6 2:1.6.3-1
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1+b1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.1-2+b2
ii libxi6 2:1.7.4-1+b2
ii libxml2 2.9.1+dfsg1-5
ii libxrandr2 2:1.4.2-1+b1
ii libxrender1 1:0.9.8-1+b1
ii libxslt1.1 1.1.28-2+b2
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1+b1
ii x11-utils 7.7+3
ii xdg-utils 1.1.0~rc1+git20111210-7.4
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Aug 11, 2015 at 8:25 AM, Arturo Borrero Gonzalez wrote:
> Ok thanks. Anyway, the issue seems OK now.
>
> Feel free to close the bug :-)
--- End Message ---
