Bug 28657 - lector memory bad function
Summary: lector memory bad function
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
: 28658 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-03-27 01:35 CET by Josè Juan Peña Leal
Modified: 2021-04-20 09:56 CEST (History)
2 users (show)

See Also:
Source RPM: rpmdrake-6.32-1.mga8
CVE:
Status comment:


Attachments

Description Josè Juan Peña Leal 2021-03-27 01:35:48 CET
Theme name: Adwaita
Kernel version = 5.10.25-desktop-1.mga8
Distribution=Mageia release 8 (Official) for x86_64
CPU=AMD Phenom(tm) II N950 Quad-Core Processor
Comment 1 Morgan Leijström 2021-03-27 12:08:54 CET
*** Bug 28658 has been marked as a duplicate of this bug. ***
Comment 2 Morgan Leijström 2021-03-27 12:10:59 CET
Please I don't understand.
Is this a message you get when starting rpmdrake from command line?
What more happens or fails?
Comment 3 Lewis Smith 2021-03-27 21:46:22 CET
Yes, you Josè have said effectively nothing at all about the bug you are trying to report. To repeat Morgan: please give details of what you are doing, what exactly happens. Is it repeatable, or was it one-off?
To give a brief idea of your system, please do:
 $ inxi -Sxx
We might ask for additional information once we have an idea of what is going wrong.

CC: (none) => lewyssmith
Status: NEW => NEEDINFO

Comment 4 Aurelien Oudelet 2021-04-03 17:15:12 CEST
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

CC: (none) => ouaurelien
Keywords: (none) => NEEDINFO

Comment 5 Aurelien Oudelet 2021-04-20 09:56:48 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEEDINFO => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.