Bug 363679 - muon update manager crashes on segmentation fault during startup
Summary: muon update manager crashes on segmentation fault during startup
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: Updates (other bugs)
Version First Reported In: unspecified
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-29 22:10 UTC by mabbott131
Modified: 2016-06-01 15:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description mabbott131 2016-05-29 22:10:26 UTC 
Anytime the muon update manager is started, the application window opens but crashes before completely starting.  The initial run crashes after the busy icon spins for a while indicating (I assume) that it was updating the package indexes.  Subsequent runs crash immediately after the window appears presumably because the index is already up to date. 

Reproducible: Always

Steps to Reproduce:
1. run muon-updater, from the command line or from a launcher
2.
3.

Actual Results:  
Segmentation fault (core dumped)


From syslog:
May 29 16:57:04 meerkat kernel: [ 1379.166520] muon-updater[3141]: segfault at 20 ip 0000000000000020 sp 00007ffc57833f98 error 14 in muon-updater[4
00000+1e000]


From /var/crash/_usr_bin_muon-updater.1000.crash:

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Sun May 29 16:30:46 2016
DistroRelease: Ubuntu 15.10
ExecutablePath: /usr/bin/muon-updater
ExecutableTimestamp: 1443799015
ProcCmdline: /usr/bin/muon-updater
ProcCwd: /home/mark
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcMaps:
 00400000-0041e000 r-xp 00000000 08:09 1056358                            /usr/bin/muon-updater

 [snip]

ProcStatus:
 Name:  muon-updater
 State: S (sleeping)
 Tgid:  7734
 Ngid:  0
 Pid:   7734
 PPid:  1888
 TracerPid:     0
 Uid:   1000    1000    1000    1000
 Gid:   1000    1000    1000    1000
 FDSize:        128
 Groups:        4 24 27 30 46 109 125 1000 
 NStgid:        7734
 NSpid: 7734
 NSpgid:        1815
 NSsid: 1815
 VmPeak:          878672 kB
 VmSize:          838404 kB
 VmLck:        0 kB
 VmPin:        0 kB
 VmHWM:   189648 kB
 VmRSS:   189648 kB
 VmData:          337312 kB
 VmStk:      136 kB
 VmExe:      120 kB
 VmLib:   123044 kB
 VmPTE:     1076 kB
 VmPMD:       16 kB
 VmSwap:               0 kB
 Threads:       5
 SigQ:  0/63438
 SigPnd:        0000000000000000
 ShdPnd:        0000000000000000
 SigBlk:        0000000000000000
 SigIgn:        0000000000001000
 SigCgt:        0000000180010000
 CapInh:        0000000000000000
 CapPrm:        0000000000000000
 CapEff:        0000000000000000
 CapBnd:        0000003fffffffff
 Seccomp:       0
 Cpus_allowed:  ff
 Cpus_allowed_list:     0-7
 Mems_allowed:  00000000,00000001
 Mems_allowed_list:     0
 voluntary_ctxt_switches:       1105
 nonvoluntary_ctxt_switches:    13
Signal: 11
Uname: Linux 4.2.0-36-generic x86_64
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_LogindSession: 2
CoreDump: base64

[snip]
Comment 1 Aleix Pol 2016-05-31 13:29:00 UTC 
Can you check again if it works? We've had some issues in our OCS servers.
Comment 2 Ron St. Denis 2016-05-31 18:24:59 UTC 
(In reply to Aleix Pol from comment #1)
> Can you check again if it works? We've had some issues in our OCS servers.

Although I'm not the original submitter, I experienced the same issue yesterday and it is working fine today, so I'm guessing that it was in fact a problem with your OCS servers.  Thank you...
Comment 3 mabbott131 2016-05-31 18:40:09 UTC 
I just tried it and it is now working properly.  Thanks!