Your message dated Mon, 1 Jan 2018 22:44:57 +0100
with message-id <[email protected]>
and subject line Re: Bug#821927: basename: missing operand
has caused the Debian Bug report #821927,
regarding basename: missing operand
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.)
--
821927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821927
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.20.1-1
Severity: important
Dear Maintainer,
I did an 'apt-get dist-upgrade' and end with this:
# LANG=C apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up gdm3 (3.20.1-1) ...
basename: missing operand
Try 'basename --help' for more information.
dpkg: error processing package gdm3 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
gdm3
Seems to be the same error reported in bug #579103 (2010 - squeeze/sid)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579103
regards,
Herbert
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gdm3 depends on:
ii accountsservice 0.6.40-3
ii adduser 3.114
ii dconf-cli 0.26.0-1
ii dconf-gsettings-backend 0.26.0-1
ii debconf [debconf-2.0] 1.5.59
ii gir1.2-gdm-1.0 3.20.1-1
ii gnome-session [x-session-manager] 3.20.1-1
ii gnome-session-bin 3.20.1-1
ii gnome-settings-daemon 3.20.1-1
ii gnome-shell 3.20.1-1
ii gnome-terminal [x-terminal-emulator] 3.20.1-2
ii gsettings-desktop-schemas 3.20.0-3
ii libaccountsservice0 0.6.40-3
ii libaudit1 1:2.4.5-1+b1
ii libc6 2.22-7
ii libcanberra-gtk3-0 0.30-3
ii libcanberra0 0.30-3
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libgdm1 3.20.1-1
ii libglib2.0-0 2.48.0-1
ii libglib2.0-bin 2.48.0-1
ii libgtk-3-0 3.20.3-1
ii libpam-modules 1.1.8-3.2
ii libpam-runtime 1.1.8-3.2
ii libpam-systemd 229-4
ii libpam0g 1.1.8-3.2
ii librsvg2-common 2.40.15-1
ii libselinux1 2.4-3+b1
ii libsystemd0 229-4
ii libwrap0 7.6.q-25
ii libx11-6 2:1.6.3-1
ii libxau6 1:1.0.8-1
ii libxdmcp6 1:1.1.2-1.1
ii lsb-base 9.20160110
ii metacity [x-window-manager] 1:3.18.3-1
ii mutter [x-window-manager] 3.20.1-1
ii policykit-1 0.105-15
ii ucf 3.0036
ii x11-common 1:7.7+14
ii x11-xserver-utils 7.7+7
ii xterm [x-terminal-emulator] 324-1
Versions of packages gdm3 recommends:
ii at-spi2-core 2.18.3-4
ii desktop-base 8.0.2
ii x11-xkb-utils 7.7+2
ii xserver-xephyr 2:1.18.3-1
ii xserver-xorg 1:7.7+14
ii zenity 3.20.0-1
Versions of packages gdm3 suggests:
ii gnome-orca 3.20.0-1
ii libpam-gnome-keyring 3.20.0-1
-- debconf information:
* shared/default-x-display-manager: gdm3
gdm3/daemon_name: /usr/sbin/gdm3
--- End Message ---
--- Begin Message ---
Version: 3.26.1-3
On Thu, 21 Apr 2016 00:45:24 +0200 Michael Biebl <[email protected]> wrote:
> Am 21.04.2016 um 00:26 schrieb Herbert Fortes (hpfn):
> > On Wed, 20 Apr 2016 20:13:05 +0200
> > Michael Biebl <[email protected]> wrote:
> >
> >> Control: tags -1 moreinfo
> >
> >> Am 20.04.2016 um 16:26 schrieb Herbert Parentes Fortes Neto:
> >>> I did an 'apt-get dist-upgrade' and end with this:
> >>>
> >>> # LANG=C apt-get dist-upgrade
> >>> Reading package lists... Done
> >>> Building dependency tree
> >>> Reading state information... Done
> >>> Calculating upgrade... Done
> >>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> >>> 1 not fully installed or removed.
> >>> After this operation, 0 B of additional disk space will be used.
> >>> Do you want to continue? [Y/n]
> >>> Setting up gdm3 (3.20.1-1) ...
> >>> basename: missing operand
> >>> Try 'basename --help' for more information.
> >>> dpkg: error processing package gdm3 (--configure):
> >>> subprocess installed post-installation script returned error exit status
> >>> 1
> >>> Errors were encountered while processing:
> >>> gdm3
> >>>
> >
> >> Do you have a /etc/X11/default-display-manager file? If so, what does it
> >> contain?
> >
> >
> > Ok. The file was empty. It was empty because the VM (KVM)
> > does not complete the boot with gdm3.
>
> A better way to disable boot-to-graphical-login is to use
>
> systemctl set-default multi-user.target
>
> > After put '/usr/sbin/gdm3' on it, the 'dist-upgrade' ran
> > without errors. Version 3.20.1-1 is installed. But it does
> > not boot after that. It freezes at: 'Booting from Hard Disk'.
>
> That sounds like a problem related to your graphics drivers.
>
> > Before the 'dist-upgrade', with the '/etc/X11/default-display-manager'
> > empty, it was possible to boot and use the console(tty1) login.
> > Then 'startx'.
>
> I assume we should handle an empty /etc/X11/default-display-manager more
> gracefully.
>
> bigon, thoughts?
>
> Related to that, I think we should start removing the
> /etc/X11/default-display-manager from the systemd .service files.
> All display managers should implement the
> /etc/systemd/display-manager.service interface nowadays.
> We still need /etc/X11/default-display-manager for the sysv init script
> though.
>
This check was removed from the systemd service file. So closing this
bug report.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
