Xorg-server broken after upgrade to 1.6.3.901-1

Hello,
After upgrading to xorg-server 1.6.3.901-1 and rebooting the computer xorg-server respawned repeatedly very fast and I was unable to exit except for pressing the power button (I had runlevel 5 set in /etc/inittab). Then I set the runlevel to 3 in /etc/inittab (using a liveCD), logged in and typed startx. The terminal became black except for a grey cursor in the top left of the screen and I was unable to exit except for pressing the power button.
The previous version of xorg-server is no longer in the pacman cache because I cleared it.
Thanks.

helpvampire wrote:
Hi,
I fixed this by using the xf86-video-nv driver instead of xf86-video-nouveau. However it has very poor performance.
Why you don't use NVIDIA drivers?It's very nice from your side to use open source dirver but you have any problem's with NVIDIA drivers?
Here you have topic with same issue and drivers:
http://bbs.archlinux.org/viewtopic.php?id=79512
Last edited by SpeedVin (2009-09-08 18:00:08)

Similar Messages

Xorg(nouveau) problem after upgrade (x86_64)

hi,
in my arch64 (current) I have updated some packages:
[2011-01-31 12:22] upgraded kernel26 (2.6.36.3-2 -> 2.6.37-5)
[2011-01-31 12:22] upgraded kernel26-headers (2.6.36.3-2 -> 2.6.37-5)
[2011-01-31 12:22] upgraded nouveau-dri (7.9.0.git20101207-2 -> 7.10-1)
[2011-01-31 12:22] upgraded xf86-video-nouveau (0.0.16_git20100819-2 -> 0.0.16_git20101217-1)
[2011-01-31 12:22] upgraded xorg-server-common (1.9.2-2 -> 1.9.3.901-1)
[2011-01-31 12:22] upgraded xorg-server (1.9.2-2 -> 1.9.3.901-1)
after reboot, X not work OK, it seems like out of frequencies
it works only if I use "vesa" instead of "nouveau"
p.s.
if I exec: X -configure
I have:
(EE) [drm] No DRICreatePCIBusID symbol
thank you
Last edited by sacarde (2011-02-01 19:38:27)

There is already a thread on broken GUI after the libdrm/nouveau upgrade :
see https://bbs.archlinux.org/viewtopic.php?id=112758
A bug report was opened in the Flyspay about that (#22700).
Downgrading the packages listed in the thread above solves temporarily the problem.
Please can you precise the Nvidia chipset you use ?
Thanks.

Re: (forte-users) Unstable server ENV after upgrade to Forte30M2.

I see/suggest a few things:
1) In your #1, you mention ".... development and test environments which use the
same Forte 3M installs through links ...". This concerns me. On our UNIX box
each environment has it's own directory containing it's own install. If your
environments are some how sharing a node manager, log directory or processes (to
name a few things) that is a recipe for disaster. They may be competing for
resources and usually the first one started will win.
2) I haven't done a lot with compatibility levels, but if an application built
in dev is to run in test it may be important that node managers and services
(autocompile, codegen etc.) be at the same level (????).
3) Check the definition files, to make sure the two environments operate
independently. If they are both trying to write to the same log file the one
started up first will work while the second will not as the file will be "busy".
4) We usually use rpcreate (newer version) to create brand new repositories.
Than we export/import the source code that we need. Also it is important to
force compile ALL plans in a workspace at least once after doing the import.
This will ensure that all of the code is "speaking the same language". The other
compile, only compiles those pieces of code that changed from the last compile.
Hope this helps.
Kelsey PetrychynSaskTel Technical Analyst
ITM - Technology Solutions - Distributed Computing
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:kelsey.petrychynSasktel.sk.ca
Quality is not job 1. It is the only job!
"Braja Chattaraj" <forte_brajachotmail.com> on 09/13/2000 03:43:57 PM
Please respond to chattaraj_braja_NONLILLYlilly.com
To: forte-userslists.xpedior.com
cc: (bcc: Kelsey Petrychyn/SaskTel/CA)
Subject: (forte-users) Unstable server ENV after upgrade to Forte 30M2.
We are running Forte 3M2 clients and server in our test environment with
clients on NT and server on Solaris 2.6. Eversince the upgrade from 3L to 3M
we have been having an unstable environment that does not remain alive for >
10 mins. These are the details of the Forte installs and server setups :
1. The server hosts the development and test environments which use the same
Forte 3M installs through links (same ftcmd, ftexec, nodemgr, etc.). The
environments are at compatibility levels 0 and 1 respectively.
2. The two environments have the same definition files (defining the ENV
variables), though seperate copies and the two environments are hosted on
different ports on the same server.
3. While building the new 3M environmnets in DEV and TST, we exported the
old 3L repositories and imported them into the new 3M repositories and
deployed the applications.
While the DEV environment is stable the TST environment is not. This has
been observed while moving plans between the environments (export and
import) using fscript commands, deploying the apps after the move using
fscript, and testing the apps. Sometimes it has come down right after a
startup. There is no programatic reference to the environment agent in the
code. So, a programatic shutdown is ruled out.
Does anybody have a clue or a similar experience ?
Thanks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BRAJA KISHORE CHATTARAJ
Consultant, Analysts International.
Work : Sphinx Pharmaceuticals (A division of Eli Lilly & Co.)
(919) 314-4134
Home : 1801, Williamsburg Rd., #41H, Durham, NC 27707.
(919) 463-7802
E-mail : forte_brajachotmail.com
Visit us www.analysts.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://profiles.msn.com.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

We found a solution to our issue.Their desktops were in a lockdown environment and the essbase.id file located in the windows directory was locked as well. This file is responsible for assigning ports etc and it couldn't be updated for the 6.5.4p2 upgrade. Once the file was deleted and the user reconnected to Essbase, the essbase.id was reset and they could connect.

Mail flow completely broken after upgrading Exchange Server 2013 CU3 (Build 775.38) to Exchange Server 2013 SP1 (Build 847.32)

internal mail flow completely broken.
external mail flow completely broken.
i upgraded exchange server as follows:
1. setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
2. setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
3. upgraded the exchange server with GUI installer
also considered this: http://support.microsoft.com/kb/2938053/en-us
receive connectors :
Transport Service couldn't start, then i disabled hub transports, and it starts, but no mail flow on port 25. according to this:
http://social.technet.microsoft.com/wiki/contents/articles/24056.what-the-crash.aspx
i didn't have any success to fix mail flow, any solution?

Hi Alireza
The above tech-net http://social.technet.microsoft.com/wiki/contents/articles/24056.what-the-crash.aspx
will be applicable only if we get these events in the app log 1019,1018,1036,4999
You can check the transport service is running in which service account - Local or network
It should be running in network account by default.
You can run get-transportagent and check if there are any transport agents installed
If you find them then disable all the transport agents that you have installed on the Exchange servers by running disable-transportagents
Disable the antivirus if you have any installed.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

[Solved]Terminology - Broken after upgrade

After running a system update it appears that Terminology is no longer working correctly.
i.e:
Background does not render properly, just shows black screen, Cannot use rightclick to make modifications, etc
Has anyone else experienced this issue?
=====================================
Fix:
Downgrade to package 0.6.1-1 from cache
pacman -U /var/cache/pacman/pkg/terminology-0.6.1-1-x86_64.pkg.tar.xz
=====================================
Last edited by cyberpsych0sis (2014-11-12 02:59:41)

jasonwryan wrote:
Start it from another terminal and see what error it prints...
Also, please paste the list of packages that were included in your last upgrade.
Output from the pacman.log after upgrade:
[2014-11-11 18:21] [PACMAN] Running 'pacman -Syu'
[2014-11-11 18:21] [PACMAN] synchronizing package lists
[2014-11-11 18:22] [PACMAN] starting full system upgrade
[2014-11-11 18:30] [PACMAN] upgraded at-spi2-core (2.14.0-1 -> 2.14.1-1)
[2014-11-11 18:30] [PACMAN] upgraded avahi (0.6.31-13 -> 0.6.31-14)
[2014-11-11 18:30] [PACMAN] upgraded ca-certificates-mozilla (3.17.1-1 -> 3.17.2-1)
[2014-11-11 18:30] [PACMAN] upgraded calibre (2.8.0-1 -> 2.9.0-1)
[2014-11-11 18:30] [PACMAN] upgraded kmod (18-1 -> 18-2)
[2014-11-11 18:30] [PACMAN] upgraded libsystemd (216-3 -> 217-6)
[2014-11-11 18:30] [PACMAN] installed lz4 (123-1)
[2014-11-11 18:30] [PACMAN] upgraded systemd (216-3 -> 217-6)
[2014-11-11 18:30] [PACMAN] upgraded colord (1.2.3-1 -> 1.2.5-1)
[2014-11-11 18:30] [PACMAN] upgraded curl (7.38.0-3 -> 7.39.0-1)
[2014-11-11 18:30] [PACMAN] upgraded dhcpcd (6.6.0-1 -> 6.6.1-1)
[2014-11-11 18:30] [PACMAN] upgraded gcc-libs (4.9.1-2 -> 4.9.2-1)
[2014-11-11 18:30] [PACMAN] upgraded poppler (0.26.5-1 -> 0.28.1-1)
[2014-11-11 18:30] [PACMAN] upgraded evas_generic_loaders (1.11.2-1 -> 1.11.2-2)
[2014-11-11 18:30] [PACMAN] upgraded fakeroot (1.20.1-1 -> 1.20.2-1)
[2014-11-11 18:30] [PACMAN] upgraded gcc (4.9.1-2 -> 4.9.2-1)
[2014-11-11 18:30] [PACMAN] upgraded gnutls (3.3.9-1 -> 3.3.10-1)
[2014-11-11 18:30] [PACMAN] upgraded gstreamer (1.4.3-1 -> 1.4.4-1)
[2014-11-11 18:30] [PACMAN] upgraded gst-plugins-base-libs (1.4.3-1 -> 1.4.4-1)
[2014-11-11 18:30] [PACMAN] upgraded gst-plugins-base (1.4.3-1 -> 1.4.4-1)
[2014-11-11 18:30] [PACMAN] upgraded gtk3 (3.14.4-2 -> 3.14.5-1)
[2014-11-11 18:30] [PACMAN] upgraded ldns (1.6.17-1 -> 1.6.17-2)
[2014-11-11 18:30] [PACMAN] upgraded libedit (20140620_3.1-1 -> 20141030_3.1-1)
[2014-11-11 18:30] [PACMAN] upgraded libffi (3.1-2 -> 3.1-3)
[2014-11-11 18:30] [PACMAN] upgraded libltdl (2.4.2-14 -> 2.4.2-15)
[2014-11-11 18:30] [PACMAN] upgraded libtool (2.4.2-14 -> 2.4.2-15)
[2014-11-11 18:30] [PACMAN] upgraded logrotate (3.8.7-3 -> 3.8.8-2)
[2014-11-11 18:30] [PACMAN] upgraded man-db (2.7.0.2-2 -> 2.7.1-1)
[2014-11-11 18:30] [PACMAN] upgraded mesa-dri (10.3.2-1 -> 10.3.3-1)
[2014-11-11 18:30] [PACMAN] upgraded mesa (10.3.2-1 -> 10.3.3-1)
[2014-11-11 18:30] [PACMAN] upgraded mesa-libgl (10.3.2-1 -> 10.3.3-1)
[2014-11-11 18:30] [PACMAN] upgraded nss (3.17.1-1 -> 3.17.2-1)
[2014-11-11 18:30] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2014-11-11 18:30] [PACMAN] upgraded pacman-mirrorlist (20141028-1 -> 20141108-1)
[2014-11-11 18:30] [PACMAN] upgraded poppler-glib (0.26.5-1 -> 0.28.1-1)
[2014-11-11 18:30] [PACMAN] upgraded python-pygments (1.6-4 -> 2.0.1-1)
[2014-11-11 18:30] [PACMAN] upgraded systemd-sysvcompat (216-3 -> 217-6)
[2014-11-11 18:30] [PACMAN] upgraded terminology (0.6.1-1 -> 0.7.0-1)
[2014-11-11 18:30] [PACMAN] upgraded xorg-server-common (1.16.1-1 -> 1.16.2-1)
[2014-11-11 18:30] [PACMAN] upgraded xorg-server (1.16.1-1 -> 1.16.2-1)
And when I run Terminology from Xterm it doesn't seem to provide any errors.

Mail server issues after upgrading

Hello,
After upgrading my iMac to Mountain Lion 3 of our 5 email account are not working.
The 5 accounts are [email protected] However 3 of them are not able to come online.
I tried MANY times to delete them and recreate them coming ALWAYS to the same issue.
What I noticed is that the INCOMING mail is different from the incoming mail from the accounts that are working. (the accounts that are working use an incoming mail server: p05-imap.mail.me.com or p01-imap.mail.me.com) However the accounts in trouble only show a grey out "MAIL.EXAMPLE.COM" unable to switch it.
The outcoming mail in those accounts is "ICLOUD - OFFLINE".
Even if I tried to switch servers I get a notice " SERVERS MARKED WITH ALERT ICONS ARE IN CONFLICT AND CANNOT BE SAVED. TOW SERVERS CANNOT SHARE THE SAME ADDRESS AND AUTHENTICATION SETTINGS. TRY AGAIN".
I get this notice even after deleting all the problem accounts.
Also I tried switching ports like some people suggested on other posts and does not help either.
The account are working perfectly on ipads, ipods and iphones.

David,
You are right, theer are some changes incorporated in the latest MLR # 16 on the configurations files and on the dehydration store metrics(such as performance, fields,..).
However, I would not suggest to continue working on olite, even for Development/Test purposes as you might get stuck with strange errors...and the only solution would be to re-install SOA Suite if your olite gets corrupted. There might be ways to gets your olite back to position, but trust me..its not so simple.
Also, when you develop and stress test all your testcase scenarios in an TEST Adv installation, its simple to mimic the same in actual production box, as you exactly know its behavior.
So, go for a brand new SOA 10.1.3.4 MLR # 5 (or) 10.1.3.3.1 MLR # 16 SOA Suite Advanced installation with Oracle DB 10.2.0.3 as its dehydration store.
Hope this helps!
Cheers
Anirudh Pucha

[SOLVED] xorg / nvidia problems after upgrade

Hello,
I have recently done an upgrade with pacman -Syu and am having problems.
When X starts, it hangs at a blank screen. Keyboard is frozen and I am unable to hit another tty. I can ssh in, but I cannot even seem to kill X, or reboot. I am forced to do a hard reboot.
I have tracked the problem down to running multiple X sessions. I currently have 4 monitors, and have them configured such that I have 2 X sessions, (2 monitiors with twinview on each session). I can get things working on 2 monitors using twinview, but I cannot get X to start properly if I enable the second X session. (I have tried everything and cannot get anything to come up unto a third monitor... I can only get X working on 2..)
This seems like it could be a bug. Although I am not sure if the problem is with X or with the nvidia drivers, as both were updated, however I am thinking it is an issue with X.
I have checked and rechecked my xorg log files, and there are no errors, however, once I did see this error, but it did not happen consistently..
[mi] EQ overflowing. The server is probably stuck in an infinite loop
Any suggestions? I would like even be happy with downgrading some packages to get this working again.
Last edited by mikej_96 (2010-03-20 19:49:49)

mikej_96 wrote:
Update 2:
Since downgrading xorg-server didn't help, I decided to try installing the latest and greated nvidia drivers. I grabbed them from their website, and uninstalled the nvida package from arch. (Version 190.53.1). The drivers I am currently running are 195.36.15 and all is well.
Instead of installing non-managed packages, why not use nvidia-beta and nvidia-utils-beta from the AUR?

File Sharing broken after Upgrade to 10.9

Hello,
after upgrading to Maverick Server i cannot connect to File Sharing services anymore.
AFP protocol does not accept my user passwords anymore. Only guest access works.
I read that Mavericks prefers smb now instead of afp. But smb seems not to be active at all. Allthoh the server app claims that smb is running.
Any similar observations?

This might also help: connect with cifs://
FROM:
http://osxdaily.com/2013/10/30/connect-smb-nas-network-shares-os-x-mavericks/
Connect to SMB & NAS Network Shares in OS X Mavericks
Oct 30, 2013
... a very easy workaround to connect to SMB and NAS shares from OS X:
From the OS X Finder, hit Command+K to summon “Go To Server” as usual.
In the “Server Address” field, use the cifs:// prefix as follows:
cifs://127.0.0.1
Connect to the SMB, NAS, or Windows share as usual.
... it’s because using CIFS connects with SMB1 rather than the (currently) buggy implementation of SMB2. ... Apple adjusted the default protocol for SMB (Samba, the Windows file sharing ability) from SMB1 to SMB2, and the SMB2 implementation apparently carries a bug which is incompatible with ...

Mail broken after upgrade to Leopard

After upgrading my G5 from 10.4 to Leopard, everything works fine except Apple Mail is completely broken. All of my folders were transferred, but they are empty and can not be rebuilt. My old folders are intact and located in the User/Library/Mail folder. All of my accounts (2) transferred correctly, but I can not send or receive mail. Most of the menu items are grayed out, and the application will not quit–except by using force quit. Connection Doctor shows all servers as green. I have completely run out of ideas.

Had the same problem. There is an apple support note with another simple solution: TS2537.
Resolution
1) Force quit Mail if necessary: From the Apple menu, choose Force Quit, select Mail in the Force Quit window's list of applications, then click "Force Quit".
2) If the issue persists after relaunching Mail, follow these steps while Mail is not running:
3) From the Finder's Go menu choose Go to Folder. Go to this location (type or paste the following, then click Go): ~/Library/Mail
4) Move the items named "MessageRules.plist" and "MessageRules.plist.backup" to another location, such as your desktop.
5) Open Mail. Note: At this point you can either set your Junk Mail settings and re-create your Mail rules manually in Mail preferences, or follow the next two steps (if you re-create rules and Junk settings, do not perform the following steps).
6 ) Quit Mail.
7) Place the items named "MessageRules.plist" and "MessageRules.plist.backup" back in the ~/Library/Mail folder (replace any copies that were added to ~/Library/Mail when you opened Mail).
Second issue
I had another problem in addition. My mail came back up by using the individual remove commands listed above, but they buttons in my new mail application still reflected the old 2.x layout and not the new mail 3.x layout. Only clearing all the settings by running
defaults remove com.apple.mail
solved the issue for me.
Thanks everyone for their help!!
in a terminal window cleared everything. Now the buttons are in the right spot.

USB Share broken after upgrade to Firmware 1.05.36

Hi, Problem after upgrade to Firmware 1.05.36. When connecting USB disk there no share created for the newly connected disk. The result is: Broken functionality backup to USB diskBroken functionality restore from USB disk It worked OK before thefirmware upgrade (I have been using this a lot). I have checked through ssh login: the disk mounts ok. Please fix!!

Yes, that's exactly what I mean - the shares that are automatically created when you insert the drive (ie the functionality you seem to have lost). There's no setting to enable/disable that, at least that I know of. It should just always automatically do it. The shares themselves are just links in the /shares folder, to the relevant mount folder if what I can see on my MCM via SSH is what I think it is. You may be able to manually make the links yourself via the command prompt as a work-around. Please note that I haven't tried this myself, as my one works. But what I would do is try and install the firmware image again over the top of your current one. You can download it manually from this page and then install it via the dashboard using Settings > Firmware Update > Manual Update. There should be a button there that you press and point it to the firmware image file you downloaded and stored on your local machine. If the button isn't there, try a different browser (I find on my Windows machine it doesn't appear under Chrome, I have to use IE for that job).

HT6114 My os x server disappeared after upgrading to mavericks

I had purchased OS X Server on my Mountain Lion version, but it disappeared after upgrading to Mavericks. What should I do to get my Server back?

I understand, sadly Apple set the rules & the prices.
You will need to read the requirements for running Server.app, the old version was for 10.8, the newest is for 10.9. if you hope to configure on 10.9 you'll need to pay again.

Server admin is unable to login to server.app after upgrade to Mountain Lion Server?

After upgrade to Mountain Lion Server I am unable to login to the server tools. When I input the admin user name and password the dialog box just shakes indicating the wrong password. But it is the correct password. How do I reset the password or if necessary how do I rest the server and start over on Mountain Lion. I found info on how to reset the server on previous versions of the server which involved executing a plist in the LaunchDaemon folder. However that file does not exist on the server following upgrade to Mountain Lion.
Thanks, Howard

I upgraded today and had the same issue. I took following steps to fix my computer.
Boot into Recovery Partition (Hold Option Button while booting)
Open Terminal.
Type resetpassword
Select your hard drive
Select the user account (Administrator)
Enter a new password for the user
Reenter password
Save
Restart
Boot normally, Login as Adminstrator with the new password and add "Admin" permission to your account.
Restart
Everything should be working as expected

NetworkManager applet broken after upgrading from 0.8.1-2 to 0.8.2-2

After upgrading both networkmanager and network-manager-applet, i am unable to connect to any wifi networks.
[2010-12-15 23:22] upgraded networkmanager (0.8.1-1 -> 0.8.3-0.20101130)
[2010-12-15 23:23] upgraded network-manager-applet (0.8.1-2 -> 0.8.2-2)
The applet detects and shows networks, but then keeps trying to connect indefinitely without success.
What's the problem here?
I'm not the only one having this problem:
https://bbs.archlinux.org/viewtopic.php?id=109413
https://bbs.archlinux.org/viewtopic.php?id=109818
So it seems most likely a problem with nm-applet only working if you run it as root (sudo nm-applet).
I have no experience with this area. Any idea what might be wrong? Perhaps something to do with PAM?
Last edited by trusktr (2011-01-11 18:18:43)

Aah, you're right. Sorry. Haven't heard anything regarding this though, and it's a fairly distracting problem.
Last edited by trusktr (2011-01-11 20:33:58)

Unable to setup server.app after upgrading 10.7.5

hi, i had a macmini server and i upgrade from lion to mountain lion, when i try to setup server.app i get this message
"se ha producido un error de ssl y no puede establecerse una conexion segura con el servidor"
please help

You must delete the "com.apple.servermgrd" identity preference and certificate.
More info: http://support.apple.com/kb/TS4493

IMAP Mail Trash broken after upgrading to Mavericks

Hi,
after upgrading an iMac from latest 10.8 to 10.9 Mail.app doesnt use the trash folder on imap correctly.
It displays the trash folder separately; the "global" trash folder doesn't contain anything.
When deleting an email it is moved to the trash folder like it should be.
Any idea how to fix this?

In the left panel that appears after clicking Show, I only had Inbox, Flagged, Sent, Trash, Archive, On My Mac, and my name. After hovering on my name "Show" appeared. I clicked on Show and all the mail boxes appeared. Problem solved

Xorg-server broken after upgrade to 1.6.3.901-1

Similar Messages

Maybe you are looking for