Bug 21114 - doing a "urpme --auto-orphans" break konqueror
Summary: doing a "urpme --auto-orphans" break konqueror
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2017-06-19 18:24 CEST by Robert Courtright
Modified: 2021-05-17 01:15 CEST (History)
2 users (show)

See Also:
Source RPM: konqueror-16.12.3-1.mga6
CVE:
Status comment:

Attachments
Log file as requested (123.57 KB, text/plain)
2017-06-20 02:00 CEST, Robert Courtright 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Robert Courtright 2017-06-19 18:24:24 CEST 
Description of problem:if "urpme --auto-orphans" is used tabs no longer work in konqueror. It crashes it


Version-Release number of selected component (if applicable):
konqueror-16.12.3-1.mga6

How reproducible: every time


Steps to Reproduce:
1. Freash install of Cauldron
2. Check to make sure that knoqueror works as nornal
3. type in urpme --auto-orphans
4. confirm that when using tabs in konqueror it crashes
Comment 1 Marja Van Waes 2017-06-19 22:24:17 CEST 
Please attach the journalctl output from the time when you ran urpme --auto-orphans, run as root (adjust times and date as needed):

  journalctl --since="2017-06-19 08:00" --until="2017-06-19 08:30" > log.txt

and attach log.txt to this bug report.

Assignee: bugsquad => kde
Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 2 katnatek 2017-06-20 00:37:51 CEST 
Always take care of what be uninstalled by urpme --auto-orphans
https://wiki.mageia.org/en/Removing_packages#Warning
please provide also the output of running konqueror in console.

CC: (none) => j.alberto.vc

Comment 3 Robert Courtright 2017-06-20 02:00:57 CEST 
Created attachment 9430 [details]
Log file as requested
Comment 4 Aurelien Oudelet 2021-05-17 01:15:44 CEST 
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.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.