[Bug 1853717] Re: Bug Ubiquity Install Ubuntu 19.10
It is a Toshiba Satellite C850-D - 102 I also got a report of Ubiquity install.py crash When upgrade from 19.04 failed, at restart I still had access to grub menu and Ubuntu Recovery (message of End Kernel panic). After the fresh reinstall from Live CD failed (I got graphical warning and made this report) I have no more grub : error : file '/boot/grub/i386-pc/normal.mod' not found Entering rescue mode... grub rescue> There is a windows 7 version installed on the unique SSD (sda), and live CD of Ubuntu 19.10, as well as previously Ubuntu 19.04 in dual boot with W7, worked fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853717 Title: Bug Ubiquity Install Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1853717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853717] [NEW] Bug Ubiquity Install Ubuntu 19.10
Public bug reported: During a fresh install of Ubuntu 19.10 Desktop on a Toshiba Satellite laptop (AMD® E1-1200 apu with radeon(tm) hd graphics × 2), install fails. Ubuntu 19.04 worked fine, upgrade failed : end Kernel panic, not syncing : VFS Unable to mount root fs on unknown block A fresh reinstall with partitions formatting on LiveDVD fails, too... ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 Date: Sat Nov 23 22:45:13 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853717 Title: Bug Ubiquity Install Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1853717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842880] Re: Numlock state inverted: active at login, disabled on session
Hi, yes this bug seems resolved since a few days and 19.10 release : NumLock is still enabled on the login screen (which is fine), and this time well remains active after connexion, so no more problem for me ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842880 Title: Numlock state inverted: active at login, disabled on session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1842880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842880] Re: Numlock state inverted: active at login, disabled on session
apport information ** Tags added: apport-collected wayland-session ** Description changed: Hi, running Ubuntu 19.10 development version, I have a problem since a few days: Numlock behaviour is inverted. It is active and already enabled on the login screen, without the need to press the "Verr Num" Key to type numbers for the password. But just after the connexion and session start, it is inactive - I have to press the Key to make it available again. Normally it's the contrary! NumLock is disabled on login screen, and if activated at this moment, it remains active on the session... In Dconf editor, numlock-state is well 'on' and remember-numlock-state 'true'. Thanks in advance for your help. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2018-06-16 (445 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) + Package: gnome-settings-daemon 3.33.90-1ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 + Tags: eoan wayland-session + Uname: Linux 5.2.0-15-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-06-10 (86 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1842880/+attachment/5286940/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842880 Title: Numlock state inverted: active at login, disabled on session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1842880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842880] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1842880/+attachment/5286941/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842880 Title: Numlock state inverted: active at login, disabled on session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1842880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842880] [NEW] Numlock state inverted: active at login, disabled on session
Public bug reported: Hi, running Ubuntu 19.10 development version, I have a problem since a few days: Numlock behaviour is inverted. It is active and already enabled on the login screen, without the need to press the "Verr Num" Key to type numbers for the password. But just after the connexion and session start, it is inactive - I have to press the Key to make it available again. Normally it's the contrary! NumLock is disabled on login screen, and if activated at this moment, it remains active on the session... In Dconf editor, numlock-state is well 'on' and remember-numlock-state 'true'. Thanks in advance for your help. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: eoan numlock ** Tags added: eoan numlock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842880 Title: Numlock state inverted: active at login, disabled on session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1842880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727958] Re: Libreoffice writer / calc etc show as white icon in launcher when opened
** Tags added: cosmic dingo eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727958 Title: Libreoffice writer / calc etc show as white icon in launcher when opened To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1727958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727958] Re: Libreoffice writer / calc etc show as white icon in launcher when opened
Yes, bug is still present, even in Ubuntu 19. 10 : Whether any Writer or Calc document is opened, in the dock I have only the generic white LibreOffice icon showing, the same for all of them - instead of the blue one for Writer, the green for Calc etc... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727958 Title: Libreoffice writer / calc etc show as white icon in launcher when opened To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1727958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801757] Re: all app indicators disappear
With the last update today: Dropbox, Radiotray-NG and gEncFS Manager indicators came back working in the top panel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1801757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801757] Re: all app indicators disappear
I don't know if it is the same bug, but I have a similar problem since approx. 1 week in Dingo : Dropbox, Radio-tray NG, gEncFS Manager indicators are no more visible in the top bar, programs are still running. Those from Gnome Shell extensions are still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1801757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804465] Re: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo
*** This bug is a duplicate of bug 1804260 *** https://bugs.launchpad.net/bugs/1804260 Thanks for the answer. I well made 2 reports on the windows opened after the crashes when asked to do it, but it didn't open Launchpad, I got no confirmation bug report was sent, and when searching before creating a new bug, nothing similar appeared, that's why I made the screenshots. Perhaps it would be useful to add a confirmation that crash report has well been received ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804465 Title: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804465] Re: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo
** Attachment added: "Nautilus-02.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+attachment/5214997/+files/Nautilus-02.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804465 Title: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804465] Re: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo
** Attachment added: "Nautilus-04.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+attachment/5214999/+files/Nautilus-04.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804465 Title: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804465] [NEW] Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo
Public bug reported: Hi, since a few days on Ubuntu 19.04 Dingo development version, Nautilus systematically crashes when I'm doing a research by file name. Error message: Nautilus crashed with SIGSEGV in g_type_check_instance_cast (see images joined) It happens when I enter a word on the search bar with the keyboard, never on first character, nor if I do a copy - paste with Ctrl C / Ctrl V ; but if I write the search item, it crashes, Nautilus closes. Package : Nautilus 3.26.4-0ubuntu8 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Nautilus-01.png" https://bugs.launchpad.net/bugs/1804465/+attachment/5214996/+files/Nautilus-01.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804465 Title: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804465] Re: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo
** Attachment added: "Nautilus-03.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+attachment/5214998/+files/Nautilus-03.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804465 Title: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
Hi, I have the same problem since 3 weeks on a fresh install of Ubuntu Cosmic, with Wayland session enabled by default : 2/3 of the time, login screen doesn't appear and screen remains black, pushing power button makes Ubuntu background visible again and computer stops. I join some Auth.log since 17th September, here is an extract - will do some further tests : Session c1 logged out. Waiting for processes to exit. Unregistered Authentication Agent for unix-session:c1 (system bus name :1.35, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus) Removed session c1. session closed for user gdm session opened for user root by (uid=1000) Executing command [USER=root] [TTY=unknown] [CWD=/home/valeryan24] [COMMAND=/usr/lib/update-notifier/package-system-locked] Operator of unix-session:2 successfully authenticated as unix-user:valeryan24 to gain TEMPORARY authorization for action org.debian.apt.install-or-remove-packages for system-bus-name::1.336 [/usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map] (owned by unix-user:valeryan24) asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Registered Authentication Agent for unix-session:2 (system bus name :1.190 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) New seat seat0. pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) New session c1 of user gdm. session opened for user gdm by (uid=0) gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session closed for user gdm Session c1 logged out. Waiting for processes to exit. Removed session c1. pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) New session c2 of user gdm. pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user-121.slice failed with 'canceled' session closed for user gdm session opened for user gdm by (uid=0) pam_unix(gdm-launch-environment:session): session closed for user gdm Session c2 logged out. Waiting for processes to exit. Removed session c2. systemd: pam_unix(systemd-user:session): session closed for user gdm systemd-logind[815]: Power key pressed. systemd-logind[815]: Powering Off... systemd-logind[815]: System is powering down. ** Attachment added: "Auth.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+attachment/5199069/+files/Auth.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780472] Re: After beta update all plugins are turned off and can't be turned on
Hi, bug seems to be resolved with last Ubuntu 18.04 and ppa update, addons were reactivated. Some of them needed to be done manually, but button for enabling reappared, so it works normally, thanks for your help ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780472 Title: After beta update all plugins are turned off and can't be turned on To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1780472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780472] Re: After beta update all plugins are turned off and can't be turned on
Hi, some comments on Bugzilla : https://bugzilla.mozilla.org/show_bug.cgi?id=1474255#c13 "I guess they have a patch to address bug 1464766 - https://bugzilla.mozilla.org/show_bug.cgi?id=1464766 - and didn't notice that bug 1461217 changed _installLocation to location - https://bugzilla.mozilla.org/show_bug.cgi?id=1461217"; "It's entirely Ubuntu specific. My guess as to what happened is that they took the patch from bug 1464766, backported it to 61, and had to adjust it because of bug 1461217 not being on 61, and then that patch ended up being used in the backported form on 62, which breaks things because of bug 1461217." ** Bug watch added: Mozilla Bugzilla #1464766 https://bugzilla.mozilla.org/show_bug.cgi?id=1464766 ** Bug watch added: Mozilla Bugzilla #1461217 https://bugzilla.mozilla.org/show_bug.cgi?id=1461217 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780472 Title: After beta update all plugins are turned off and can't be turned on To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1780472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780472] Re: After beta update all plugins are turned off and can't be turned on
I have the same problem in Ubuntu 18.04 LTS with ppa Mozilla Team Firefox Next enabled, but not on another computer on 18.10 development version: Firefox is also in 62.06b and all addons still work well... ** Attachment added: "FF62-1810.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780472/+attachment/5161596/+files/FF62-1810.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780472 Title: After beta update all plugins are turned off and can't be turned on To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1780472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780793] [NEW] All extensions disabled in Firefox 62.0b6 on Ubuntu 18.04 LTS
Public bug reported: Hi, This is related to Firefox-next version from the Mozilla Team ppa : https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next Steps to reproduce: On Ubuntu 18.04 LTS, with the ppa Mozilla Firefox Next activated, updates this morning (9th July), which installed Firefox 62.0b6 64 bits. Actual results: At FF restart, all extensions were totally disabled. On the "Tools - Addons" pane, only the button "Remove" is possible, no way to reactive extensions. I only use Linux, Firefox profile is in Ubuntu. Tried to uninstall and reinstall one of the addons from Mozilla site, got the error message : "the addon downloaded from this site could not be installed because it appears to be corrupt" Expected results: Webextensions should continue to work. Other users seem impacted (see the last comments): https://blog.mozilla.org/addons/2018/07/05/extensions-in-firefox-62/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: addons firefox ** Attachment added: "FF-62.png" https://bugs.launchpad.net/bugs/1780793/+attachment/5161391/+files/FF-62.png ** Bug watch added: Mozilla Bugzilla #1474255 https://bugzilla.mozilla.org/show_bug.cgi?id=1474255 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780793 Title: All extensions disabled in Firefox 62.0b6 on Ubuntu 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780793] Re: All extensions disabled in Firefox 62.0b6 on Ubuntu 18.04 LTS
Upstream report : https://bugzilla.mozilla.org/show_bug.cgi?id=1474255 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780793 Title: All extensions disabled in Firefox 62.0b6 on Ubuntu 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt
I have the same problem with Gnome-packagekit : first password attempt doesn't work (Authentification failure, try again), second is always successful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1765261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I don't agree with the last comme,nt : I have a fresh install of 18.04 and get the same error when trying to recover my old savec Private directory : Enter your MOUNT passphrase: mount: /tmp/ecryptfs.fSC9TkTG : échec de l’appel système mount(2) : Aucun fichier ou dossier de ce type. ERROR: Failed to mount private data at [/tmp/ecryptfs.fSC9TkTG]. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent
Current 18.04, on gdm login field, if I type : € # $ @ ù é they are well and correctly written. Only letters with an accent needing click on 2 keys are no more written correctly since 10th March updates on 18.04 (but work on 17.10) : û and ü give u ô and ö give o French language and "French (alternative)" keyboard configuration 07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Kernel driver in use: radeon Kernel modules: radeon, amdgpu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758563 Title: Blocked at gdm login screen on 18.04 if user password has a circumflex accent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716159] Re: gdm greeter does not allow non-US characters (like euro character €) when typing password
I just tried : - on a laptop where Ubuntu has been updated from 17.04 to 17.10 yesterday (27th March) - on the current 18.04 pre-release version on my home computer (updates made until 27th March) Both were installed with French language and "French alternative" keyboard configuration. On both I can well type Euro symbol € and it is well written in the gdm login field. Same for # $ @ ù é. Only letters with an accent needing a double click are not written correctly since 10th March updates on 18.04 (but work on 17.10) : û and ü give u ô and ö give o (see bug 1758563) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716159 Title: gdm greeter does not allow non-US characters (like euro character €) when typing password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent
*** This bug is a duplicate of bug 1716159 *** https://bugs.launchpad.net/bugs/1716159 Hi, I made some more testings. First, I just updated my laptop to Ubuntu 17.10 : I confirm that writing "û" with circumflex accent still worked on artful and that password is accepted. It's like on my computer home : from Artful until 18.04 alpha, it worked in gdm with a "û" character. Since 10th March updates, no more. On Ubuntu 17.10, on the contrary to bug 1716159, I still can type the Euro symbol € in the login field and it is well written... I will check later for current 18.04. To resume : gdm : Debian Stretch 3.22.3 Type "u with circumflex accent" = û Ubuntu 17.10 updated 03-27-2018 3.26.1 Type "u with circumflex accent" = û Ubuntu 18.04 > 10th March 2018 3.27.92 Type "u with circumflex accent" = u I made an upstream bug report to gdm in Gnome to see if there has been on their side a modification in code which made this circumflex accent no more writable and then password refused : https://bugzilla.gnome.org/show_bug.cgi?id=794734 ** Bug watch added: GNOME Bug Tracker #794734 https://bugzilla.gnome.org/show_bug.cgi?id=794734 ** Attachment added: "Gdm in Ubuntu 17.10 updated 03-27-2018 with circumflex accent in login field" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758563/+attachment/5092542/+files/Gdm-Artful.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758563 Title: Blocked at gdm login screen on 18.04 if user password has a circumflex accent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent
*** This bug is a duplicate of bug 1716159 *** https://bugs.launchpad.net/bugs/1716159 Thanks, I already did that the first time I was blocked on login screen, it failed at step 3 : unable to connect after changing passwd in recovery... I don't know if problem is correlated, but I have no more access to terminal : Ctrl Alt F1 F2... does nothing. For the moment I solved the problem with a complete fresh reinstallation of Ubuntu bionic, iso from 21st March and an initial password without "û". But someone just tried with Debian Stretch, gdm3 version 3.22.3 : when he writes û in the login field, it well writes û with the accent. In 18.04, when I type û, it writes u I need to test on Ubuntu Artful, but as said before my password always had û on 17.10 and it worked, same on early versions of 18.04 ; only with the 10th March updates of bionic it failed, with gdm3 now in 3.27.92. For me it is a different bug than 1716159 because much more recent, at least for the circumflex accent problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758563 Title: Blocked at gdm login screen on 18.04 if user password has a circumflex accent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent
*** This bug is a duplicate of bug 1716159 *** https://bugs.launchpad.net/bugs/1716159 Hi, I'm not sure this is an exact duplicte of bug 1716159 (I saw it before reporting here). It's right, today I checked, if I enter û in the gdm login field, it writes u, but : - this was also the case since early alpha testing of Ubuntu 17.10, I already had the same password, only since update of 10th March 2018 it is refused. And when I chose it, on the live USB installation, was the French alternative keyboard selected, so I'm sure it was with the accent (I checked again, typing one with û and one with u gets an error on 2 passwords not matching). - In this case, modifying the password in recovery session should have allowed me to login again (which I could in terminal only the very first time I had this bug, so modification was successful, after ,I have no access to console), but not... Something specifically changed between mid-February and 10th March making login impossible with my "û" containing password and forcing me to reinstall... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758563 Title: Blocked at gdm login screen on 18.04 if user password has a circumflex accent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758563] [NEW] Blocked at gdm login screen on 18.04 if user password has a circumflex accent
Public bug reported: Hi, I have a bug since the recent updates on Ubuntu 18.04 (post 10th March): when the user password contains a circumflex accent, like "û", access is denied even if password entered is correct and I stay blocked in a loop at gdm login screen - error message (translated from French): "Sorry, it doesn't work, please try again". Even after modifying it on recovery mode with passwd without û, it stays blocked. Only way to solve it is to reinstall. Graphic card: [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] Kernel driver in use: radeon Kernel modules: radeon, amdgpu Steps to reproduce : I did a fresh and new install with 18.04 daily iso from 21st March, formatting / and /home with following user password: Ubuntu42 At startup, I could log successfully both on Xorg and Wayland sessions. Then I modified and tested those passwords, with all of them I could again boot and connect, on Xorg and Wayland: ArchLinux43 LinuxMint@28 KDENeon=51 Fedora_1984 But the last one made me blocked at the gdm login screen: Debianû74 Here unable to modify it on recovery session, error message in French: "erreur de manipulation du jeton d'authentification". Also unable to launch terminal: CTRl Alt F1 refreshes the screen, but F2, F3... F12 freezes it! I only can update in chroot with lie USB. I had to again format and reinstall, with a password without any circumflex accent. How and when I discovered it : On 10th March, I ran since many weeks the alpha version of Ubuntu 18.04, with a password having a "û" inside, which had always worked fine. I did an update, cumulating the last 3 weeks before. On next startup, when I typed my password, both on Xorg and Wayland sessions, no error message but no desktop, nothing appeared but a few seconds later I was back on login screen. I could well log in on terminal (Ctrl Alt F2) or chroot with a live USB, and do the last updates in the next days, but nothing changed. On console, if I ran "startx" I got the message "timeout in locking authority file" and "fatal server error: cannot open log file ./local/share/xorg/Xorg.0.log Both / and /home were not full - more than 60% space available, verified with df -Th ; echo ; df -Ti I tried to reinstall Ubuntu with daily live of 15th March, formatting / but not /home as it was protected by ecryptfs and I didn't save some files, using same user name and password, still blocked. So I copied the /home and .Private folders to another disk to try later recover them, reinstall again, formatting both / and /home, always with my usual password having a "û" (I verified French language, keyboard with French activated, upper case, symbols... OK). This time, again both for Xorg or Wayland sessions, at gdm login I did not success to connect, I got an error message "Désolé ça n'a pas fonctionné, veuillez réessayer", I tried to modify the password in recovery mode, with no special characters nor accents, but still blocked at gdm. And no terminal available with Ctrl Alt F2... On 23rd March, I re-reinstalled all Ubuntu, formatting / and /home, this time with daily iso from 21st March, but with a modification: to avoid any misconfiguration with languages on live USB, I chose a very easy password, only with normal letters and numbers. On startup, yes, finally I could log at gdm on default Xorg session and enter desktop ! I went to my user configuration, changed to put my usual password (with an "û"), and bam, back to the future, still blocked at gdm screen on restart, either on Xorg or Wayland, Ctr Alt F2 not working. It made me understand that the bug came from a special character in my password, then I tried the different ones explained on top of this report to discover it was "û". ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: gdm password ubuntu-fr-bionic ** Attachment added: "Ubuntu.jpg" https://bugs.launchpad.net/bugs/1758563/+attachment/5089342/+files/Ubuntu.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758563 Title: Blocked at gdm login screen on 18.04 if user password has a circumflex accent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
