[Bug 2049752] [NEW] gnome-shell crashed with SIGSEGV in __GI_getenv()
Public bug reported: New noble version ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 18 12:22:32 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2024-01-18 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7e9568201e5d <__GI_getenv+77>: cmp(%rbx),%r12b PC (0x7e9568201e5d) ok source "(%rbx)" (0x621392096246) not located in a known VMA region (needed readable region)! destination "%r12b" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7e956533813e "FONTCONFIG_SYSROOT") at ./stdlib/getenv.c:31 FcConfigCreate () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 FcInit () from /lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace noble ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2049752 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049752] Re: gnome-shell crashed with SIGSEGV in __GI_getenv()
*** This bug is a duplicate of bug 2043958 *** https://bugs.launchpad.net/bugs/2043958 Hello The bug 2043958 say This problem was most recently seen with package version 45.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/c4d852b67163763f6ebf416e212eb366999c17b8 contains more details, But but my bug say DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 and 45.3 is not likd 45.1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2049752 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049752] Re: gnome-shell crashed with SIGSEGV in __GI_getenv()
*** This bug is a duplicate of bug 2043958 *** https://bugs.launchpad.net/bugs/2043958 Hello The bug 2043958 say This problem was most recently seen with package version 45.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/c4d852b67163763f6ebf416e212eb366999c17b8 contains more details, But but my bug say DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 and 45.3 is not like 45.1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2049752 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2069835] Re: Search current folder ignores generic * outside home
Hello The search works very well in a partition formatted in NTFS. It does not work for a partition formatted in EXT4 whether there is the x-gvfs-show option or not. (ubuntu 22.04) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2069835 Title: Search current folder ignores generic * outside home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2069835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949355] [NEW] unity-tweak-tool
Public bug reported:
Hello
it seems to me that the installation of unity-tweak-tool is going wrong
Paramétrage de unity-tweak-tool (0.0.7+-0ubuntu9) ...
/usr/lib/python3/dist-packages/UnityTweakTool/__init__.py:136: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
assert id is not -1
/usr/lib/python3/dist-packages/UnityTweakTool/section/spaghetti/theme.py:155:
SyntaxWarning: "is" with a literal. Did you mean "=="?
self.ui['check_cursor_size'].set_active(True if
gsettings.interface.get_int('cursor-size') is 48 else False)
a@a:~$
thank you
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 40.4-2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 1 12:33:30 2021
InstallationDate: Installed on 2021-10-24 (8 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
KernLog:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2021-10-29 (2 days ago)
** Affects: unity-tweak-tool (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1949355
Title:
unity-tweak-tool
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1949355/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1951416] [NEW] gparted fat32 mtools
Public bug reported: hello. gparted incorrectly indicates that all fat32 partitions are in trouble only because the mtools package is missing. Can you rectify in the right place: In the O.S. main or during the installation of gparted Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.2-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 18 13:28:36 2021 InstallationDate: Installed on 2021-11-01 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211031) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1951416 Title: gparted fat32 mtools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1951416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
Hello. Hello Not exactly the same. it processes a few files and the toshiba boot screen is offered. I can only press the restart button on the lap -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963902] [NEW] xdg-user-dirs-gtk-update not working properly
Public bug reported: Hello. It seems to me that the xdg-user-dirs-gtk-update command does nothing at all. I want to change the location of the download directory. So I move the directory with this command: "mv -v /media/Common/a/Downloads /media/Common/a/BisDownloads" Then I update my reference file with this command: "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/DownloadsBis" Then I think to inform the software that the directory has changed by doing this command: "xdg-user-dirs-gtk-update" But when initiating a download, it cannot be done with the error message "...unable to save because an unknown error has occurred" Also, the "files" application continues to reference the old directory as if no update had been made. I have to log out and log back in to get everything working properly again. On the other hand, would it be possible to modify the contents of the file "user-dirs.dirs" to clearly say if the modification carried out by the command "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/TéléchargementsBis" is immediately carried out wherever necessary or if it is necessary to make another additional command or if it is necessary to wait for the next session launch because the message is not very understandable by saying only that the modifications are not lost. UBUNTU version 20.04 Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.3-3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 13:09:20 2022 InstallationDate: Installed on 2022-02-16 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220216) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1963902 Title: xdg-user-dirs-gtk-update not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963902/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965961] [NEW] gjs and mount.ntfs loop together with 150 processeor and errors
Public bug reported: a@a:~$ journalctl -g finalized mars 22 15:27:05 a gnome-shell[4162]: Object 0x5574e1359b30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:05 a gnome-shell[4162]: Object 0x7ff0e0025d70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:05 a gnome-shell[4162]: Object 0x7ff0dc0134d0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:36 a gnome-shell[4162]: Object 0x5574dfdfb6f0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:36 a gnome-shell[4162]: Object 0x5574e1bbb050 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:36 a gnome-shell[4162]: Object 0x5574e1359b30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:36 a gnome-shell[4162]: Object 0x7ff0e0025e50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:52 a gnome-shell[4162]: Object 0x5574e062b4d0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:28:02 a gnome-shell[4162]: Object 0x5574e17f1770 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:28:02 a gnome-shell[4162]: Object 0x7ff0e0027cb0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:28:02 a gnome-shell[4162]: Object 0x5574e256ab70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:28:02 a gnome-shell[4162]: Object 0x5574e256a940 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:34 a gnome-shell[4162]: Object 0x5574e3642250 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:34 a gnome-shell[4162]: Object 0x7ff0e02c8ec0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:34 a gnome-shell[4162]: Object 0x7ff0e02d9830 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff090003f40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e3642250 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e0be0910 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e0026f70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e062b5b0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e02c8ec0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e0be09f0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e0be0a60 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e0215530 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e2f1f490 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e02d9910 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e02d9830 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e01fa190 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e02d9830 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid mem
[Bug 1965961] Re: gjs and mount.ntfs loop together with 150 processeor and errors
lines 68-111 a@a:~$ journalctl -b -p err mars 22 16:11:38 a kernel: Bluetooth: Patch file not found ar3k/AthrBT_0x3101.dfu mars 22 16:11:38 a kernel: Bluetooth: Loading patch file failed mars 22 16:11:49 a gpod[1414]: No device found with uuid bd21926a45c292c575869dffe91ae2b1458bfb40, is it plugged in? mars 22 16:12:14 a gnome-session-binary[2712]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed mars 22 16:12:14 a gnome-session-binary[2712]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed mars 22 16:12:40 a gdm-password][3399]: gkr-pam: unable to locate daemon control file mars 22 16:12:41 a kernel: nouveau :01:00.0: bus: MMIO read of FAULT at 002140 [ !ENGINE ] mars 22 16:12:43 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:43 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:43 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:46 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:46 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:48 a gdm-launch-environment][2539]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed** a@a:~$ journalctl -b -g finalize | head mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af71f8cb0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157540 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157620 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157620 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157620 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7151740 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7141020 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af71574d0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157700 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af71f8cb0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. a@a:~$ journalctl -b -g finalize | wc -l 635 a@a:~$ journalctl -b -g finalize | tail mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c41bb270 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c40ad140 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f568000aa20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f568000aa20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c427ce00 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c41e1cc0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c40ad290 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x564af56b74a0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x564af53ef4c0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c427cd90 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. a@a:~$ -- You received th
[Bug 1859899] Re: Please add a ZFS gui
Hello Hello With the arrival of version 22.04, it is now certain that ZFS is a way to do an installation. It seems abnormal to me that gnome-disks keeps saying that ZFS is an unknown system and doesn't know how to mount it. Please do the needful quickly. Do not forget that the partition can be encrypted. Thanks. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1859899 Title: Please add a ZFS gui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1859899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922380] [NEW] remove shim-signed very difficult
Public bug reported:
Hello
I don't want the shim-signed anymore, but I need an additional password to
remove it.
This error is for all version of ubuntu.
I am sure I am entering the correct one because I entered it using a
copy paste technique.
Have pity on those who do not know English well !!
apt purge shim-signed
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus
nécessaires :
mokutil shim
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
shim-signed*
ATTENTION : Les paquets essentiels suivants vont être enlevés.
Vous NE devez PAS faire ceci, à moins de savoir exactement ce
que vous êtes en train de faire.
shim-signed
0 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.
Après cette opération, 2 734 ko d'espace disque seront libérés.
Vous êtes sur le point de faire quelque chose de potentiellement dangereux
Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! »
?]Oui, faites ce que je vous dis !
Annulation.
root@a:~# export LANG=us
root@a:~# apt purge shim-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
mokutil shim
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
shim-signed*
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
shim-signed
0 upgraded, 0 newly installed, 1 to remove and 171 not upgraded.
After this operation, 2734 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
?] Yes, do as I say!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "fr_FR:fr_CA",
LC_ALL = (unset),
LC_TIME = "fr_FR.UTF-8",
LC_MONETARY = "fr_FR.UTF-8",
LC_ADDRESS = "fr_FR.UTF-8",
LC_TELEPHONE = "fr_FR.UTF-8",
LC_NAME = "fr_FR.UTF-8",
LC_MEASUREMENT = "fr_FR.UTF-8",
LC_IDENTIFICATION = "fr_FR.UTF-8",
LC_NUMERIC = "fr_FR.UTF-8",
LC_PAPER = "fr_FR.UTF-8",
LANG = "us"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: this is a protected package; it should not be removed
(Reading database ... 211327 files and directories currently installed.)
Removing shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
(Reading database ... 211314 files and directories currently installed.)
Purging configuration files for shim-signed
(1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
root@a:~#
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: evince 3.38.0-1
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 2 15:07:48 2021
InstallationDate: Installed on 2020-10-25 (159 days ago)
InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64
(20201022)
KernLog:
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: evince (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy uec-images
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1922380
Title:
remove shim-signed very difficult
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922380/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1939238] [NEW] UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Public bug reported: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" become "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1939238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
https://forum.ubuntu-fr.org/viewtopic.php?id=2066134 https://forum.ubuntu-fr.org/viewtopic.php?id=2066096 https://forum.ubuntu-fr.org/viewtopic.php?id=2066153 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1939238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875647] [NEW] freewifi and IPAD not détected in 20.04.0
Public bug reported: Hello I just installed version 20.04. I note that the wifi no longer works using the iPad in relay mode. I note that the French service FREEWIFI serving as a backup is not offered as a breakdown service. Not currently having a wired connection, I am forced to steal an iphone to have a connection. Is it possible for you to operate as in version 18.04 Thank you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 15:40:17 2020 InstallationDate: Installed on 2020-04-25 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1875647 Title: freewifi and IPAD not détected in 20.04.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1875647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875647] Re: freewifi and IPAD not détected in 20.04.0
Contents of journalctl ** Attachment added: "Contents of journalctl" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1875647/+attachment/5362493/+files/Trace.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1875647 Title: freewifi and IPAD not détected in 20.04.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881816] [NEW] /share/smart-notifier/smart-notifier missing
Public bug reported: Hello I am a user who updates the documentation from time to time. In the old French version of smartmontools, it was specified that the verification of the operation of the disk destruction alerts was possible to verify by making this command sudo sh -c 'echo test de message | smart-notifier --notify' I have installed the application sudo dpkg -l | grep smart-notifier ii smart-notifier 0.28-5build1 all graphical hard disk health status notifier a@a:~$ But smart-notifier --notify La commande « smart-notifier » n'a pas été trouvée, mais peut être installée avec : sudo apt install smart-notifier after researching a bit, I saw a broken link a@a:~$ ls /usr/bin/smart-notifier /usr/bin/smart-notifier a@a:~$ ls -als /usr/bin/smart-notifier 0 lrwxrwxrwx 1 root root 38 janv. 11 19:57 /usr/bin/smart-notifier -> ../share/smart-notifier/smart-notifier a@a:~$ ls -als /share/smart-notifier/smart-notifier ls: impossible d'accéder à '/share/smart-notifier/smart-notifier': Aucun fichier ou dossier de ce type sudo apt update Atteint :1 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu focal InRelease Atteint :3 http://security.ubuntu.com/ubuntu focal-security InRelease Atteint :4 http://fr.archive.ubuntu.com/ubuntu focal-updates InRelease Atteint :5 http://fr.archive.ubuntu.com/ubuntu focal-backports InRelease Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Tous les paquets sont à jour. a@a:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" I'm not sure I'm responsible for it. Thank you for your opinion. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1881816 Title: /share/smart-notifier/smart-notifier missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1881816/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881817] [NEW] /share/smart-notifier/smart-notifier missing
Public bug reported: Hello I am a user who updates the documentation from time to time. In the old French version of smartmontools, it was specified that the verification of the operation of the disk destruction alerts was possible to verify by making this command sudo sh -c 'echo test de message | smart-notifier --notify' I have installed the application sudo dpkg -l | grep smart-notifier ii smart-notifier 0.28-5build1 all graphical hard disk health status notifier a@a:~$ But smart-notifier --notify La commande « smart-notifier » n'a pas été trouvée, mais peut être installée avec : sudo apt install smart-notifier after researching a bit, I saw a broken link a@a:~$ ls /usr/bin/smart-notifier /usr/bin/smart-notifier a@a:~$ ls -als /usr/bin/smart-notifier 0 lrwxrwxrwx 1 root root 38 janv. 11 19:57 /usr/bin/smart-notifier -> ../share/smart-notifier/smart-notifier a@a:~$ ls -als /share/smart-notifier/smart-notifier ls: impossible d'accéder à '/share/smart-notifier/smart-notifier': Aucun fichier ou dossier de ce type sudo apt update Atteint :1 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu focal InRelease Atteint :3 http://security.ubuntu.com/ubuntu focal-security InRelease Atteint :4 http://fr.archive.ubuntu.com/ubuntu focal-updates InRelease Atteint :5 http://fr.archive.ubuntu.com/ubuntu focal-backports InRelease Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Tous les paquets sont à jour. a@a:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" I'm not sure I'm responsible for it. Thank you for your opinion. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1881817 Title: /share/smart-notifier/smart-notifier missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1881817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000626] [NEW] cp command loop when using ntfs3 package
Public bug reported: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. Second try on LEGACY computer: I make a script based on cp command. I try it on a normal NTFS partition in NTFS-3G. It ends perfectly well. I restart it on the same partition mounted in NTF3 He blocks. I make on another disk two partitions of identical size. I launch on one. It hangs almost in the same place. I launch on the other. It hangs in exactly the same place. This makes me open the bug. I can provide you with some information. @b:~$ sudo df -ah |egrep "Taille|root" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sdb6 99G 28G 71G 29% /media/root/TestNTFS /dev/sdd10 60G 30G 31G 50% /media/root/TestNTFS1 /dev/sdd11 60G 30G 31G 50% /media/root/TestNTFS2 a@b:~$ First disk root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 14 3 18 Second disk root@b:~# mount -v -t ntfs3 /dev/sdd10 /$Rep mount: /media/root/TestNTFS1: /dev/sdd10 déjà monté sur /media/root/TestNTFS1. root@b:~# root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 root@b:~# dd if=/dev/zero of=FIC count=1 bs=1K Rep=/media/root/TestNTFS2 mkdir $Rep mount -v -t ntfs3 /dev/sdd11 /$Rep Na=0 Nb=25 1+0 enregistrements lus 1+0 enregistrements écrits 1024 octets (1,0 kB, 1,0 KiB) copiés, 0,000783991 s, 1,3 MB/s mount : /dev/sdd11 monté sur /media/root/TestNTFS2. root@b:~# root@b:~# time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 28 11:35:15 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-08-11 (138 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000626] Re: cp command loop when using ntfs3 package
Contents of full journal logs ** Attachment added: "journalctl -b" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+attachment/5638110/+files/Tjour0.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000626] Re: cp command loop when using ntfs3 package
Contents of errors in the journal log and remember sudo smartctl -a /dev/sdb | egrep "Pending|Reallocated" 5 Reallocated_Sector_Ct 0x0033 028 028 036Pre-fail Always FAILING_NOW 2978 197 Current_Pending_Sector 0x0012 100 100 000Old_age Always - 0 ** Attachment added: "Tjour1.txt" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+attachment/5638111/+files/Tjour1.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000626] Re: cp command loop when using ntfs3 package
Hello I can't stop both processes with the Ctrl C command. So I kill both sessions. But I can't unmount both partitions. I start the shutdown of the computer. You will see in the attached chart that it is not easy for him to request the unmounts of two TestNTFSn partitions. Especially these lines where he uses a strong way which certainly explains it becomes necessary to ask windows to work to restore. déc. 28 19:39:44 p systemd[1]: Unmounting /media/root/TestNTFS1... déc. 28 19:39:44 p systemd[1]: Unmounting /media/root/TestNTFS2b... déc. 28 19:39:44 p umount[2916153]: umount: /media/root/TestNTFS1: la cible est active. déc. 28 19:39:44 p systemd[1]: Unmounting /run/credentials/systemd-sysusers.service... déc. 28 19:39:44 p umount[2916154]: umount: /media/root/TestNTFS2b: la cible est active. déc. 28 19:39:36 p systemd[1]: user@1000.service: Killing process 2673471 (cp) with signal SIGKILL. déc. 28 19:39:36 p systemd[1]: user@1000.service: Killing process 2914934 (cp) with signal SIGKILL. déc. 28 19:39:36 p systemd[1]: user@1000.service: Deactivated successfully. déc. 28 19:39:36 p systemd[1]: user@1000.service: Unit process 2673471 (cp) remains running after unit stopped. déc. 28 19:39:36 p systemd[1]: user@1000.service: Unit process 2914934 (cp) remains running after unit stopped. déc. 28 19:39:36 p systemd[1]: Stopped User Manager for UID 1000. ** Attachment added: "trace of shutdown" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+attachment/5638368/+files/T1.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000626] Re: cp command loop when using ntfs3 package
And, now the chkdsk is blocked since about one hour on the last line. PS C:\Windows\system32> chkdsk i: /f Le type du système de fichiers est NTFS. Le nom de volume est TestNTFS1. Étape 1 : Examen de la structure du système de fichiers de base... Suppression du segment d’enregistrement de fichier endommagé 557F9E. de fin reste : 0:09:45 ... 5603584 enregistrements de fichier traités. n reste : 0:09:45 La vérification des fichiers est terminée. Durée de la phase (Vérification des enregistrements de fichiers) : 4.92 minutes. Suppression du segment d’enregistrement de fichier orphelin 557D46. Suppression du segment d’enregistrement de fichier orphelin 557DAE. Suppression du segment d’enregistrement de fichier orphelin 557E16. Suppression du segment d’enregistrement de fichier orphelin 557E7E. Suppression du segment d’enregistrement de fichier orphelin 557EE6. Suppression du segment d’enregistrement de fichier orphelin 557F4E. Suppression du segment d’enregistrement de fichier orphelin 557FBA. Suppression du segment d’enregistrement de fichier orphelin 558022. Suppression du segment d’enregistrement de fichier orphelin 55808A. 11 enregistrements de grand fichier traités. ste : 0:09:00 . Suppression du segment d’enregistrement de fichier orphelin 5580F2. Durée de la phase (Récupération des enregistrements de fichiers orphelins) : 0.00 millisecondes. 0 enregistrements de fichier incorrect traités. : 0:08:59 .. Durée de la phase (Vérification des enregistrements de fichiers incorrects) : 4.66 millisecondes. Étape 2 : Examen de la liaison des noms de fichiers... 1 enregistrements d’analyse traités. e : 0:03:480:03:50 ... État d’avancement : 5637787 de 6051814 effectué(s) ; Étape : 93% ; Total : 74% ; Heure de fin reste : 0:04:06 . -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000626] Re: cp command loop when using ntfs3 package
Finally, i kill the process then PS C:\Windows\system32> chkdsk i: /f Le type du système de fichiers est NTFS. Le nom de volume est TestNTFS1. Étape 1 : Examen de la structure du système de fichiers de base... 5603584 enregistrements de fichier traités. n reste : 0:03:45 ... La vérification des fichiers est terminée. Durée de la phase (Vérification des enregistrements de fichiers) : 1.86 minutes. 1 enregistrements de grand fichier traités. e : 0:03:41 Durée de la phase (Récupération des enregistrements de fichiers orphelins) : 0.00 millisecondes. 0 enregistrements de fichier incorrect traités. : 0:03:37 . Durée de la phase (Vérification des enregistrements de fichiers incorrects) : 2.86 millisecondes. Étape 2 : Examen de la liaison des noms de fichiers... 1 enregistrements d’analyse traités. e : 0:00:43 .. 0:00:43 . Suppression de l’entrée d’index 11 dans l’index $I30 du fichier 557BD1. de fin reste : 0:00:14 .. 6051814 entrées d’index traitées. te : 0:00:14 ... La vérification des index est terminée. Durée de la phase (Vérification de l'index) : 12.44 minutes. CHKDSK analyse les fichiers non indexés pour les reconnecter à leur répertoire d’origine. 15 fichiers non indexés analysés. ste : 0:01:28 . 0 fichiers non indexés récupérés dans le répertoire d'origine. Durée de la phase (Reconnexion orpheline) : 0.00 millisecondes. ste : 999:00:00 .. CHKDSK récupère les fichiers non indexés restants. 15 fichiers non indexés récupérés dans le répertoire des fichiers perdus et trouvés. Le répertoire des fichiers perdus et trouvés se situe dans \found.000. Durée de la phase (Récupération orpheline vers éléments perdus et trouvés) : 0.00 millisecondes. 1 enregistrements d’analyse traités. e : 999:00:00 Durée de la phase (Vérification de l’ID d’objet et du point de réanalyse) : 34.78 millisecondes. Étape 3 : Examen des descripteurs de sécurité... La vérification des descripteurs de sécurité est terminée. Durée de la phase (Vérification du descripteur de sécurité) : 55.38 millisecondes. 224115 fichiers de données traités. ste : 0:00:00 . Durée de la phase (Vérification des attributs de données) : 1.84 millisecondes. Correction des erreurs dans l’attribut BITMAP de la table de fichiers maîtres (MFT). Correction des erreurs dans le carte du volume. Windows a effectué des corrections sur le système de fichiers. Aucune autre action n’est requise. 83886079 Ko d’espace disque au total. 21538268 Ko dans 5602527 fichiers. 896488 Ko dans 224119 index. 0 Ko dans des secteurs défectueux. 5673039 Ko utilisés par le système. 65536 Ko occupés par le fichier journal. 55778284 Ko disponibles sur le disque. 4096 octets dans chaque unité d’allocation. 20971519 unités d’allocation au total sur le disque. 13944571 unités d’allocation disponibles sur le disque. Durée totale : 16.00 minutes (960008 ms). PS C:\Windows\system32> -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003649] [NEW] Illegal block number passed to ext2fs_test_block_bitmap
Public bug reported: Hello I am trying to understand how the three commands testb, icheck and ncheck of the debugfs command work. My goal is to use them to find all the sectors allocated to a file. For this, I created a test set consisting of a 100% full EXT4 partition containing only one file. Here are the features: mount /dev/sda9 /mnt/TEST df --block-size=512 -text4 | grep TEST /dev/sda94245641392 0 100% /mnt/TEST So I think there are only 1064 (42456-41392) unused sectors. To check it, I make this script: rm -v testb.in for ((k=1;k<42457;k++));do echo testb $k >>testb.in done debugfs -f testb.in /dev/sda9 > testb.out 2>err then I control head -2 testb.out; tail -2 testb.out ; head -2 err; tail -1 err debugfs: testb 1 Block 1 marked in use debugfs: testb 42456 Block 42456 not in use debugfs 1.46.5 (30-Dec-2021) Illegal block number passed to ext2fs_test_block_bitmap #6656 for block bitmap for /dev/sda9 Illegal block number passed to ext2fs_test_block_bitmap #42456 for block bitmap for /dev/sda9 I can only find this reported incident: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1487787 grep "Illegal block number passed to ext2fs_test_block_bitmap" err | wc -l 35801 i.e. 84% rejection. The rest of the treatment will not be good grep "marked in use" testb.out | wc -l 6522 grep "not in use" testb.out | wc -l 35934 I don't know if it's because of a missing option, misuse or malfunction of the command. thank you for looking into the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 22 16:18:03 2023 InstallationDate: Installed on 2022-02-16 (339 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-08-19 (156 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2003649 Title: Illegal block number passed to ext2fs_test_block_bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003649] Re: Illegal block number passed to ext2fs_test_block_bitmap
Hello Case with size 8 blocks. 9% of files are not identified ** Attachment added: "CR execution" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+attachment/5643029/+files/Debugfs-3.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2003649 Title: Illegal block number passed to ext2fs_test_block_bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003649] Re: Illegal block number passed to ext2fs_test_block_bitmap
Hello Case with size 16 blocks. 25% of files are not identified ** Attachment added: "CR execution" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+attachment/5643030/+files/Debugfs-2.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2003649 Title: Illegal block number passed to ext2fs_test_block_bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003649] Re: Illegal block number passed to ext2fs_test_block_bitmap
Hello Case with size 32 blocks. 21,4% of files are not identified ** Attachment added: "CR execution" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+attachment/5643031/+files/Debugfs-4.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2003649 Title: Illegal block number passed to ext2fs_test_block_bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013082] [NEW] EFI boot does not detect RAID.
Public bug reported: I installed ubuntu 22.04.2 in a raids structure. The grub.cfg files seem fine. Content of EFI grub.cfg is search.fs_uuid b9c1881f-a0b5-4fe3-b5ea-eb3d4567cfec root mduuid/d9442342aaf72e055793a60e5ed333e4 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg The boot crashes. But a can do this command mdadm --examine --scan The response is mdadm no device listed in /etc/mdadm/mdadm.conf I suspect that the EFI part does not know how to correctly assemble the RAID because during the I don't know how to transmit the crash at this precise moment. The workaround found is to make a standard EXT4 partition dedicated to booting. However, that seems abnormal to me then the EFI part proposes to boot directly on the RAID if it is not possible. Thank you for doing what is necessary to have something coherent. Good day. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 14:58:24 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2013082 Title: EFI boot does not detect RAID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2013082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013082] Re: EFI boot does not detect RAID.
The structure of the raid. ** Attachment added: "mdadm --detail /dev/md10" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2013082/+attachment/5658297/+files/raid.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2013082 Title: EFI boot does not detect RAID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2013082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
$ journalctl -f -- Logs begin at Wed 2020-01-08 00:43:00 CET. -- févr. 10 22:51:35 a pkexec[3203]: a: Executing command [USER=root] [TTY=unknown] [CWD=/home/a] [COMMAND=/usr/lib/update-notifier/package-system-locked] févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of $ journalctl -f -- Logs begin at Wed 2020-01-08 00:43:00 CET. -- févr. 10 22:51:35 a pkexec[3203]: a: Executing command [USER=root] [TTY=unknown] [CWD=/home/a] [COMMAND=/usr/lib/update-notifier/package-system-locked] févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). keysym 36 with keysym 36 (keycode f). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
