[Bug 1955163] [NEW] passwd command somehow screwed up the password, lost access to the machine
Public bug reported: I had a fresh install of Ubuntu 20.4 Desktop on a server (yes, desktop on a server). The only extra package installed was ssh. It was a fresh install of 20.4 desktop as downloaded from the official website, plus the ssh package (and any dependency) installed via apt. The user created during installation was x with password "x" (not the real credentials, I'm using fake ones here, but the username was the same as the password). I logged in via SSH with user x: > ssh x@123.123.123.123 (obviously this wasn't the real IP) was prompted for the password, entered it, and I was in. Then I did: > sudo passwd x (yes I could probably just have done "passwd" without sudoing and without specifying the user, so I would have changed my own password. But that should be the same. I'm sudoing to change the password of an arbitrary user that happens to be myself. No reason why that shouldn't work). So I was prompted for the current password (because sudo), which I entered, and then I was prompted for a new password that I had to repeat twice and so I did. Let's say the new password was 12345678. Actually (this shouldn't be relevant), I copied the password from somewhere else and pasted it both times. I got a message saying the password was changed successfully. Then I logged out with: > exit Now I can't ssh to it anymore. When I do: > ssh x@123.123.123.123 and enter the new password, it says "Permission denied, please try again." I tried the old password too, with no success. I also tried ssh root@123.123.123.123, both with the old and new password, but unsurprisingly that doesn't work either (I don't think the root user actually has a password at all, right? and if it does, there's no reason it should be any of those two). I also tried entering nothing when prompted for the password (just the Enter key, i.e. an empty password, thinking maybe the copy-paste was what failed for whatever reason), but no. And I also tried both pasting the password and manually typing it. I'm not asking for help, I'm reporting a bug because whatever happened here, it shouldn't have happened and it caused me to lose access to the machine forever. Luckily it was a freshly installed system so it's no big deal, but in principle this is a disaster. There's no way I can have mis-typed the password at any stage, because I had it in a text file before I started and I copied and pasted it from there. If somehow some character got screwed up by pasting, and what was saved is not the string that I copied, that would be a bug. My local machine is linux too and I use a konsole terminal to ssh to the remote machine. To paste copied text I use Ctrl+Shift+V which generally work (I use it all the time to paste into the terminal both locally and when connected via ssh to other remote machines). ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955163 Title: passwd command somehow screwed up the password, lost access to the machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164016] Re: restore type-ahead find
> bug 1751069: restore type-ahead find in nautilus itself You have linked to the wrong issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771] Re: Reboot after resume from suspend (deep)
Now not only does my laptop reboot on resuming from suspend: it suddenly RANDOMLY SHUTS DOWN while I'm using it. Ubuntu people, please, give us an older non-broken version of the kernel while this gets fixed upstream, because that is obviously going to take a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897284] [NEW] duplicate bluetooth indicator
Public bug reported: At random times I get two bluetooth indicators on the bottom of the screen instead of one. See the screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Sep 25 15:27:19 2020 InstallationDate: Installed on 2013-10-11 (2540 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-07-12 (74 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:1190 acl:0 sco:0 events:67 errors:0 TX bytes:1076 acl:0 sco:0 commands:67 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-09-25 15-26-55.png" https://bugs.launchpad.net/bugs/1897284/+attachment/5414167/+files/Screenshot%20from%202020-09-25%2015-26-55.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897284 Title: duplicate bluetooth indicator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1897284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected
The bug is not invalid. It may belong to ibus or to Cinnamon or to something else. Are all icons supposed to have transparent backgrounds? If so, that would mean that both icons and desktop environments should adhere to strict color guidelines so that icons are always guaranteed to be legible. Do such guidelines exist? If so, either (a) this icon does not have an acceptable color, or (b) Cinnamon's panel does not have an acceptable background color, or (c) the guidelines are not good enough. If there are no such guidelines, then icons should never have a completely transparent background without any border. That is, they should be designed in whatever way that guarantees that they are visible on any backround. So, something is wrong somewhere, either in how the icon is designed, or in how the desktop environment is designed, or in the the framework where the desktop and the icons live. That the user can change the icon color is cool but is not a solution. The icon must be visible out of the box. So far, iBus icon is the only one I've ever seen that is practically invisible. Most icon have bright colors, which seems to suggest that if there is an expectation about the background color, it's that it is dark, which my current panel background is. ** Changed in: ibus (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895454 Title: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1895454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895454] [NEW] ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected
Public bug reported: I don't know exactly what iBus is and what it does, but it has this indicator on the bottom-right corner of the screen (whatever that area is called) which shows what the currently selected input language is, whatever that means. For example, on my system there are two choices available: "Spanish - Spanish" and "English - English (US)", and therefore the indicator shows either "ES" or "EN" depending on which one is selected. Whatever the effect of that is. The issue is, this indicator is designed with an idiotic choice of colours: a very dark blue text on a very dark gray background, which makes it mostly unreadable. I am not color blind nor visually impaired, yet both colors are almost undistinguishable to me, and it costs me a great effort to tell whether it says "EN" or "ES". Additionally, adding to the idiocy, if I click on it to see which one is actually selected, a dropdown unfolds where the two options are listed, and the currently selected one is not highlighted in any way!! It seems that the selected one is always shown first, which, assuming it's true, I can only learn by changing the selection back and forth, when it could have been as easy as showing the currently selected one in bold. It looks as if every single possible step had been purposefully taken to make this less useful, because even by doing it carelessly and without putting any thought into it, it's unlikely that it could turn out so ridiculously badly designed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Sep 13 15:38:34 2020 InstallationDate: Installed on 2013-10-11 (2528 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: ibus UpgradeStatus: Upgraded to focal on 2020-07-12 (62 days ago) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895454 Title: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1895454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892642] [NEW] liveptch indicator icon is broken
Public bug reported: See the attached screenshot, it speaks for itself ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Aug 23 18:58:13 2020 InstallationDate: Installed on 2013-10-11 (2507 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-07-12 (41 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Screenshot from 2020-08-23 18-37-56.png" https://bugs.launchpad.net/bugs/1892642/+attachment/5403909/+files/Screenshot%20from%202020-08-23%2018-37-56.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892642 Title: liveptch indicator icon is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1892642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880438] Re: Cinnamon takes a lot of CPU Usage
Is there any workaround to this crap? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880438 Title: Cinnamon takes a lot of CPU Usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1880438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892225] [NEW] apport-gtk consumes 100% CPU for way too long after something crashes
Public bug reported: Something (related to Cinnamon) crashes, so the usual popup appears telling me that something crashed, and asking me whether I wanted to send a report. I choose Send. Every time this happens, then a process called apport-gtk starts consuming 100% CPU and it goes on for several minutes, so long that I end up killing it. There's no way there is a good reason for consuming so much CPU for so long. If you need to do such an amount of processing just to generate and send a bug report, something is deeply broken. But if the operation actually had to be that computationally expensive, then you must do it in a less intensive way so that it can go on in the background, for no matter how long, without rendering me unable to use my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: /usr/bin/cinnamon (command line "cinnamon --replace") ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus call: (true,) ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report /var/crash/_usr_bin_cinnamon.1000.crash ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash 640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash CurrentDesktop: X-Cinnamon Date: Wed Aug 19 18:42:34 2020 InstallationDate: Installed on 2013-10-11 (2503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892225 Title: apport-gtk consumes 100% CPU for way too long after something crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1892225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890583] [NEW] Cinnamon (or Nemo) already EOL??
Public bug reported: I installed Cinnamon on Ubuntu 20.04 with apt-get. I went to report a bug about Nemo upstream at https://github.com/linuxmint/nemo/issues/2473 and they told me that the version I have (4.4) is EOL. How can the version distributed to Ubuntu 20.04 (the latest stable release of Ubuntu) via the Ubuntu repos ALREADY be end-of-life? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cinnamon 4.4.8-4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Thu Aug 6 14:01:25 2020 InstallationDate: Installed on 2013-10-11 (2490 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: cinnamon UpgradeStatus: Upgraded to focal on 2020-07-12 (24 days ago) ** Affects: cinnamon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890583 Title: Cinnamon (or Nemo) already EOL?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1890583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
For god's sake, this regression is HUGE. It makes the life of any developer a hell and it's been MONTHS. Can't you at least release an update rollinb back to a non-broken version until this is fixed?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535452] Re: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged
** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535452 Title: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1535452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
