Bug#863513: [Reportbug-maint] Bug#863513: reportbug: No GUI; only '--ui=text'
On Saturday, May 27, 2017 7:33:56 PM -05 you wrote: > On Sat, May 27, 2017 at 5:00 PM, Diego A. Casas Toro > > <daca...@uninorte.edu.co> wrote: > > I tried to start reportbug for the first time in KDE Plasma 5, but it did > > not start. > did you install the additional dependencies as specified by the > documentation? > > ``` > How to Use New GTK+ User Interface > == > > If you tried to set the new GTK+ UI (named in reportbug as gtk2 ui) > and it fails to start (falling back to text mode, hopefully), chances > are that you are missing some of the packages listed as Suggests, in > particular: > > - python3-gi > - python3-gi-cairo > - gir1.2-gtk-3.0 > - gir1.2-vte-2.91 > - python3-gtkspellcheck > > If after installing both of them still GTK+ UI doesn't show up, please > file a report (in text ui :) ). > ``` > > from /usr/share/doc/reportbug/README.Users.gz I did not install the suggests of reportbug. After 2 years using GTK-based desktop environments (GNOME, Mate, Xfce), I thought the GTK UI was the “default” UI; I never had to install “additional dependencies” in those DEs. I just installed python3-gi-cairo, gir1.2-vte-2.91 and python3-gtkspellcheck, and it works. Now the default UI is GTK. So the bug is actually different: why does the reportbug package create a menu entry for the gtk2 UI if it's not the default UI? This is the command of the '.desktop' file: reportbug --exit-prompt --ui gtk2 It means the gtk2 UI is supposed to be the default, and it doesn't make sense to create a menu entry for program that doesn’t start how it is supposed to. To conclude, GTK UI should be default for people using a DE in order to be user-friendly (maybe include it in the task-* packages). Or if the gtk2 UI is not supposed to be the default, the menu entry should not be created during install. -- Diego A. Casas Toro Est. de ingeniería civil C. e.: daca...@uninorte.edu.co -- *Este correo no representa opinión o consentimiento oficial de la Universidad del Norte, por lo que esta no adquiere ninguna responsabilidad por su contenido, salvo en el caso de funcionarios en ejercicio de atribuciones reglamentarias. Puede provenir de una cuenta ofrecida a funcionarios o estudiantes, como parte del ejercicio educativo, evento en el cual tanto el mensaje como sus anexos son estrictamente confidenciales. Ha sido analizado con software antivirus; no obstante, no se garantiza que sea seguro o no contenga errores o virus, por lo que la Universidad del Norte no se hace responsable de su transmisión.*
Bug#863513: reportbug: No GUI; only '--ui=text'
Package: reportbug Version: 7.1.6 Severity: important Dear Maintainer, I tried to start reportbug for the first time in KDE Plasma 5, but it did not start. I thought it was a problem with the '.desktop' file asociated with the menu entry. Then I realized that reportbug was starting in the background, without gtk2 GUI. I tried to start reportbug from Konsole using '--ui=gtk2', but it starts in text mode and shows 'Ignored bogus setting for --ui: gtk'. I don't understand why reportbug shows "Ignored bogus setting" when the man entry says "Valid options are text, urwid, and gtk2". I realized that the autocompletion give these options: "gnome newt text", but gnome and newt cause the same output: 'Ignored bogus setting for --ui'. The bug is the same with '--interface' and '-u'. I updated and reinstalled reportbug, but I couldn't solve the problem. Actually, I'm reporting this bug from command line. Even if the man entry is wrong, and gnome replaces gtk2 option, reportbug should start using GUI. So, to conclude, there are two problems: the man entry is incorrect, and the reportbug program has a missing GUI. -- Package-specific info: ** Environment settings: INTERFACE="text" ** /home/dact/.reportbugrc: reportbug_version "7.1.6" mode standard ui text email "daca...@uninorte.edu.co" no-cc header "X-Debbugs-CC: daca...@uninorte.edu.co" smtphost reportbug.debian.org -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt1.4.4 ii python3-reportbug 7.1.6 pn python3:any reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate pn emacs23-bin-common | emacs24-bin-common ii file 1:5.30-1 ii gir1.2-gtk-3.0 3.22.11-1 pn gir1.2-vte-2.91 ii gnupg2.1.18-6 pn postfix | exim4 | mail-transport-agent ii python3-gi 3.22.0-2 pn python3-gi-cairo pn python3-gtkspellcheck pn python3-urwid ii xdg-utils1.1.1-1 Versions of packages python3-reportbug depends on: ii apt1.4.4 ii file 1:5.30-1 ii python3-debian 0.1.30 ii python3-debianbts 2.6.1 ii python3-requests 2.12.4-1 pn python3:any python3-reportbug suggests no packages. -- no debconf information
Bug#863500: sddm: SDDM doesn't allow empty password field for passwordless account
Package: sddm Version: 0.14.0-4 Severity: normal Dear Maintainer, I did 'passwd -d' and activated autologin. It start seamlessly, but when I try to logout and relogin using i3-wm, SDDM ask for password. Supposedly, 'passwd -d' made the password empty, but SDDM doesn't allow empty password field; it shows "Failed Login". Currently, I'm unable to relogin after logout, so I can't use a different DE. The only workaround to relogin is start tty1 as root and do 'systemctl restart sddm.service'. This make SDDM to start in autologin mode, and I get back to Plasma without typing my password. I think SDDM should allow me to login without asking password, or at least allow empty password field. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sddm depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.61 ii libc6 2.24-10 ii libgcc1 1:6.3.0-18 ii libpam0g1.1.8-3.5 ii libqt5core5a5.7.1+dfsg-3+b1 ii libqt5dbus5 5.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5network5 5.7.1+dfsg-3+b1 ii libqt5qml5 5.7.1-2+b2 ii libqt5quick55.7.1-2+b2 ii libstdc++6 6.3.0-18 ii libsystemd0 232-23 ii libxcb-xkb1 1.12-1 ii libxcb1 1.12-1 ii qml-module-qtquick2 5.7.1-2+b2 ii x11-common 1:7.7+19 ii xserver-xorg [xserver] 1:7.7+19 Versions of packages sddm recommends: ii libpam-systemd 232-23 ii sddm-theme-breeze [sddm-theme] 4:5.8.6-2 ii sddm-theme-debian-breeze [sddm-theme] 4:5.8.6-2 ii sddm-theme-debian-maui [sddm-theme]0.14.0-4 Versions of packages sddm suggests: ii libpam-kwallet5 5.8.4-1 -- debconf information: sddm/daemon_name: /usr/bin/sddm * shared/default-x-display-manager: sddm
