No native resolution of 1366x768 in gnome resolution manager..

I kinda have a problem..My computer's monitor is an acer monitor and its configured right in the xserver (Brand name and everything recognized) but in the gnome monitor manager it does not give me a resolution of 1366x768 which is my monitors native resolution, which leads to poor image quality on the monitor..can anyone tell me how to get 1366x768 as a resolution option?

Maybe you need to make a modeline to force the resolution? I did something like that with my TV.
Here is a website that explains a bit about it, and also a calculator to actually calculate the modeline for you.
http://www.arachnoid.com/modelines/
The part I changed in my Xorg conf is
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
Option "ExactModeTimingsDVI" "True"
# HorizSync 27.0-60.0
# VertRefresh 60
#ModeLine "720p" 114.47 1280 1312 1744 1776 720 733 743 757
Modeline "1280x720@60" 73.78 1280 1312 1592 1624 720 735 742 757
Modeline "1280x768@60" 79.75 1280 1312 1608 1640 768 783 791 807
Modeline "1152x864@30" 36.95 1152 1184 1320 1352 864 883 888 908
EndSection
Hope this can help you on your way.

Similar Messages

I have Firefox 3.6.14, when I start up it says windows resolution of 1366x768 is set under 1024x768, why?

Mozilla 5 Firefox 3.6.14 opens and a screen appears:
"There seems to be a screen resolution problem.
Your screen resolution is set below our minimum recommendation. When it's set under 1024 x 768 pixels, the all-new Yahoo! Mail won't look as good."
I check the screen resolution and it is 1366x768. I think you have a bug!
bwagner

Clear the cache and the cookies from sites that cause problems.
* "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
* "Remove the Cookies" from sites causing problems: Tools > Options > Privacy > Cookies: "Show Cookies"
What are the dimensions of the Firefox window?
You can try;
* http://kb.mozillazine.org/Corrupt_localstore.rdf

Gnome-network-manager

Hi Everybody
I just tried to play a little with gnome-network-manager from AUR, first of all the normal network manager was missing a few files, but I managed to find them(http://aur.archlinux.org/packages/networkmanager/networkmanager/).
But when i start up gnome, it is shown fine in the Status Area, and shows all the networks, but it won't connect to any...
When connecting to an unencrypted network it says it is waiting for the network, when connecting to an encrypted network, it is waiting for the key to be verified.
My assumption is, that it is waiting for DHCP, in both cases.
If I use wifi-radar it gets an IP perfectly, also if I use dhclient or dhpcd it works fine.
Any suggestions?

I tried to use the one from testing, along with the gnome GUI from testing, but with no luck...
As you can see here, it tells me it is waiting fr the key, http://gallery.timmy.dk/Screenshots/gno … anager.png
But in the consle, iwconfig says I'm already connected...
So I'm pretty sure there something wrong with the dhcp

Xfce4 and gnome-network-manager [solved]

I just made a clean install of archlinux. installed xorg and Xfce4, xfce-goodies, gnome-panel, gnome-desktop and gnome-network-manager. also I enabled GNOME services in startup and sessions. how do I start that network manager now? is nowhere in the settings, nor there is icon to add to the taskbar (i got xfapplets installed too)
Last edited by anarxi (2009-01-14 00:22:42)

quoted from a previous thread
I solved it by uncommenting my <locale><charset> in /etc/locale.gen.
First you have to enable the locales you want being supported by your system. To enable or disable them, the file /etc/locale.gen is used. It contains every locale you can enable, and you have just to uncomment lines you want to do so.
As we want to setup an english UTF-8 conform system, we want to enable en_US.UTF-8. But for compatibility to programs that don't support UTF-8 yet, it's recommended to support any other locale, prefixed with en_US as well. Having this in mind, we enable this set of locales:
en_US.UTF8 UTF-8
en_US ISO-8859-1
After you've enabled the necessary locales, you have to run locale-gen as root to update them:
# sudo locale-gen
Generating locales...
en_US.UTF-8... done
en_US.ISO-8859-1... done
Generation complete.

Gnome-network-manager problems

Hello all,
I'm trying to use gnome-network-manager to connect to my wifi as it is WEP enabled and I don't know how to get it working in 'network'.
I followed this tutorial: http://wiki.archlinux.org/index.php/NetworkManager
However, when I reboot under those settings, I can't connect to anything, including ethernet.
Is there a problem in the wiki or is there a workaround that hasn't been posted there yet? I'm utterly confused as to why it will not work.
Also, if you need me to paste any code from any file, can you also tell me an easy way to copy/paste between aterm and Opera as I haven't found a way to do that yet.
Thank you very much for any help.
Matt

[matt@myhost ~]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"3KR98"
Mode:Managed Frequency:2.427 GHz Access Point: 00:18:01:E0:43:1A
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=21/100 Signal level=-72 dBm Noise level=-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:76 Missed beacon:31
[matt@myhost ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:A1:71:02
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fea1:7102/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:82717 errors:300 dropped:592 overruns:300 frame:0
TX packets:61302 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:79395572 (75.7 Mb) TX bytes:9179527 (8.7 Mb)
Interrupt:22 Base address:0x6800
eth1 Link encap:Ethernet HWaddr 00:13:CE:6A:FE:C1
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:ceff:fe6a:fec1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:309 errors:0 dropped:76 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2420181 (2.3 Mb) TX bytes:2012 (1.9 Kb)
Interrupt:23 Base address:0x4000 Memory:bc005000-bc005fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:232 errors:0 dropped:0 overruns:0 frame:0
TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20464 (19.9 Kb) TX bytes:20464 (19.9 Kb)
ill post output of disabling gnome-net-manager in a bit (i have to reboot and save it as a file first).
also, im running fluxbox, not gnome, so could that be part of the problem? am i missing something flux specific?

Gnome-network-manager & XFCE 4.4

Hey guys, someone know if gnome-network-manager also run on XFCE 4.4?
It won't run on my XFCE
Solutions to problem?
Bye,
Riccardo

Captain Spaulding wrote:
OK, open NetworkManager.conf and search for the line
<policy at_console="true">
and add this line:
<allow own="org.freedesktop.NetworkManagerInfo"/>
That, at least, should fix your initial issue. I have only just begun to learn more about dbus, so I have no clue about the second problem.
Mmmmm no entries as <policy at_console="true"> in my NetworkManager.conf....
So here we are my NetworkManager.conf:
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<policy user="root">
<allow own="org.freedesktop.NetworkManager"/>
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy group="users">
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy user="hal">
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy context="default">
<deny own="org.freedesktop.NetworkManager"/>
<deny send_destination="org.freedesktop.NetworkManager"/>
<deny send_interface="org.freedesktop.NetworkManager"/>
</policy>
</busconfig>

Gnome Network Manager Isues

Hi Guys,
I have some weird issues with Gnome Network manager when I first boot up. I seem to have 2 profiles for my network connection enp3s0. I have a static IP for my PC, xxx.xxx.xxx.66, as I share music and photo's with a media centre PC in another room. But when I boot up or reboot the PC, it defaults to what appears to be another static IP address, xxx.xxx.xxx.109, that was used during the installation of Arch. I have disabled dhcpcd via
systemctl disable dhcpcd.service
but I can't seem to find where this weird IP is coming from.
If I open a command prompt at first login, and I issue ifconfig, my PC has the 109 IP address. If I expand on the Wired icon in Gnome's top right panel, I can see the two profiles, the incorrect one has a small dot next to it, to indicate its active. If I click on it, it disappears and my network becomes disconnected. When I reconnect, I get the correct profile with the correct IP address of 66, the 109 profile has gone.
If I go into the Weird Settings just after login, without clicking on any profiles, I have 2 settings in the box, the top one has a tick next to it and ther bottom one hasn't. If I click on the cog for the first profile, I can see it has a static of 109. Under identity, I remove the ticks for connect automatically and make available to ther users and apply. I reboot and the 109 profile is still there.
Cheers

yes, I have done it, and nothing happen
edit : I have reinstall the software, and now it is OK, tks for the help
Last edited by serafimsaudade (2007-05-20 17:34:56)

Gnome-power-manager update causes backlight to power off frequently

After the upgrade to gnome-power-manager 2.26.1-1 today, my laptop screen backlight is being powered off constantly, after only about 1 minute. It's not the screen blanking, but the backlight going off. It comes right back up if I do anything on the keyboard.
My power management preferences haven't changed though. They're all set (as before the upgrade) to never dim the display and never put the display to sleep. So why is the backlight going off anyway?
Also, this pretty distinctly seems to have to do with Gnome and not X. If I leave the laptop for an extended period at the GDM login screen, the backlight is never powered off. The problem only develops after I have logged into Gnome.
Thanks for any help.
Last edited by cb474 (2009-04-23 07:14:55)

Thanks, I looked for bugs on this, but didn't find that one on the backlight for some reason. I was about to issue my own bug report. Anyway, so I added my comments to the bug report, but it has been marked "fixed" already (because it was really addressing a slightly different issue with DPMS), so I don't know if I need to start a new bug report or not. I'll wait and see what kind of reply I get. (In fact, it seems like the fix to the problem in the backlight bug report may have caused the problem addressed in this thread.)
That said, I found a work around, if you want to completely disable the backlight ever going off. You can issue the command:
xset -dpms
This disables entirely the display power management system (which I'm guessing gnome-power-manager operates as a frontend for). Of course, if you want your screen to be put to sleep after some set point of time this won't work. But you may be able to configure this directly with other xset commands or in xorg.conf (see links below).
To disable dpms at startup. I found oddly that it didn't work to add it to my .xinitrc. So instead I went to System > Preferences > Startup Applications. Added an a program in the "Startup Programs" tab, named it "DPMS (disable)" and for the command put:
xset -dpms
This is working.
You can also configue DPMS in xorg.conf, but I'm not using xorg.conf so I didn't fiddle with it. See: http://wiki.archlinux.org/index.php/DPMS and http://www.shallowsky.com/linux/x-screen-blanking.html.
Hope that helps.
Last edited by cb474 (2009-04-24 08:26:23)

Solaris 10 gnome session manager crashes on login

There are two Solaris 10 servers at work that I cannot log into. At the login screen I choose Options --> Session --> Java Desktop System, Release 3
and then try to log in. I get the following error message:
"The GNOME session manager (process XXXXX) has crashed due to a fatal error. (Segmentation Fault). When you close this dialog, all applications will close and your session will exit. Please save all your files before closing this dialog."
I was able to find one post on this error using google. It said that the user solved this problem by editing the LD_LIBRARY_PATH variable by moving /usr/local/lib to the beginning of the line. This didn't fix my problem. I logged in via ssh and double checked that the LD_LIBRARY_PATH change had saved.
Other people can log into the server just fine. Just not me. I even completely wiped my home directory. Anybody know where I can find a fix for this?

Just discovered that if one of the working users logs completely out, they cannot log back in. So this error affects everybody.

[SOLVED] gnome-volume-manager is lazy

Until some update that I missed all was fine. I boot, my volumes are mounted, I can see them in ROX (my main file management program).
I insert a CD/DVD/whatever, its mounted and its all in /media/.:D
But now it just does nothing, until I start Nautilus, then everything gets mounted.
I close Nautilus, and it doesnt mount anything again.
gnome-volume-manager process is up and running after login before running nautilus and after closing it too.
How can I make it behave nicely without the nuisance that Nautilus is?
Oh and Im running Openbox as the window manager in Gnome, Nautilus desktop handling disabled.
Last edited by Hohoho (2008-05-28 20:21:12)

i had the same problem.
i looked in the changelog and it appears that from now on the automount function is disabled upstream because that function is to be handled by the nautilus ( http://ftp.gnome.org/pub/GNOME/sources/ … .3.changes ). For me it is a problem because i use openbox and thunar, so you just have to recompile the package with the option: "--enable-automount" .
info from:
~/Desktop/gnome-volume-manager-2.22.3 $ ./configure --help
then start it ( after recompiling with abs, for example ), but look that the path changed, now in my autostart file for openbox i have:
/usr/lib/gnome-volume-manager/gnome-volume-manager --sm-disable --daemon=yes &
hope it helps you, because this annoyed me for a long time and this is the only easy way to mount my partitions easily
Last edited by Diaz (2008-05-28 20:04:56)

Gnome Power Manager Applet

Hi all,
since the last update, the gnome power manager applet is gone. I can change the preferences with the gnome-power-preferences tool, but the applet in the system bar is gone... Any idea?
Acker

Master One wrote:
So what's going on?
I do not assume, that users of other distros have such problems, at least in Foresight Linux the applet is working as supposed to, which confirms that it's not an upstream problem. There is a bug open, but no info about any progress.
Is anybody working on a fix?
Jan de Groot has been assigned to this task a few days ago. Jan works on 580 open tasks, most of which have a higher priority then this bug.
As seen from the screenshot threads, quite some Arch users are on Gnome, so that's surely not something just a minority is in need of.
What's with the Gnome 2.18.1 updates (though the working version of the Gnome Power Manager in Foresight Linux is 2.18.2 as well)?
Oh my, an icon is not shown, man the life boats. The gnome-power-manager works perfectly -- at least for me -- it just doesn't show an icon in the notification area. If you absolutely need the icon, deploy Iloeki's script. It should do the job.

Gnome-Shell logs in as Gnome Display Manager

Hello,
My gnome-shell decided to crap out on me after working perfectly for the past few days. It wouldn't boot into the session even with extensions off. I tried everything(removing old configuration files, setting an autostart on Gnome-shell in ~/.config/autostart. Now my Gnome-shell starts but it logs in as Gnome Display Manager. Terminals do not start up(they come up and dissapear). I can't log in to XFCE anymore as a fallback because GDM autostarts into itself. I tried switching display managers to slim but it errors starting in there also.
This behavior happened after a symlinked a file but I'm not sure which. The page I was browsing it on was on my other user.
Thanks, I am really bummed that I can't even get into my XFCE session right now and this GDM as user is nearly unuseable.
Edit: https://bbs.archlinux.org/viewtopic.php?id=118651
#3 is the post I followed, will try to remove the sym link and see what happens.
Last edited by 6msj (2011-10-26 18:55:36)

Looks like removing the sym link did it, but now my previews are screwed up.
http://dl.dropbox.com/u/11400324/Screen … 0%3A09.png

Gnome file manager problem

lately I've noticed that in the Gnome file manager when I go to a directory with images in it, 4 will show up and all the rest don't and the cursor is in a waiting mode that it can't get out of.
What causes this and how can it correct it?
Last edited by vinoman2 (2009-11-07 15:00:38)

Thanks, I later rebooted and that fixed the problem. It was only in one directory.
I just moved a image to a folder and it did it again. I ran nautilus in the terminal and it only opened nautilus.
Is this a bug in Gnome? It seems to happen every time I want to move an image into a folder.
Is there a way to fix this?
Last edited by vinoman2 (2009-11-07 15:02:37)

Mounting drives on a udev+hal+gnome-volume-manager setup

Hi,
I set up Arch Linux on a friends computer. The setup seems to work, for example gnome-cd is started when one inserts an Audio CD. However, everything that involves mounting does not work. The error message given by gnome-volume-manager is
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
or too many mounted file systems
* /bin/mount has sid set, 755, owner and file group are root
* udev is set up correctly, so /dev/hdc for example does have write rights for the group disk, and the user is member of that group.
What could be wrong?

The problem was mainly about mounting, and not about /dev/sda or /dev/hdc. We found the solution:
The "mount" binary in Arch's current is confused by the entry "managed" that hal puts in /etc/fstab. You can correct this by
a) Adding a policy file in /usr/share/hal/fdi/95userpolicy named, for example, local.fdi that hinders hal from doing so:
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">

<device>
<match key="info.udi" string="/org/freedesktop/Hal/devices/computer">
<merge key="storage.policy.default.managed_keyword.primary" type="string">user</merge>
</match>
</device>
</deviceinfo>
Then restart hal by typing
/etc/rc.d/hal restart
as root
b) Patching "mount" as described in Arch Linux bug #1930.[/code]

"The GNOME keyring manager hijacked the GnuPG agent"

I've run gpg from the command line and suddenly a dialog box appeared asking for my password: it even asked if I wanted to remember it.
Meanwhile, in my bash terminal gpg had this to say:
gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.
gpg: WARNING: GnuPG will not work proberly - please configure that tool to not interfere with the GnuPG system!
Googling didn't help much, seems to be a new "feature"...
Any idea how can I configure the keyring manager to stay away when I'm working in bash?

I had similar situation and decided to disable gnome-keyring's ssh and gpg agents. https://wiki.archlinux.org/index.php/GN … ing_daemon
The reason is that gnome keyring is active only when you have a GUI session active, thus it does not work for headless machines or when one SSH to the machine. It is just easier for me to use "default" agents.
PS The ssh-agent and gpg-agent is a mess from usability/configuration point of view (without those ugly environment variables). I wish there was a systemd friendly implementation of these agents.
PPS The latest gnupg use "use-standard-socket' config option by default, it means one does not need to start gpg-agent and configure GPG_AGENT_INFO envvar manually. gpg will start agent for you transparently.

No native resolution of 1366x768 in gnome resolution manager..

Similar Messages

Maybe you are looking for