RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1272544 - keepassx grep window
Summary: keepassx grep window
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qt
Version: 6.7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-16 17:11 UTC by jason.prokopowich
Modified: 2017-12-06 10:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:50:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
actual window (29.09 KB, image/png)
2015-10-16 17:11 UTC, jason.prokopowich
no flags Details
ipcs_out (320.04 KB, text/plain)
2015-10-19 16:36 UTC, jason.prokopowich
no flags Details
grep output (454.98 KB, text/plain)
2015-10-21 15:13 UTC, jason.prokopowich
no flags Details
xrestop attached. (16.34 KB, text/plain)
2015-10-23 11:56 UTC, jason.prokopowich
no flags Details

Description jason.prokopowich 2015-10-16 17:11:10 UTC
Created attachment 1083778 [details]
actual window

Description of problem:
When trying to use keepassx the window malfunctions by becoming grep with missing input blocks.


Version-Release number of selected component (if applicable):
keepassx.x86_64  0.4.3-7.el6

How reproducible:
starting keepassx via commandline or via menu.

Steps to Reproduce:
1. start keepassx
2.
3.

Actual results:
grey windows missing input blocks and malfunctioning dropdown menus.

errors,
$ keepassx

(<unknown>:18307): Gdk-WARNING **: shmget failed: error 28 (No space left on device)
QNativeImage: Unable to attach to shared memory segment. 
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9


note:
$ df -h
Filesystem           Size  Used Avail Use% Mounted on
/dev/mapper/vg-root   39G   24G   13G  65% /
tmpfs                3.8G  680K  3.8G   1% /dev/shm
/dev/sda1            976M  317M  609M  35% /boot
/dev/mapper/vg-log   976M   89M  837M  10% /var/log


Expected results:
To work as expected.

Additional info:
starting the app via the following seems to resolve the issue,
$ QT_X11_NO_MITSHM=1 keepassx

Comment 1 Orion Poplawski 2015-10-16 17:30:58 UTC
What does:

ipcs -ml
ipcs -mu
ipcs -m

report?  Does a reboot clear things up?

Comment 2 jason.prokopowich 2015-10-19 16:36:48 UTC
Created attachment 1084459 [details]
ipcs_out

Comment 3 jason.prokopowich 2015-10-19 16:37:33 UTC
# ipcs -ml

------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 67108864
max total shared memory (kbytes) = 17179869184
min seg size (bytes) = 1

# ipcs -mu

------ Shared Memory Status --------
segments allocated 4095
pages allocated 841907
pages resident  1931
pages swapped   0
Swap performance: 0 attempts	 0 successes

# ipcs -m
*** see attached***

Comment 4 jason.prokopowich 2015-10-19 16:38:29 UTC
Rebooted once with no change.

Comment 5 Orion Poplawski 2015-10-20 01:59:51 UTC
Well, that's definitely the issue - you're out of shared memory segments (4095 allocated out of a max of 4096).   Now to figure out what is allocating them.  Seems like we can do:

grep /SYSV /proc/*/maps

and perhaps see what process is sucking up lots of shared memory segments.

Comment 6 jason.prokopowich 2015-10-21 15:13:23 UTC
Created attachment 1085199 [details]
grep output

I have attached the requested output.

Comment 7 Orion Poplawski 2015-10-21 15:15:01 UTC
What is process 3707?  (ps -fp 3707)

Comment 8 jason.prokopowich 2015-10-22 12:32:18 UTC
root      3707  3703  0 Oct14 tty7     01:18:19 /usr/bin/Xorg :1 -br -verbose -audit 4 -auth /var/run/gdm/auth-for-gdm-YiInvc/database -nolisten tcp

Comment 9 Orion Poplawski 2015-10-22 16:07:42 UTC
Likely a Qt issue.  Output of "xrestop -b -m 1" may be helpful.

Comment 11 jason.prokopowich 2015-10-23 11:56:06 UTC
Created attachment 1085820 [details]
xrestop attached.

Comment 12 Jan Kurik 2017-12-06 10:50:44 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.