[Solved] GNOME 3 Properties Dialogue auto closing

I recently discovered that when i right click on a file and select "Properties" dialog box flashes and gone.....
what should i do to fix it.... Help Mee.......
Last edited by chamoo2000 (2012-04-24 14:45:46)

I solved it enyway....... after i run " sudo pacman -Syu" and run a full update it solved...

Similar Messages

  • [SOLVED][GNOME] What is the line for the startup sound?

    Hi!
    I removed the startup sound from GNOME.
    I don't even remember if it did work, but I press the remove button a bit too quickly and there is no confirmation box.
    Could you launch gnome-session-properties and tell me the command line for the GNOME startup sound please?
    Thanks!
    Last edited by Creak (2014-01-17 18:40:13)

    Spider.007 wrote:You're welcome! You should also mark this thread [SOLVED]
    Done!

  • Editing the properties of the closed captioning area.

    Is there a way to edit the properties of the closed captioning (CC) area.  I mean besides the number of lines and font type and size.
    For instance in a responsive design project the closed captioning runs under the X to close the CC window in the phone view.
    I know if they have a phone why would they want to see the CC, but someone has asked us to see about fixing that.

    The file extension does not matter. It is an .html file. I put it right after the existing Style:
    <style type="text/css">#initialLoading{background:url(assets/htmlimages/loader.gif) no-repeat center center;background-color:#ffffff;position:absolute;margin:auto;top:0;left:0;right:0;bottom :0;z-index:10010;}</style>
    <style>
    @media screen and (max-width: 300px) {
        #ccClose {
            display:none;
    </style>
    Also you might want to change the max-width to 400 or something. You can test in the broswer and then resizing until you hit the threshhold.

  • Cannot set resolution with gnome-display-properties

    Hey all!
    After full system update my external display does not get detected/recognized properly by gnome-display-properties
    Though before upgrade it worked just fine!
    Tried to downgrade hal and xorg-server but without any success.
    Any ideas how to fix?
    Thanks!

    I have the same problem. I do, like You, own a ASUS P4S8X motherboard and a MSI (Ti4800SE-VTD8X(MS-8900))videocard.
    Because it was a brand new system i installed everything from scratch, so installed the MSI drivers for the videocard. Afterwards i thought i that it would be better to download the latest nvidia drivers. Since that time i have the same problem with the property settings of the videocard, Ghost Recon (original and supplied version) does not work anymore as goes for liveupdate of msi.
    There is a solution but i think it is CRAP. You have to uninstall nvidia drivers and reinstall the original msi drivers.... bla bla bla... Why is it that there are a lot of known errors with msi/nvidia drivers in conjuntion with the liveupdate, supplied games and with the settings?? I would like to see a (driver)update from msi which is for mortals. I'm not the hacking and phreaking guy, and so are more. I have spent a fortune on this card so MSI get started!!!!!!

  • Dispute case auto closing

    Hi,
    I have created a dispute case on customer noted item, when i will reverse the noted item the dispute case is not auto closed, it is still in open status.
    can any one give me solution for this.
    Regards,
    Prakash

    Hi,
    I have read already but my problem is i have created a noted item for which if i post advance receipt then i will go preclosed, but when i cancel the noted item it will still be open, i need close it pre closed manually.
    regards,
    Prakash

  • Auto closing of open Purchase Orders

    hai all
    My requirement is to find all the Auto closing of open Purchase Orders which donu2019t have any more use in business transaction
    using BAPI.pls send me one sample report
    regards
    Asish.

    Hi Lebogang
    Go to the open items list under sales or purchasing reports, select PO's on the top right and then highlight all the PO's you want to close. Then right click on the grey area on top of the report and select close. This will close all at once.
    Kind regards
    Peter Juby

  • System-config-display, gnome-display-properties - inconsistent R5 U5 64bit

    Hi all,
    I have OEL Rel 5 U5 (64-bit) installed and running on an IBM x3200 which has Radeon integrated graphics, with a IBM ThinkVision LCD monitor (1280x1024 max)
    Problem I have is eventhough system-config-display lets me select 1280x1024 I can't actually get it to switch. Upon log-off/log-in, reboot, restart, etc... it still returns to 1024x768 mode.
    Running gnome-display-properties only gives me a choice of 1024x768, 800x600, or 640x480.
    I've also tried xrandr and trying to force it to 1280x1024 but it tells me I only have the 3 choices given by gnome-display-properties.
    My xorg.conf file is configured with 1280x1024, 1024x768, and 800x600 modes, so I'm baffled at where gnome-display-properties and xrandr are getting their mode choices...
    Can anyone shed some light on this?

    Based on Xorg log I'm guessing the monitor driver just will not support the higher res and apparently that's where 'gnome-display-properties' gets its info regardless of what I try in Xorg.conf.
    I'll see if I can manipulate the monitor settings and see where that gets me...
    I see the following in the log:
    (II) RADEON(0): Monitor1 EDID data ---------------------------
    (II) RADEON(0): Manufacturer: IBM Model: 29a Serial#: 16843009
    (II) RADEON(0): Year: 2003 Week: 16
    (II) RADEON(0): EDID Version: 1.3
    (II) RADEON(0): Digital Display Input
    (II) RADEON(0): Max Image Size [cm]: horiz.: 30 vert.: 23
    (II) RADEON(0): Gamma: 1.00
    (II) RADEON(0): No DPMS capabilities specified
    (II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    (II) RADEON(0): Default color space is primary color space
    (II) RADEON(0): First detailed timing is preferred mode
    (II) RADEON(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
    (II) RADEON(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
    (II) RADEON(0): Supported VESA Video Modes:
    (II) RADEON(0): 720x400@70Hz
    (II) RADEON(0): 640x480@60Hz
    (II) RADEON(0): 640x480@72Hz
    (II) RADEON(0): 640x480@75Hz
    (II) RADEON(0): 800x600@56Hz
    (II) RADEON(0): 800x600@60Hz
    (II) RADEON(0): 800x600@72Hz
    (II) RADEON(0): 800x600@75Hz
    (II) RADEON(0): 1024x768@60Hz
    (II) RADEON(0): 1024x768@70Hz
    (II) RADEON(0): 1024x768@75Hz
    (II) RADEON(0): Manufacturer's mask: 0
    (II) RADEON(0): Supported Future Video Modes:
    (II) RADEON(0): #0: hsize: 1024 vsize 768 refresh: 60 vid: 16481
    (II) RADEON(0): Supported additional Video Mode:
    (II) RADEON(0): clock: 65.0 MHz Image Size: 300 x 225 mm
    (II) RADEON(0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1344 h_border: 0
    (II) RADEON(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0
    (II) RADEON(0): Serial No: Reserved
    (II) RADEON(0): Monitor name: IBM RSA2
    (II) RADEON(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 70 kHz, PixClock max 110 MHz
    (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
    (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
    (II) RADEON(0): Validating modes on Primary head ---------
    (II) RADEON(0): DFP table revision: 3
    (II) RADEON(0): Panel infos found from DDC detailed: 1024x768
    (II) RADEON(0): Valid Mode from Detailed timing table: 1024x768
    (II) RADEON(0): Valid Mode from standard timing table: 1024x768
    (II) RADEON(0): Valid Mode from established timing table: 1024x768
    (II) RADEON(0): Valid Mode from established timing table: 1024x768
    (II) RADEON(0): Valid Mode from established timing table: 1024x768
    (II) RADEON(0): Valid Mode from established timing table: 800x600
    (II) RADEON(0): Valid Mode from established timing table: 800x600
    (II) RADEON(0): Valid Mode from established timing table: 800x600
    (II) RADEON(0): Valid Mode from established timing table: 800x600
    (II) RADEON(0): Valid Mode from established timing table: 640x480
    (II) RADEON(0): Valid Mode from established timing table: 640x480
    (II) RADEON(0): Valid Mode from established timing table: 640x480
    (II) RADEON(0): Total of 12 mode(s) found.
    Here's video info from lspci:
    0a:04.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) (prog-if 00 [VGA controller])
         Subsystem: IBM Unknown device 0325
         Flags: bus master, stepping, fast Back2Back, medium devsel, latency 66, IRQ 11
         Memory at d8000000 (32-bit, prefetchable) [size=128M]
         I/O ports at 6000 [size=256]
         Memory at d0800000 (32-bit, non-prefetchable) [size=64K]
         [virtual] Expansion ROM at d0820000 [disabled] [size=128K]
         Capabilities: [50] Power Management version 2
    Xorg.conf:
    # Xorg configuration created by system-config-display
    Section "ServerLayout"
         Identifier "single head configuration"
         Screen 0 "Screen0" 0 0
         InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "InputDevice"
         Identifier "Keyboard0"
         Driver "kbd"
         Option     "XkbModel" "pc105"
         Option     "XkbLayout" "us"
    EndSection
    Section "Monitor"
    ### Comment all HorizSync and VertSync values to use DDC:
    ### Comment all HorizSync and VertSync values to use DDC:
         Identifier "Monitor0"
         ModelName "LCD Panel 1280x1024"
    ### Comment all HorizSync and VertSync values to use DDC:
         HorizSync 31.5 - 64.0
         VertRefresh 56.0 - 65.0
         Option     "dpms"
    EndSection
    Section "Device"
         Identifier "Videocard0"
         Driver "radeon"
         Option     "AccelMethod" "UXA"
    EndSection
    Section "Screen"
         Identifier "Screen0"
         Device "Videocard0"
         Monitor "Monitor0"
         DefaultDepth 16
         SubSection "Display"
              Viewport 0 0
              Depth 24
              Modes "1280x1024" "1024x768" "800x600"
         EndSubSection
         SubSection "Display"
              Viewport 0 0
              Depth 16
              Modes "1280x1024" "1024x768" "800x600"
         EndSubSection
    EndSection

  • Auto closing curly braces

    Is there any options in Dreamweaver 8 that is capable of auto
    closing curly braces and parenthesis like I see in a lot of code
    editors. I'm trying to use the coding environment. Thanks.

    Nope. Please suggest this to the dev team, though -
    http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "monfreex" <[email protected]> wrote in
    message
    news:evpm3j$f5s$[email protected]..
    > Is there any options in Dreamweaver 8 that is capable of
    auto closing
    > curly braces and parenthesis like I see in a lot of code
    editors. I'm
    > trying to use the coding environment. Thanks.

  • Auto closing of dispute cases--only for some company codes

    Hi
    We have activated dispute management for several company codes in our system. The auto closing of dispute cases also has been activated in status management. Cases are automatically closed by the system (through a batch job) when the last disputed object is cleared.
    Now there is a requirement to deactivate auto closing only for some company codes. They want to close cases manually in these company codes.
    Is this possible and if so how?
    Regards
    Raj.

    You cannot deselect at a company code level.
    Can we go through you proposed process.
    So you have a dispute for $100.
    The customer pays it and the dispute closes.
    Then the customer calls up and says they have an issue with the invoice they paid previously.
    I have seen this happen before but there was a little twist
    1 - The customer raised a debit note against the client for the issue that they had. The original invoice is cleared but a debit note is created and then disputed and processed. So you can close the original dispute and create a new dispute against the debit note
    2 - The customer paid the wrong invoice. The dispute was closed. However to rectify the miss allocation the clearing document will be reversed meaning the dispute is "re-opened" and can be processed.
    I am unaware of any other requirement for a customer to "re-dispute" a paid item in SAP.

  • Gnome Keyboard Properties invalid pointer

    I keep getting
    *** glibc detected *** free(): invalid pointer: 0xb74ae9a0 ***
    everytime I try to run gnome-keyboard-properties.
    On a side note, the weather report applet seems to only list North America and the Middle East as possible locations, and it seems that Alaska is the only state in the US.
    Anyone else have these problems or is it only occuring on my computers?

    I updated gnome-applets, so the weather applet should work indeed
    The gnome-keyboard-properties thingy was a bug in libxklavier 1.0.4 which returns a static declared variable as a pointer, which breaks with the new glibc. Fixed that with a patch kindly grabbed from gentoo CVS

  • Gnome Appearance Properties error

    I just do a clean install and got this error from Gnome.
    The program 'gnome-appearance-properties' received an X Window System error.
    This probably reflects a bug in the program.
    The error was 'BadAlloc (insufficient resources for operation)'.
    (Details: serial 467 error_code 11 request_code 53 minor_code 0)
    (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() function.)
    Can someone help me?

    I encounter the same problem now, but this thread give me a solution: https://bugs.launchpad.net/ubuntu/+sour … bug/386573
    quote:
    I was told in private email that this behaviour is due to the /desktop/gnome/font_rendering/dpi key being an integer rather than a float.
    You can do something like this to repair:
    (find out existing value):
    $ gconftool-2 --get /desktop/gnome/font_rendering/dpi
    (reset to float)
    $ gconftool-2 --set --type float /desktop/gnome/font_rendering/dpi [your value]
    (unset entirely)
    $ gconftool-2 --unset /desktop/gnome/font_rendering/dpi
    This does seem to repair the problem (prior to unsetting my DPI, I was still getting the mis-rendering at least until today, using Lucid).

  • [SOLVED][GNOME] Pulseaudio doesn't start

    Hey,
    On cinnamon, pulseaudio starts on startup but with gnome3.8/3.6 pulseaudio doesn't start.
    I always need to start it manually via `pulseaudio --start`.
    Does someone know how to fix this?
    Thanks in advance!
    Last edited by sh4nks (2013-05-01 07:04:20)

    ijanos wrote:Run gnome-session-properties and enable "PulseAudio Sound System"
    Thanks!
    But there wasn't such an entry so I have to add by myself
    If someone is curious how I added it..:
    1. Run `gnome-session-propertiers`
    2. Click on `Add`
    3. Fill in
    `Name` with `PulseAudio Sound System` or something like that and
    `Command` with `start-pulseaudio-x11`
    Thats it!
    Last edited by sh4nks (2013-05-01 07:07:03)

  • Safari auto closing/shutdown

    Hi is anyone else experiencing their safari auto closing/shutdown during use? I looks around and saw it may be a memory thing but safari is all that's running and I have the 30gb iPad gen3  with over 10gb available. Any help would be great

    HKWOY-
    Your symptoms sound more serious, as if there was an internal electrical problem with your iPad.  I suggest you show it to an Apple Store Genius.  If the Genius can not fix it, you may get a replacement iPad.
    If there is no Apple Store near you, look for an Apple Authorized Repair Center.  There may be one in your city.  <Apple Authorized Repair Centers>
    Fred

  • Gnome-font-properties

    I recently switched my desktop machine over to Arch after being a long time Slackware user.  After installing Gnome 2.6 I'm experiencing problems with gnome-font-properties.  It flat out won't start, it crashes every single time.  Starting it from terminal gives the following error
    [john@metatron ~]$ gnome-font-properties
    (gnome-font-properties:1782): GConf-CRITICAL **: file gconf-value.c: line 837 (gconf_value_get_string): assertion `value->type == GCONF_VALUE_STRING' failed
    ** (gnome-font-properties:1782): CRITICAL **: file fonts.c: line 824 (pango_font_description_from_string): assertion `str != NULL' failed
    Any ideas?

    just looking at the error text will give away what's wrong:
    "assertion 'str != NULL' failed" -> if this fails, it implies a string is NULL
    so some string is null, let's look at the previous error:
    "gconf-value.c: assertion 'value->type == GCONF_VALUE_STRING' failed" -> if this fails somethign which should be a string is not a string (meaning null most likely)
    where did this error come from? gconf-value.c : most likely the gconf parsing routines.
    your gnome configuration is borked.... if you messed with it by hand, try and fix it, or just get one of the configuration GUIs

  • Gnome-appearance-properties crashing

    Yestarday I noticed that I can't change wallpaper, theme or anything else in gnome because of gnome-appearance-properties crashing.
    It opens and suddenly bug buddy shows. Running it in console gives me this output:
    bash-3.2$ gnome-appearance-properties
    5e9dc123-1fd3-73fa-0bc67308-32b8d538 is dumped
    Anyone knows what I can do about it?
    Last edited by Szelek (2008-12-30 13:12:44)

    Szelek wrote:
    Yestarday I noticed that I can't change wallpaper, theme or anything else in gnome because of gnome-appearance-properties crashing.
    It opens and suddenly bug buddy shows. Running it in console gives me this output:
    bash-3.2$ gnome-appearance-properties
    5e9dc123-1fd3-73fa-0bc67308-32b8d538 is dumped
    Anyone knows what I can do about it?
    Perhaps you installed some packages that were corrupted? A redownload + reinstall might do the trick. What repositories are you using? I'm using testing and everything works here.

Maybe you are looking for