[Bug 33288] Re: Evince doesn't handle columns properly
I agree... now, it's MUCH better. However, I think it would be better if one could select the text from only one column. I think this makes more sense as most of the times one doesn't want to select, at the same time, part of a column and part of the other column. But, again, great job!!! -- Evince doesn't handle columns properly https://bugs.launchpad.net/bugs/33288 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33288] Re: Evince doesn't handle columns properly
I used the PPA from Arand: https://launchpad.net/~arand/+archive/poppler After the update of the libpoppler, when I past the text copied from two columns, the text of the first column is pasted separately from the text of the second column. Before the update, the text was pasted all mixed, as the two columns were only one column. For instance, in this file: http://www.sigcomm.org/sigcomm2005/paper-KarPap.pdf If I try to select the last paragraph, of the first column, in the third page, the text from both columns is selected. But, when I paste it, the text from the first column appears before the text from the second column, as it is below. Before the update, the text appeared all mixed up as if the two columns were only one. "The two sites and time-of-capture of the analyzed traces were selected so that our methodology could be tested against a variety of different conditions and a diverse set of applica- tions. Indeed, the selected links reflect significantly different network “types”, evident from the application mix as ana- lyzed in the following section. In addition, the two university traces were collected both during weekdays (UN1 ) and also beginning of weekend (UN2 ) to capture possible weekday to weekend variation in application usage and network traffic to further identify data transfer flows, such as passive ftp, we parse the control stream to acquire the context regarding the upcoming data transfer, i.e. the host and port number where the follow-up data connection is going to take place. The per-packet operation simply examines the contents of each packet against our array of strings, and classifies the corresponding flow with an application-specific tag in case of a match. Successful classification of a flow on one direction leads to the subsequent classification of the respective flow in" -- Evince doesn't handle columns properly https://bugs.launchpad.net/bugs/33288 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33288] Re: Evince doesn't handle columns properly
Sorry!!! I realize now that this is supposed to be a solution for Evince. I was using Okular. I tried now with Evince and it works very well. Thank you and sorry again for the confusion! -- Evince doesn't handle columns properly https://bugs.launchpad.net/bugs/33288 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33288] Re: Evince doesn't handle columns properly
Yes, it pastes all the text that is selected, and only that. Yes, I agree, it is improved. Before, pasting text from two columns was a complete mess. Now, at least, the text from both columns is pasted separately. -- Evince doesn't handle columns properly https://bugs.launchpad.net/bugs/33288 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 511086] Re: Missing some Czech unicode characters in selected text
I have the same problem with portuguese characters. This is especially annoying when you trying to copy text from a pdf file and paste it into another document. The normal characters appear in a line, and the special characters in a different line. Maybe it is something related with these old problems: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/116453 https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/37283 -- Missing some Czech unicode characters in selected text https://bugs.launchpad.net/bugs/511086 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37283] Re: Punctuation, Characters disappear upon highlighting.
But worse than the fact that the characters disappear when highlighting, is that if one selects, copies and pastes that text the special characters will appear all messed up. -- Punctuation, Characters disappear upon highlighting. https://bugs.launchpad.net/bugs/37283 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203513] Re: display doesn't go to DPMS sleep
The problem still exists in Lucid. -- display doesn't go to DPMS sleep https://bugs.launchpad.net/bugs/203513 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
Hi! I just made a clean install of Lucid and the problem remains. It is really annoying... :s I also noticed the following warning messages which I don't know if they're important: TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_xevent_key,203 - could not map keysym 1008ffa8 to keycode (gnome-power-manager:18687): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:2273: signal `proxy- status' is invalid for instance `0x94d9270' TI:01:24:09 TH:0x94746d8FI:gpm-brightness-hal.c FN:gpm_brightness_hal_init,455 - No devices of capability laptop_panel TI:01:24:09 TH:0x94746d8FI:gpm-phone.c FN:gpm_phone_dbus_connect,261 - Cannot connect, maybe the daemon is not running: Could not get owner of name 'org.gnome.phone': no such name TI:01:24:09 TH:0x94746d8FI:gpm-phone.c FN:gpm_phone_coldplug,76 - not connected Appeared here: - Verbose debugging 1 (on console 1)GPM_VERBOSE TI:01:24:09 TH:0x94746d8FI:gpm-main.c FN:main,210 - GNOME Power Manager 2.30.0 TI:01:24:09 TH:0x94746d8FI:gpm-session.cFN:gpm_session_init,511 - idle: 1, idle_inhibited: 0, suspend_inhibited: 0 TI:01:24:09 TH:0x94746d8FI:gpm-session.c FN:gpm_session_register_client,367 - registered startup '(null)' to client id '/org/gnome/SessionManager/Client33' TI:01:24:09 TH:0x94746d8FI:egg-console-kit.c FN:egg_console_kit_init,304 - ConsoleKit session ID: /org/freedesktop/ConsoleKit/Session2 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=124 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=213 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=150 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_xevent_key,203 - could not map keysym 1008ffa8 to keycode TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=233 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=232 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=160 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=244 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=238 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=237 TI:01:24:09 TH:0x94746d8FI:gpm-button.c FN:gpm_button_grab_keystring,176 - Grabbed modmask=8000, keycode=236 (gnome-power-manager:18687): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x94d9270' TI:01:24:09 TH:0x94746d8FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_setup_display,170 - No outputs have backlight property TI:01:24:09 TH:0x94746d8FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_init,717 - no XRANDR extension, so aborting init TI:01:24:09 TH:0x94746d8FI:egg-dbus-proxy.c FN:egg_dbus_proxy_connect,73 - already connected to org.freedesktop.Hal TI:01:24:09 TH:0x94746d8FI:egg-dbus-proxy.c FN:egg_dbus_proxy_connect,73 - already connected to org.freedesktop.Hal TI:01:24:09 TH:0x94746d8FI:gpm-brightness-hal.c FN:gpm_brightness_hal_init,455 - No devices of capability laptop_panel TI:01:24:09 TH:0x94746d8FI:gpm-prefs-server.c FN:gpm_prefs_server_set_capability,84 - capability now 4 TI:01:24:09 TH:0x94746d8FI:gpm-idle.c FN:gpm_idle_evaluate,187 - session_idle=1, idle_inhibited=0, suspend_inhibited=0, x_idle=0 TI:01:24:09 TH:0x94746d8FI:gpm-idle.c FN:gpm_idle_evaluate,192 - X not idle TI:01:24:09 TH:0x94746d8FI:gpm-idle.c FN:gpm_idle_set_timeout_dim,261 - Setting dim idle timeout: 10s TI:01:24:09 TH:0x94746d8FI:gpm-dpms.c FN:gpm_dpms_clear_timeouts,311 - set timeouts to zero TI:01:24:09 TH:0x94746d8FI:egg-console-kit.c FN:egg_console_kit_init,304 - ConsoleKit session ID: /org/freedesktop/ConsoleKit/Session2 TI:01:24:09 TH:0x94746d8FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,299 - no dimming hardware TI:01:24:09 TH:0x94746d8FI:gpm-idle.c FN:gpm_idle_set_check_cpu,122 - Setting the CPU load check to 0 TI:01:24:09 TH:0x94746d8FI:gpm-manager.cFN:gpm_manager_init,1950 - creating new control instance TI:01:24:09 TH:0x94746d8FI:gpm-manager.cFN:gpm_manager_init,1955 - creating new tray icon TI:01:24:09 TH:0x94746d8FI:gpm-phone.c FN:gpm_phone_dbus_connect,242 - get connection TI:01:24:09 TH:0x94746d8FI:gpm-phone.c FN:gpm_phone_dbus_connect,253 - get proxy TI:0
[Bug 473705] Re: power management does not consistently power down inactive monitor
I'm seeing this problem in Lucid and I've been experiencing since I updated to Karmic. I thought that it might be something that went wrong in the update process. But now, I made a clean install of Lucid, and the problem remains. Sometimes it works well, but most of the times it doesn't. However, it is hard to know how to reproduce the problem. Maybe it is related with change from HAL. xfce4-power-manager uses HAL (as it used gnome-power-manager before Karmic) and it works properly. This is a really annoying issue. Thank you -- power management does not consistently power down inactive monitor https://bugs.launchpad.net/bugs/473705 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423771] Re: [TOSHIBA Satellite A200] late resume failure
I'm experiencing this exact same problem in Lucid with kernel 2.6.32-22. -- [TOSHIBA Satellite A200] late resume failure https://bugs.launchpad.net/bugs/423771 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
I'm not 100% sure that this is the same problem that I'm experimenting, but I think so. When I turn on the computer and I log in, the display seems to go sleep when it is supposed to go. However, after a while, the display stops going to the sleep mode when it is inactive and I can see the same icon, with the arrows in the corners, in the notification area. I have been trying, for a long time, to find out what causes this change in the display behavior, but I couldn't understand what it is. I noticed that, if I take out the laptop battery and put it again, or vice versa, the display starts failing to go to the sleeping mode. But I couldn't exactly notice a concrete pattern. If I kill the gnome-power-management process and start it again, everything seems to work properly again. I also saw the following when running the gnome-power-management in verbose mode: "TI:23:11:17TH:0x9146168FI:gpm-manager.c FN:gpm_manager_idle_changed_cb,632 - lid is closed, so we are ignoring ->NORMAL state changes" Why does it say that the lid is close if it is open? Maybe this has no importance... I don't know. I have the screensaver disabled. I have an intel integrated video chipset. Thank you! -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
There is another unexpected behavior that I forgot to mention. If I turn on the laptop with the battery plugged, in the power management preferences, there are three tabs: On AC Power; On Battery Power; and General. However, if I turn on the laptop without the battery attached, I can only see two tabs: On AC Power and General. This is not completely absurd. But, if I plug the battery with the computer on, it still show only the two tabs: On AC Power and General. And even if I then unplug the AC power and use only the battery power, I continue to see only the same two tabs in the power management preferences. I don't know if this is related with the problem reported or if it is a new and independent problem. Thank you! -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
Sorry, I also forgot to mention that I updated from Jaunty to Karmic. In Jaunty, everything was working properly. -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
I'm not sure if I understood correctly. Did you suggest to try a clean install of Karmic or to updated from Jaunty to Karmic? I'm woking on an important project, and I cannot make a clean install of ubuntu in my computer right now. Maybe in a few months I'll do it. -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
Ok, I'll add more information when I install Karmic from a clean state. Thank you! -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
This is not a solution, nor even a workaround. It's more a alternative for those of you who, like my self, cannot make a clean install of Karmic right now. The power manager tool from Xfce works pretty well. The version in the repositories still has this bug: http://bugzilla.xfce.org/show_bug.cgi?id=6008 But it is not very important for me. Merry Christmas! ** Bug watch added: Xfce Bugzilla #6008 http://bugzilla.xfce.org/show_bug.cgi?id=6008 -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915958] [NEW] Touchpad (hardware) is not recognized, does not appear in the device list - Lenovo BS145-15IIL
Public bug reported: Touchpad (hardware) is not recognized, does not appear in the device list - Lenovo BS145-15IIL. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joao 1168 F pulseaudio /dev/snd/pcmC0D0c: joao 1168 F...m pulseaudio /dev/snd/pcmC0D0p: joao 1168 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 17 16:42:19 2021 InstallationDate: Installed on 2021-02-02 (15 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 413c:301d Dell Computer Corp. Dell Universal Receiver Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82HB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=7aab346d-8439-40aa-b9f3-fa4e5cadb865 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo BS145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82HB:pvrLenovoBS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoBS145-15IIL: dmi.product.family: BS145-15IIL dmi.product.name: 82HB dmi.product.sku: LENOVO_MT_82HB_BU_idea_FM_BS145-15IIL dmi.product.version: Lenovo BS145-15IIL dmi.sys.vendor: LENOVO ** Affects: linux (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/1915958 Title: Touchpad (hardware) is not recognized, does not appear in the device list - Lenovo BS145-15IIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915958] Re: Touchpad (hardware) is not recognized, does not appear in the device list - Lenovo BS145-15IIL
** Description changed: - Touchpad (hardware) is not recognized, does not appear in the device - list - Lenovo BS145-15IIL. + Touchpad (hardware) não é reconhecido, não aparece na lista de + dispositivos - Lenovo BS145-15IIL. - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: linux-image-5.4.0-65-generic 5.4.0-65.73 - ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 - Uname: Linux 5.4.0-65-generic x86_64 - ApportVersion: 2.20.11-0ubuntu27.16 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: joao 1168 F pulseaudio - /dev/snd/pcmC0D0c: joao 1168 F...m pulseaudio - /dev/snd/pcmC0D0p: joao 1168 F...m pulseaudio - CasperMD5CheckResult: skip - CurrentDesktop: XFCE - Date: Wed Feb 17 16:42:19 2021 - InstallationDate: Installed on 2021-02-02 (15 days ago) - InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) - Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 413c:301d Dell Computer Corp. Dell Universal Receiver - Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera - Bus 001 Device 003: ID 8087:0aaa Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - MachineType: LENOVO 82HB - ProcFB: 0 i915drmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=7aab346d-8439-40aa-b9f3-fa4e5cadb865 ro quiet splash vt.handoff=7 - RelatedPackageVersions: - linux-restricted-modules-5.4.0-65-generic N/A - linux-backports-modules-5.4.0-65-generic N/A - linux-firmware1.187.9 - SourcePackage: linux - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 07/22/2020 - dmi.bios.vendor: LENOVO - dmi.bios.version: DKCN48WW - dmi.board.asset.tag: NO Asset Tag - dmi.board.name: LNVNB161216 - dmi.board.vendor: LENOVO - dmi.board.version: SDK0J40697 WIN - dmi.chassis.asset.tag: NO Asset Tag - dmi.chassis.type: 10 - dmi.chassis.vendor: LENOVO - dmi.chassis.version: Lenovo BS145-15IIL - dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82HB:pvrLenovoBS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoBS145-15IIL: - dmi.product.family: BS145-15IIL - dmi.product.name: 82HB - dmi.product.sku: LENOVO_MT_82HB_BU_idea_FM_BS145-15IIL - dmi.product.version: Lenovo BS145-15IIL + Tipo de problema: Bug + DistroRelease: Ubuntu 20.04 + Pacote: linux-image- 5.4.0-65- genérico 5.4.0-65.73 + ProcVersionSign ature : Ubuntu 5.4.0-65.73-genérico 5.4.78 + Uname: Linux 5.4.0-65-genérico x86_64 + ApportVersion: 2.20.11- 0ubuntu27. 16 + Arquitetura: amd64 + AudioDevicesInUse: + COMANDO DE ACESSO PID DE USUÁRIO + / dev / snd / controlC0: joao 1168 F pulseaudio + / dev / snd / pcmC0D0c: joao 1168 F ... m pulseaudio + / dev / snd / pcmC0D0p: joao 1168 F ... m + pulseaudio CasperMD5CheckR esult : ignorar + CurrentDesktop: XFCE + Data: Quarta, 17 de fevereiro 16:42:19 2021 + InstallationDate: Instalado em 2021-02-02 (15 dias atrás) + InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Lançamento amd64 (20200731) + Lsusb: + Bus 002 Dispositivo 001: ID 1d6b: 0003 Linux Foundation 3.0 root hub + Bus 001 Dispositivo 004: ID 413c: 301d Dell Computer Corp. Dell Universal Receiver + Bus 001 Dispositivo 002: ID 174f: 1176 Syntek Integrated Camera + Bus 001 Dispositivo 003: ID 8087: 0aaa Intel Corp. + Bus 001 Dispositivo 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 82HB + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 5.4.0-65- generic root = UUID = 7aab346d- 8439-40aa- b9f3-fa4e5cadb865 ro quiet splash vt.handoff = 7 + RelatedPackageV ersions: + linux- restrito- modules- 5.4.0-65- genérico N / A + linux- backports- modules- 5.4.0-65- genérico N / A + linux-firmware 1.187.9 + SourcePackage: linux + UpgradeStatus: Nenhum log de atualização presente (provavelmente instalação nova) + dmi.bios.date: + 07/22/2020 dmi.bios.vendor: LENOVO + dmi.bios.version: DKCN48WW + dmi.board. asset.tag: NO Asset Tag + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis. asset.tag: NO Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis. versão: Lenovo BS145-15IIL + dmi.modalias: dmi: bvnLENOVO: bvrDKCN48WW: bd07 / 22/2020 : svnLENOVO: pn82HB: pvrLenovoBS145- 15IIL: rvnLENOVO : rnLNVJvrB161216: cvrLNVJVRB161216 : cvrmi- 15Iproduct0IL: cvr1-15Itv0 Nv0IL: cvr115Iproduto -15I NVOTOVO : rnLNVJvrVnB161216: cvrMi-15- KVNVNV0NV0IL: + cv14DK0-16 família: BS145-15IIL + dmi.product.name: 82HB + dmi.product.sku: LENOVO_ MT_82HB_ BU_idea_ FM_BS145- 15IIL + dmi.product. versão: Lenovo BS145-15IIL dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915958 Title: Touchpad (h
[Bug 89860] Re: /proc/acpi/button/lid/*/state always says "open"
My problem is a little different. I don't know if it is related. The state in /proc/acpi/button/lid/LID/state is ALWAYS correct. However, after I close the lid for the first time and open it again, the gnome-power-manager always says: "lid is closed, so we are ignoring ->NORMAL state changes" (but the lid is open) If I reboot or hibernate, everything goes back to the normal. It's only when I close the lid and open it again that this problem appears. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/89860 Title: /proc/acpi/button/lid/*/state always says "open" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 376793] Re: HP 2140 Lid Close Not Detected
sorry, I explained it wrong. I didn't meant to say that the workaround creates a new problem. What I wanted to say is that what causes this problem also prevents the monitor from going to sleep. Both problems seems to have the same cause. By the way, I cannot apply the workaround. It says "permission denied", even if I use sudo. $ sudo echo 1 > /proc/acpi/video/GFX0/DOS bash: /proc/acpi/video/GFX0/DOS: Permission denied $ sudo echo 0 > /proc/acpi/video/GFX0/DOS bash: /proc/acpi/video/GFX0/DOS: Permission denied I also noticed another thing. If I do the following (as explained in https://bugzilla.redhat.com/show_bug.cgi?id=512958) it recognizes correctly if the lid is closed or open. $ cat /proc/acpi/button/lid/LID/state state: closed $ cat /proc/acpi/button/lid/LID/state state: open But the output of the gnome-power-manager in verbose mode (and with the lid open) says that the lid is closed: TI:12:09:52 TH:0x8a7e8b8FI:gpm-idle.c FN:gpm_idle_set_mode,108 - Doing a state transition: normal TI:12:09:52 TH:0x8a7e8b8FI:gpm-manager.c FN:gpm_manager_idle_changed_cb,804 - lid is closed, so we are ignoring ->NORMAL state changes TI:12:09:52 TH:0x8a7e8b8FI:gpm-idle.c FN:gpm_idle_evaluate,192 - X not idle -- HP 2140 Lid Close Not Detected https://bugs.launchpad.net/bugs/376793 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 376793] Re: HP 2140 Lid Close Not Detected
The workaround seems to work only in the cases where /proc/acpi/button/lid/LID0/state does NOT show the correct state. Though, there are cases where /proc/acpi/button/lid/LID0/state shows the correct state, but the gnome-power-manager does not recognizes the state changes. In those cases, the workaround suggested in that bug report does not solve the problem. And, in the verbose mode, the gnome-power-manager shows: "lid is closed, so we are ignoring ->NORMAL state changes" (but the lid is open) -- HP 2140 Lid Close Not Detected https://bugs.launchpad.net/bugs/376793 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 376793] Re: HP 2140 Lid Close Not Detected
Yes, I used sudo sh -c 'echo 1 > /proc/acpi/video/GFX0/DOS' and sudo sh -c 'echo 0 > /proc/acpi/video/GFX0/DOS' But, it is not the same case. For instance, when I do the following, it recognizes correctly if the lid is closed or open. (with the lid closed) $ cat /proc/acpi/button/lid/LID/state state: closed (with the lid open) $ cat /proc/acpi/button/lid/LID/state state: open However, when the lid is open, the gnome-power-manager stills shows: "lid is closed, so we are ignoring ->NORMAL state changes" Because of that, it does not put the display to sleep. And when I boot, it works properly. This only happens after I close the lid for the first time. Killing gnome-power-manager and starting it again does not solve the problem. Only after logging out and logging in or rebooting, it works again. In fact, also in https://bugzilla.redhat.com/show_bug.cgi?id=512958 the report creator said at the beginning: "/proc/acpi/button/lid/C1C4/state is changing correctly from open to close and vice versa." In /etc/default/acpi-support I have: HIBERNATE_MODE=shutdown and SUSPEND_METHODS="dbus-pm dbus-hal pm-utils" Though, my problem is not the hibernate or suspend modes, which work well. The problem is that gnome-power-manager recognizes the lid as closed when it is open. Do you think it might be related? Thank you for your help! -- HP 2140 Lid Close Not Detected https://bugs.launchpad.net/bugs/376793 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658865] Re: An attempt to configure apt to install additional packages from the CD failed upon install from USB
I'm having the same problem. I tried with the Ubuntu desktop CD and with the alternate CD. I also tried creating the usb disk with the usb creator from Ubuntu and with the tool from http://www.pendrivelinux.com/downloads/Universal-USB-Installer/Universal-USB-Installer.exe But the installation always fails with the message: "An attempt to configure apt to install additional packages from the CD failed". -- An attempt to configure apt to install additional packages from the CD failed upon install from USB https://bugs.launchpad.net/bugs/658865 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659647] Re: An attempt to configure apt to install additional packages from the cd failed
It also affects me. I think this bug is duplicated from this one: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/658865 -- An attempt to configure apt to install additional packages from the cd failed https://bugs.launchpad.net/bugs/659647 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 646733] Re: clicking on rhythmbox from soundmenu in unity does not show rhythmbox
I don't know if this is related but when using Banshee, if I minimized it "disapears" to the sound menu, as it should happen. However, if I click there, nothing happens. I have to open banshee again from the applications menu or from the terminal to go back again to the banshee window. -- clicking on rhythmbox from soundmenu in unity does not show rhythmbox https://bugs.launchpad.net/bugs/646733 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 646733] Re: clicking on rhythmbox from soundmenu in unity does not show rhythmbox
Sorry, my mistake. I forgot to enable the MPRIS plugin in Banshee. Sorry again. -- clicking on rhythmbox from soundmenu in unity does not show rhythmbox https://bugs.launchpad.net/bugs/646733 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629258] Re: Battery life estimation never comes around
Yes, it's right. This problem exists and many people (myself included) can confirm it. But there are here a few descriptions of distinct problems. I think that the problem that was reported here does NOT have anything to do with any physical incapacity to check the battery level. The problem is that when one clicks in the gnome-power-manager icon the tool tip says simply "Laptop battery (estimating...)". But after clicking in "Laptop battery" a window appears with several information regarding the battery. There, it is possible to see the correct level of the battery. So, I think that any problem where the gnome-power-manager is not able to check the battery level at all is not the same bug. Please correct me if I'm wrong. -- Battery life estimation never comes around https://bugs.launchpad.net/bugs/629258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629258] Re: Battery life estimation never comes around
@Darius Kulikauskas: exactly! It happens the same with me. The icon gets emptier as the time goes by. Only the text is not able to show the percentage left. But the gnome-power-manager has the correct information, because if I click on "Laptop battery" I can see the correct percentage in the window that is showed. @Frederik Elwert: I don't know if this is correct but I think the recent versions of gnome-power-manager receives that information from upower. Yes, I agree with you. If the gnome-power-manager already has the percentage left, it should be simple to show it. But I don't know, I'm not an expert. I also have Debian in the same machine and I don't have this problem. However, it is using gnome-power-manger 2.30, while ubuntu is using version 2.32. -- Battery life estimation never comes around https://bugs.launchpad.net/bugs/629258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629258] Re: Battery life estimation never comes around
Yes, you're right. I'll try your fix. Thank you!!! -- Battery life estimation never comes around https://bugs.launchpad.net/bugs/629258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594205] Re: Document viewer cannot select one column in a two-columned PDF
This problem was found and corrected in the past, I think it was when Karmic came out. Now, I installed Maverick and I was surprised to see this bug again. It's a very annoying bug when one is working with pdf files. -- Document viewer cannot select one column in a two-columned PDF https://bugs.launchpad.net/bugs/594205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594205] Re: Document viewer cannot select one column in a two-columned PDF
Please check here: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/33288 -- Document viewer cannot select one column in a two-columned PDF https://bugs.launchpad.net/bugs/594205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575630] Re: Evince doesnt correctly select the proper text in a dual collumn text
I can see this bug in Maverick. I'm using libpoppler7, version 0.14.3-0ubuntu1.1. This problem was found and corrected in the past, I think it was when Karmic came out. Now it seems to be back again. It's a very annoying bug. I think this is a duplicated bug of https://bugs.launchpad.net/ubuntu/+source/evince/+bug/594205 -- Evince doesnt correctly select the proper text in a dual collumn text https://bugs.launchpad.net/bugs/575630 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575630] Re: Evince doesnt correctly select the proper text in a dual collumn text
Please check here: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/33288 -- Evince doesnt correctly select the proper text in a dual collumn text https://bugs.launchpad.net/bugs/575630 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659434] Re: Font/image corruption after resume from hibernate
I have the exact same problem since I installed Maverick (clean install). I also have an Intel video card. Another thing in which this problem is visible is the buttons of the Gmail page. Please let me know need more information. -- Font/image corruption after resume from hibernate https://bugs.launchpad.net/bugs/659434 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447728] Re: [Lucid] Laptop only remains DPMS off for 2 seconds
I don't think the problem here is the screensaver. This problem started after GPM stopped using HAL. Since then, I've been trying to understand how to avoid this. I read many opinions. I also tried disabling gnome screensaver. But, nothing solved the problem. So, I just gave up. I removed GPM and started using Xfce power manager. It still uses HAL and it works perfectly. Every new Ubuntu version, I try again the GPM. However the problem remains. Maybe because it seems that is not being addressed. I guess the biggest reason for that is that it is difficult to reproduce the problem. Sometimes it works and others it doesn't. I just can't find out what is the pattern... By the way, when I run the GPM in verbose mode and this problem is occurring, i can see the following message: "lid is closed, so we are ignoring ->NORMAL state changes" But, the lid is not closed. Is this normal? Does it has anything to do with this problem? -- [Lucid] Laptop only remains DPMS off for 2 seconds https://bugs.launchpad.net/bugs/447728 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447728] Re: [Lucid] Laptop only remains DPMS off for 2 seconds
I noticed know that maybe my previous comment concerns a different problem. The problem I was referring to is the following: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/431146 If it is not the same, please feel free to remove my previous comment. Sorry for the confusion. -- [Lucid] Laptop only remains DPMS off for 2 seconds https://bugs.launchpad.net/bugs/447728 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
No, it's not working. It still presents the same behavior. For instance, right now I booted the laptop unplugged from power. After one hour of working, I plugged it and the display stopped going to sleep. I'm running a clean installation of Maverick. I was also looking at the changelog document of the latest version of the gnome-power-manager package and I didn't see any information about a correction of this problem, so it would be expectable that it could continue to exist in Maverick. This problem exists since gnome-power-manager stopped using HAL. I will continue to use Xfce power manager as it is much more reliable and stable. By the way, Xfce power manager is still using HAL. >From what I could read from other users it may also be a problem restricted to computers with intel graphics. But I cannot confirm this. Again, I'd like to emphasize the following message that I can see when running gnome power manager with verbose mode: "lid is closed, so we are ignoring ->NORMAL state changes" And, obviously, the lid is NOT closed. And, the following is what is showed when the laptop display should, supposedly go off, when I move the mouse. TI:17:14:54 TH:0x887c8b8FI:gpm-tray-icon.c FN:gpm_tray_icon_add_device,261 - adding device /org/freedesktop/UPower/devices/battery_BAT0 TI:17:14:58 TH:0x887c8b8FI:gpm-idle.c FN:gpm_idle_set_mode,108 - Doing a state transition: blank TI:17:15:03 TH:0x887c8b8FI:gpm-idle.c FN:gpm_idle_idletime_reset_cb,391 - idletime reset TI:17:15:03 TH:0x887c8b8FI:gpm-idle.c FN:gpm_idle_evaluate,187 - session_idle=0, idle_inhibited=0, suspend_inhibited=0, x_idle=0 TI:17:15:03 TH:0x887c8b8FI:gpm-idle.c FN:gpm_idle_set_mode,108 - Doing a state transition: normal TI:17:15:03 TH:0x887c8b8FI:gpm-manager.c FN:gpm_manager_idle_changed_cb,804 - lid is closed, so we are ignoring ->NORMAL state changes TI:17:15:03 TH:0x887c8b8FI:gpm-idle.c FN:gpm_idle_evaluate,192 - X not idle -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
I could finally understand a way of reproducing this problem. I have ubuntu maverick, fully updated, with an Intel graphics chipset. The laptop has the battery attached and is plugged to the power. After booting, when the computer is idle, the display goes off as it should. However, if I close the lid and then open it, the display cannot go off anymore when the computer is idle. The output of the verbose mode is similar to what I described in the previous comment. This is not the only case in which this problem happens, but it is till now the only one in which I can always reproduce the problem. -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
I forgot to say that, even if kill and restart the gnome power manager, the problem remains. The only way is to reboot or at least go to sleep mode and come back. -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447728] Re: [Lucid] Laptop only remains DPMS off for 2 seconds
I think (but I'm not an expert on this) that the situation that I reported may be related with this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/376793 Though it isn't the same problem, it seems to be the same cause. -- [Lucid] Laptop only remains DPMS off for 2 seconds https://bugs.launchpad.net/bugs/447728 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 431146] Re: Gnome Power Manager fails to put display to sleep
I think (but I'm not an expert on this) that the situation that I reported may be related with this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/376793 Though it isn't the same problem, it seems to be the same cause. -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 376793] Re: HP 2140 Lid Close Not Detected
This also causes another problem: the display doesn't go to sleep automatically after a certain idle time. The following appears in the output when I run gnome-power-manager with verbose mode: "lid is closed, so we are ignoring ->NORMAL state changes" It assumes that the lid is closed and, because of that, it ignores any change of the display mode. It works well until the lid is closed for the first time. After that, it always assumes that the lid is closed. -- HP 2140 Lid Close Not Detected https://bugs.launchpad.net/bugs/376793 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059367] Re: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS
Hi Arunaav, apologies for the long delay. I tried reproducing the issue and was unable to do so both with fips-preview and fips-updates. Is it still occurring? Regarding the debug log, can you also provide the server debug log? You shared the client log, which helps excluding the client as the source of the issue. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059367 Title: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048781] Re: [MIR] authd
Hi, I reviewed the internal/adapter module as requested by SE, everything seemed to be in order. The crypto they use seems to be correct and the standard lib is used. The code is structured as I would expect for an adapter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048781 Title: [MIR] authd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2048781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059367] Re: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS
Hi Arunaav, thank you for your report. How did you install the FIPS packages? Can you also provide the server log with debug enabled? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059367 Title: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
