obconf crashed with SIGSEGV in main()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| obconf (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Desktop Pager settings doesn't work after upgrade to Ubuntu 14.10.
To reproduce:
- Add "Desktop Pager" to LXDE panel,
- Right click on Desktop Pager in the panel or click on "Edit" button in the Panel applets list.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: obconf 1:2.0.4+
ProcVersionSign
Uname: Linux 3.16.0-22-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.7-0ubuntu6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: LXDE
Date: Wed Oct 15 13:09:36 2014
ExecutablePath: /usr/bin/obconf
InstallationDate: Installed on 2012-11-04 (709 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
ProcCmdline: obconf --tab 6
SegvAnalysis:
Segfault happened at: 0x7f46c8a82a57: movzbl 0x0(%r13),%r14d
PC (0x7f46c8a82a57) ok
source "0x0(%r13)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%r14d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: obconf
Stacktrace:
#0 0x00007f46c8a82a57 in ?? () from /lib/x86_
No symbol table info available.
#1 0x0000000000406551 in main ()
No symbol table info available.
StacktraceTop:
?? () from /lib/x86_
main ()
Title: obconf crashed with SIGSEGV in main()
UpgradeStatus: Upgraded to utopic on 2014-10-07 (7 days ago)
UserGroups: adm audio cdrom dip fax fuse lpadmin netdev plugdev sambashare scanner sudo vboxusers video
| jcuenca (jacquescuenca) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1272834, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.