Hello,
I’m experiencing a similar issue after I upgraded my system.
Installing Thunderbird from the experimental repository did partially
solve the problem: I can open attached files (tried with a pdf file
(evince)).
However, I’m still unable to open links.
All packages are up to date.
$
Dear maintainer,
The dependencies algorithm has changed from npm 2 and 3 <
https://docs.npmjs.com/how-npm-works/npm3> and the npm 1 registry is sort
of officially broken, as mentioned here: <
https://github.com/npm/npm/blob/1.4.x/CHANGELOG.md>.
This package is totally out of date, merely
Hello Pascal,
You should be able to use systemd just once from your bootloader.
Here is a good start:
https://wiki.debian.org/systemd
Thank you very much Laurent.
I will take a further look at systemd (not yet tested, btw).
Benjamin.
Le 13/05/2014 07:47, Pascal Obry a écrit :
Laurent,
I
Laurent,
I confirm. As expected, using systemd as init system (PID1) works fine
with last package version of gdm3.
Thank you,
Benjamin.
May 12 10:57:07 * dbus[2026]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.5 (uid=0 pid=2179 comm=/usr/sbin/gdm3 )
Hello,
I tested the fglrx-driver package version 14.4-2 this morning.
There is no more segmentation fault in the Xorg log.
However, there is a new issue blocking GDM3 from starting (same outcome:
black screen at startup). It seems related to the Clutter bug reported
recently (see attachments).
Hello,
I am experiencing the same issue. Please see xorg.log attached and
following gdm3 logs.
Package: fglrx-driver
Version: 1:14.4-2
Package: gdm3
Version: 3.8.4-7
Package: libclutter-1.0-0
Version: 1.18.2-1
Package: libclutter-gtk-1.0.0
Version: 1.5.2-2
# cat
:08:36 +0200,
Laurent Bigonville bi...@debian.org a écrit :
Le Wed, 07 May 2014 17:33:01 +0200,
Benjamin Menant benjamin.men...@gmail.com a écrit :
Well, I am not sure… It’s more or less a default Jessie
installation. I hope those following data will help. Please let me
know.
[...]
So
Thank you for your time and efforts.
I tried adding this debug parameter into `/etc/pam.d/common-session`:
session optionalpam_systemd.so debug=yes
Then, I flushed the auth.log and rebooted the computer (with v3.8.4-7).
Please see the attached file for results.
Also, when a Gnome
Oups, erratum:
Whith gmd3 v3.8.4-7, before I submit the login form, I get the two
directories (mine and Degian-gdm’s one) under `/run/user/`… until gdm3
tries to open the Gnome session. Then, I get this error notification
from the VC:
[ 178.844254] systemd-logind[2370]: Removed session 1.
And
It did not work… And I had to reinstall those packages (unless the
previous gdm3 neither worked).
Another idea?
I am thinking to try another DM (like, say, LightDM or SLiM). Will see
if the problem still occurs or not. I will let you know.
Thank you,
Benjamin.
Le 08/05/2014 16:14, Laurent
Package: gdm3
Version: 3.8.4-6
Severity: important
Dear Maintainer,
* What led up to the situation?
I upgraded gdm3 package (and its dependencies) version 3.8.4-6 to 3.8.4-7.
* What was the outcome of this action?
Then, the tomorrow, when I startup the computer, I was unable to login:
Hello,
Currently, the version 0.105 of policykit-1 is installed.
I will try to install the latest version from the experimental repository.
# aptitude show policykit-1
Paquet : policykit-1
État: installé
Automatiquement installé: oui
Multiarchitecture : étranger
Version : 0.105-5
[…]
# aptitude
Well, I am not sure… It’s more or less a default Jessie installation.
I hope those following data will help. Please let me know.
The PID #1 is /sbin/init (which is not a symlink)
# cat /proc/cmdline
\boot\vmlinuz-3.14-1-amd64 ro root=UUID=***
initrd=boot\initrd.img-3.14-1-amd64
# aptitude show
Dear Maintainer,
Just to say, upgrading fglrx-driver and its dependencies to
1:14.4~rc1.0.apr17-1 did not solve the issue (see xorg.log attachment
below).
Thank you for your time and effort,
Benjamin.
X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build
Dear Maintainer,
I am experiencing the same issue on my old desktop computer, as
described by Florian, expect that the virtual consoles remain available.
I tried to purge, install (from sid), aticonfig --initial the driver’s
packages without any success : black screen on boot after a
15 matches
Mail list logo
