Bug 388629 - update failure
Summary: update failure
Status: RESOLVED NOT A BUG
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-06 18:30 UTC by Etienne Saliez
Modified: 2018-08-29 19:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Etienne Saliez 2018-01-06 18:30:43 UTC
update failure when the program "discover" was trying to update " apport(2.20.1-Oubuntu2.15)

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/plasma-discover...(no debugging symbols found)...done.
Attaching to program: /usr/bin/plasma-discover, process 5664
Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
(gdb)
Comment 1 Nate Graham 2018-01-06 23:22:14 UTC
I'm afraid there isn't enough information here to let us debug the issue. Your gdb attach seems to have failed. If you can reproduce the issue, please do the following:
1. Launch Discover from within a gdb session before  Discover is already running and before trying the update and 
2. Perform the update in Discover
3. Once the problem occurs, save the console output and enter it here
4. If discover crashes or hangs, get a backtrace by typing `bt` in the gdb command line and entering the output here
Comment 2 Christoph Feck 2018-01-17 23:48:14 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Christoph Feck 2018-01-30 00:55:41 UTC
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 Christoph Feck 2018-02-14 15:23:37 UTC
No response; changing status. If you have new information, please add a comment.