[Bug 1260629] New: [abrt] eclipse-pydev: QBasicAtomicOps<4>::deref<int>(): python2.7 killed by SIGSEGV
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1260629
Bug ID: 1260629
Summary: [abrt] eclipse-pydev:
QBasicAtomicOps<4>::deref<int>(): python2.7 killed by
SIGSEGV
Product: Fedora
Version: 23
Component: eclipse-pydev
Assignee: akurtako(a)redhat.com
Reporter: akurtako(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jjohnstn(a)redhat.com, nathaniel(a)natemccallum.com
Version-Release number of selected component:
eclipse-pydev-4.3.0-1.fc23
Additional info:
reporter: libreport-2.6.2
backtrace_rating: 4
cmdline: /usr/bin/python -u
/usr/lib64/eclipse/dropins/pydev-core/eclipse/plugins/org.python.pydev_4.3.0.201508210800/pysrc/pycompletionserver.py
43890
crash_function: QBasicAtomicOps<4>::deref<int>
executable: /usr/bin/python2.7
global_pid: 5622
kernel: 4.2.0-300.fc23.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 QBasicAtomicOps<4>::deref<int> at ../../src/corelib/arch/qatomic_x86.h:219
#1 QBasicAtomicInteger<int>::deref at
../../src/corelib/thread/qbasicatomic.h:130
#2 QtPrivate::RefCount::deref at ../../src/corelib/tools/qrefcount.h:67
#3 QByteArray::~QByteArray at ../../src/corelib/tools/qbytearray.h:459
#4 rawStringData at kernel/qmetaobject.cpp:156
#5 objectClassName at kernel/qmetaobject.cpp:301
#6 QMetaObject::className at kernel/qmetaobject.cpp:311
#7 QMetaTypeIdQObject<QWidget*, 8>::qt_metatype_id at
../../src/corelib/kernel/qmetatype.h:1760
#8 QMetaTypeId2<QWidget*>::qt_metatype_id at
../../src/corelib/kernel/qmetatype.h:1584
#9 qMetaTypeId<QWidget*> at ../../src/corelib/kernel/qmetatype.h:1726
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aSXJ98THP2&a=cc_unsubscribe
7 years, 10 months
[Bug 1202238] New: eclipse: Dropin cache not updated completely
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1202238
Bug ID: 1202238
Summary: eclipse: Dropin cache not updated completely
Product: Fedora
Version: rawhide
Component: eclipse
Assignee: rgrunber(a)redhat.com
Reporter: mizdebsk(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, msimacek(a)redhat.com,
rgrunber(a)redhat.com, swagiaal(a)redhat.com
Description of problem:
It looks like Eclipse Mars is caching dropins in ~/.eclipse and not refreshing
this cache entirely after dropin change (eg. package update).
Version-Release number of selected component (if applicable):
4.5.0-0.4.git201503030800
Steps to Reproduce:
1. rm -rf ~/.eclipse
2. install eclipse-m2e-core-1.6.0-0.1.fc23.noarch
3. run eclipse -data /tmp/new-workspace
4. close eclipse after it starts
5. update m2e to eclipse-m2e-core-1.6.0-0.2.fc23.noarch
6. re-run eclipse -data /tmp/new-workspace
Actual results:
There are a lot of exceptions printed on stdout, such as:
java.lang.RuntimeException: Unable to aquire PluginConverter service during
generation for:
/usr/share/eclipse/dropins/m2e-core/eclipse/plugins/org.eclipse.m2e.scm_1.6.0.20150312-2022.jar
These paths are refering to old m2e bundles from 1.6.0-0.1 which were removed
during eclipse-m2e-core package update.
Removing ~/.eclipse gets rid of these exceptions, so it looks like old paths
are cached there.
M2E works after update, so this is not critical. However accumulating warnings
like that clutters Eclipse stdout and makes noticing real problems more
difficult.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6eGilMjmu9&a=cc_unsubscribe
7 years, 11 months
[Bug 1210898] New: Eclipse tries to use non-existent Mozilla (xulrunner) browser
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1210898
Bug ID: 1210898
Summary: Eclipse tries to use non-existent Mozilla (xulrunner)
browser
Product: Fedora
Version: 21
Component: eclipse
Severity: high
Priority: high
Assignee: akurtako(a)redhat.com
Reporter: rgrunber(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, msimacek(a)redhat.com,
rgrunber(a)redhat.com, swagiaal(a)redhat.com
It looks like the user has some jboss-tools plugins installed that ultimately
try to bring up the browser. When it come sup, the user sees errors regarding
missing libswt-xulrunner. The call would seem to originate from
https://github.com/jbosstools/jbosstools-base/blob/master/runtime/plugins...
.
The other interesting part to note is that the BrowserFactory is returning the
Mozilla class, which could only happen if WebKit.IsInstalled () is false.
11:31 < k170> I keep getting an error in eclipse (luna), every time I try to
download and install a new server runtime.
11:33 < k170> The error states that it cannot find libswt-xulrunner-gtk.so
11:33 < k170> as well as libswt-xulrunner-gtk-4430.so
11:34 < k170> I'm running fedora 21 64bit and I have no idea how to install
those files
!ENTRY org.eclipse.ui 4 0 2015-04-09 21:52:39.606
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTError: No more handles (java.lang.UnsatisfiedLinkError:
Could not load SWT library. Reasons:
no swt-xulrunner-gtk-4430 in java.library.path
no swt-xulrunner-gtk in java.library.path
Can't load library:
/home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4430.so
Can't load library:
/home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so
)
at org.eclipse.swt.SWT.error(SWT.java:4467)
at org.eclipse.swt.SWT.error(SWT.java:4356)
at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2745)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:670)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
at
org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment.createComposite(DownloadRuntimeLicenseFragment.java:90)
at
org.jboss.tools.foundation.ui.xpl.taskwizard.TaskWizardPage.createControl(TaskWizardPage.java:44)
at
org.jboss.tools.foundation.ui.xpl.taskwizard.TaskWizard.createPageControls(TaskWizard.java:401)
at
org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:759)
at
org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:622)
at org.eclipse.jface.window.Window.create(Window.java:435)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
at org.eclipse.jface.window.Window.open(Window.java:797)
at
org.jboss.tools.as.runtimes.integration.ui.composites.DownloadRuntimeHomeComposite$DownloadAndInstallListener.widgetSelected(DownloadRuntimeHomeComposite.java:75)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526)
at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:372)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2078)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5539)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4668)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9106)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2477)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3407)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
at org.eclipse.jface.window.Window.open(Window.java:808)
at
org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
no swt-xulrunner-gtk-4430 in java.library.path
no swt-xulrunner-gtk in java.library.path
Can't load library:
/home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4430.so
Can't load library:
/home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:321)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:242)
at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2743)
... 61 more
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Hc32FZ0PMz&a=cc_unsubscribe
7 years, 11 months
[Bug 1226615] New: Quick Outline (Ctrl+O) doesn't work (Outline is closed immediately)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1226615
Bug ID: 1226615
Summary: Quick Outline (Ctrl+O) doesn't work (Outline is closed
immediately)
Product: Fedora
Version: 22
Component: eclipse-cdt
Assignee: jjohnstn(a)redhat.com
Reporter: hedayatv(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com,
rgrunber(a)redhat.com
Description of problem:
Eclipse in Fedora 22 has many problems (actually, mostly about its color theme
which is unreadable/unnoticable in some places), but one of the most annoying
ones is that the Quick Outline view (Ctrl+O) doesn't work. It does open the
outline window, but it is closed immediately. Also, it has a black background
while it was yellow (IIRC) in F21; but this is not that important.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=C5gKD2cpuS&a=cc_unsubscribe
8 years
[Bug 1196736] New: eclipse gui white-unreadable text - changing colors too
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1196736
Bug ID: 1196736
Summary: eclipse gui white-unreadable text - changing colors
too
Product: Fedora
Version: 22
Component: eclipse-pdt
Severity: high
Assignee: mat.booth(a)redhat.com
Reporter: peljasz(a)yahoo.co.uk
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org,
mat.booth(a)redhat.com
Created attachment 995677
--> https://bugzilla.redhat.com/attachment.cgi?id=995677&action=edit
snapshot of white text
Description of problem:
please take a look a the attached snap, I'd happy it says more than if I tried
to explain.
Also, the yellow background of the second windows changes to black, is yellow
only the first time is invoked, every subsequent invocation is black.
The white text is most troublesome as you cannot see what is says, row that
gets focus changes to white text.
I thought it was configurable somewhere but failed to find settings if there
are any.
Version-Release number of selected component (if applicable):
eclipse-emf-runtime-2.10.1-3.fc22.noarch
eclipse-xsd-2.10.1-3.fc22.noarch
eclipse-pdt-3.3.1-5.fc22.noarch
eclipse-equinox-osgi-4.4.1-17.fc22.x86_64
eclipse-pde-4.4.1-17.fc22.x86_64
eclipse-gef-3.9.101-3.fc22.noarch
eclipse-subclipse-1.10.5-2.fc22.noarch
eclipse-jdt-4.4.1-17.fc22.x86_64
eclipse-webtools-common-core-3.6.2-1.fc22.noarch
eclipse-dltk-5.1.0-6.fc22.noarch
eclipse-webtools-sourceediting-3.6.2-1.fc22.noarch
eclipse-rse-3.6.0-4.fc22.noarch
eclipse-platform-4.4.1-17.fc22.x86_64
eclipse-webtools-servertools-core-3.6.2-1.fc22.noarch
eclipse-webtools-common-3.6.2-1.fc22.noarch
eclipse-filesystem-1.0-3.fc22.x86_64
eclipse-dltk-rse-5.1.0-6.fc22.noarch
eclipse-swt-4.4.1-17.fc22.x86_64
eclipse-subclipse-graph-1.10.5-2.fc22.noarch
eclipse-emf-core-2.10.1-3.fc22.x86_64
eclipse-mylyn-3.14.2-1.fc22.noarch
eclipse-webtools-servertools-3.6.2-1.fc22.noarch
eclipse-dltk-mylyn-5.1.0-6.fc22.noarch
eclipse-ecf-core-3.9.2-2.fc22.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=JkxqBUsj6O&a=cc_unsubscribe
8 years, 1 month
[Bug 1267411] New: lucene-5.3.1 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1267411
Bug ID: 1267411
Summary: lucene-5.3.1 is available
Product: Fedora
Version: rawhide
Component: lucene
Keywords: FutureFeature, Triaged
Assignee: akurtako(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
hicham.haouari(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
msimacek(a)redhat.com, puntogil(a)libero.it,
rgrunber(a)redhat.com
Latest upstream release: 5.3.1
Current version/release in rawhide: 5.3.0-1.fc24
URL: http://lucene.apache.org/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=FtPNTM1wHS&a=cc_unsubscribe
8 years, 2 months
[Bug 1263580] New: An internal error occurred during: "Repository registry initialization".
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1263580
Bug ID: 1263580
Summary: An internal error occurred during: "Repository
registry initialization".
Product: Fedora
Version: 23
Component: eclipse-m2e-core
Assignee: gerard(a)ryan.lt
Reporter: sgehwolf(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt,
mizdebsk(a)redhat.com
Description of problem:
When I load up my workspace which includes maven projects an error dialog pops
up with the following error: "An internal error occurred during: "Repository
registry initialization".
Version-Release number of selected component (if applicable):
eclipse-m2e-core-1.6.1-1.fc23.noarch
How reproducible:
100%
Steps to Reproduce:
1. Import a maven project using Import => Maven => Existing Maven projects
2. Observe the error dialog appearing.
3. Error dialog appears every time the same workspace is loaded.
Actual results:
Error dialog appearing.
Expected results:
No error dialog. Either ignore Lucene version used or discover the lucene
version in use somehow.
Additional info:
Stack trace from the error log:
java.lang.NoSuchFieldError: LUCENE_36
at
org.apache.maven.index.context.NexusIndexWriter.defaultConfig(NexusIndexWriter.java:60)
at
org.apache.maven.index.context.DefaultIndexingContext.getWriterConfig(DefaultIndexingContext.java:512)
at
org.apache.maven.index.context.DefaultIndexingContext.openAndWarmup(DefaultIndexingContext.java:500)
at
org.apache.maven.index.context.DefaultIndexingContext.prepareIndex(DefaultIndexingContext.java:201)
at
org.apache.maven.index.context.DefaultIndexingContext.<init>(DefaultIndexingContext.java:150)
at
org.apache.maven.index.context.DefaultIndexingContext.<init>(DefaultIndexingContext.java:170)
at
org.apache.maven.index.DefaultNexusIndexer.addIndexingContextForced(DefaultNexusIndexer.java:147)
at
org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.createIndexingContext(NexusIndexManager.java:964)
at
org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.setIndexDetails(NexusIndexManager.java:931)
at
org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.repositoryAdded(NexusIndexManager.java:877)
at
org.eclipse.m2e.core.internal.repository.RepositoryRegistry.addRepository(RepositoryRegistry.java:163)
at
org.eclipse.m2e.core.internal.repository.RepositoryRegistry.updateRegistry(RepositoryRegistry.java:236)
at
org.eclipse.m2e.core.internal.repository.RepositoryRegistryUpdateJob.run(RepositoryRegistryUpdateJob.java:47)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
$ rpm -q lucene
lucene-5.3.0-1.fc23.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9B3IsLHqaZ&a=cc_unsubscribe
8 years, 4 months
[Bug 1222165] New: Xdebug step not working
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1222165
Bug ID: 1222165
Summary: Xdebug step not working
Product: Fedora
Version: 22
Component: eclipse-pdt
Assignee: mat.booth(a)redhat.com
Reporter: dev002(a)pas-world.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org,
mat.booth(a)redhat.com
Description of problem:
Xdebug step not working
Version-Release number of selected component (if applicable):
eclipse-platform-4.4.2-5.fc22.x86_64
eclipse-pdt-3.3.1-5.fc22.noarch
php-pecl-xdebug-2.3.2-1.fc22.x86_64
How reproducible:
Steps to Reproduce:
1. Open PHP file
2. Configure Debug with Xdebug
3. Try step line to line
4. PDT window does not refresh the change of line.
Actual results:
Debug not working
Expected results:
Show line of debug step.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YQUSiccCDh&a=cc_unsubscribe
8 years, 5 months