control: severity -1 important
control: tags -1 moreinfo unreproducible
Am 11.01.2015 um 21:40 schrieb Chris Carr:
> On 11/01/2015 20:02, Michael Biebl wrote:
>> Am 11.01.2015 um 20:54 schrieb Chris Carr:
>>> I still cannot start gdm3:
>>>
>>> chrisc@tony:~$ sudo invoke-rc.d gdm3 start
>>> []
Processing control commands:
> severity -1 important
Bug #775065 [systemd] dpkg --configure -a results in "Hangup" after first
package
Severity set to 'important' from 'serious'
> tags -1 moreinfo unreproducible
Bug #775065 [systemd] dpkg --configure -a results in "Hangup" after first
package
Ad
Hi,
Just wondering what hal is doing here, given this is for Jessie.
[ See the journalctl-alb.txt ]
Could this be part of the problem?
Regards,
Peter
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://list
Am 11.01.2015 um 21:40 schrieb Chris Carr:
> On 11/01/2015 20:02, Michael Biebl wrote:
>> Is the dbus package installed? What's the output of "systemctl status
>> dbus.socket dbus.service"?
> Failed to get D-Bus connection: Unknown error -1
>> You might consider attaching the full output of the sy
On 11/01/2015 20:02, Michael Biebl wrote:
Am 11.01.2015 um 20:54 schrieb Chris Carr:
I still cannot start gdm3:
chrisc@tony:~$ sudo invoke-rc.d gdm3 start
[] Starting GNOME Display Manager: gdm3[ 1094.663256]
systemd-logind[9907]: Failed to enable subscription: Launch helper
exited with unk
[dropping plymouth from CC]
Am 11.01.2015 um 18:11 schrieb Guillem Jover:
> On Sun, 2015-01-11 at 09:03:34 +, Chris Carr wrote:
>> On 11/01/2015 05:13, Guillem Jover wrote:
>>> Please run «dpkg -D7 --configure -a 2>&1 | tee dpkg.log», and attach
>>> the output. We can check from there
>>
Am 11.01.2015 um 20:54 schrieb Chris Carr:
> On 11/01/2015 19:25, Michael Biebl wrote:
>> Is your system fully booted or did systemd drop you into emergency
>> shell? How are you logged into your system?
> The default boot drops me into an emergency shell. It was not fully booted.
Now that the sys
On 11/01/2015 19:25, Michael Biebl wrote:
Is your system fully booted or did systemd drop you into emergency
shell? How are you logged into your system?
The default boot drops me into an emergency shell. It was not fully booted.
Assuming, the sysvinit is still installed (which should be the ca
Am 11.01.2015 um 18:50 schrieb Chris Carr:
> On 11/01/2015 17:11, Guillem Jover wrote:
>> Control: reassign -1 systemd
>> Control: severity -1 serious
>>
>> Hi!
>>
>> On Sun, 2015-01-11 at 09:03:34 +, Chris Carr wrote:
>>> On 11/01/2015 05:13, Guillem Jover wrote:
Please run «dpkg -D7
On 11/01/2015 17:11, Guillem Jover wrote:
Control: reassign -1 systemd
Control: severity -1 serious
Hi!
On Sun, 2015-01-11 at 09:03:34 +, Chris Carr wrote:
On 11/01/2015 05:13, Guillem Jover wrote:
Please run «dpkg -D7 --configure -a 2>&1 | tee dpkg.log», and attach
the output. We can
Processing control commands:
> reassign -1 systemd
Bug #775065 [dpkg] dpkg --configure -a results in "Hangup" after first package
Bug reassigned from package 'dpkg' to 'systemd'.
No longer marked as found in versions dpkg/1.17.23.
Ignoring request to alter fixed versions of bug #775065 to the same
Control: reassign -1 systemd
Control: severity -1 serious
Hi!
On Sun, 2015-01-11 at 09:03:34 +, Chris Carr wrote:
> On 11/01/2015 05:13, Guillem Jover wrote:
> >Please run «dpkg -D7 --configure -a 2>&1 | tee dpkg.log», and attach
> >the output. We can check from there
>
> It is attached,
12 matches
Mail list logo
