Jsf filter.....why doesn't start????????

Hi guys,
excuse me if i repeat a my old post,but now i have more clear ideas about problems.
I've developed an authorization filter in my jsf application that when a page is loaded try to find a visit object in the session,if it doesn't find show login page.
It's simple as concept,but in my application my filter doesn't start!
Can you help me?
My filter is very simple
package giu;
import java.io.IOException;
import javax.servlet.*;
import javax.servlet.http.*;
public class AuthorizationFilter implements Filter
  FilterConfig config = null;
  ServletContext servletContext = null;
  public AuthorizationFilter()
  public void init(FilterConfig filterConfig) throws ServletException
    config = filterConfig;
    servletContext = config.getServletContext();
  public void doFilter(ServletRequest request, ServletResponse response,
                       FilterChain chain) throws IOException, ServletException
    Utils.log(servletContext, "Inside the filter");
    HttpServletRequest httpRequest = (HttpServletRequest)request;
    HttpServletResponse httpResponse = (HttpServletResponse)response;
    HttpSession session = httpRequest.getSession();
    String requestPath = httpRequest.getPathInfo();
    Visit visit = (Visit)session.getAttribute("visit");
    if (visit == null)
      session.setAttribute("originalTreeId", httpRequest.getPathInfo());
      Utils.log(servletContext, "redirecting to " + httpRequest.getContextPath() +
                "/faces/Login.jsp");
      httpResponse.sendRedirect(httpRequest.getContextPath() +
                "/faces/Login.jsp");
    else
      session.removeAttribute("originalTreeId");
      String role = visit.getUser().getRole();    }
    Utils.log(servletContext, "Exiting the filter");
  public void destroy()
}my Login.jsp and index.jsp pages are in WebContent folder,while the other pages are in the Webcontent/protected.
What i miss?
Here is my web.xml, i thing the error is here,it's how filter doesn't intercept the requests...can you help me?
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
                         "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<context-param>
  <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
  <param-value>client</param-value>
</context-param>
<filter>
  <filter-name>AuthorizationFilter</filter-name>
  <filter-class>giu.AuthorizationFilter</filter-class>
</filter>
<filter-mapping>
  <filter-name>AuthorizationFilter</filter-name>
  <url-pattern>/faces/protected/*</url-pattern>
</filter-mapping>
<servlet>
  <servlet-name>FacesServlet</servlet-name>
  <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
  <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
  <servlet-name>FacesServlet</servlet-name>
  <url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
  <servlet-name>FacesServlet</servlet-name>
  <url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<welcome-file-list>
  <welcome-file>index.jsp</welcome-file>
</welcome-file-list>
<resource-ref>
  <description>DB Connection</description>
  <res-ref-name>jdbc/nomedb</res-ref-name>
  <res-type>javax.sql.DataSource</res-type>
  <res-auth>Container</res-auth>
</resource-ref>
</web-app>and index.jsp
<jsp:forward page="/Login.jsf"/>

Your web.xml looks fine. If it hasn't worked yet, try this.
1)
    <filter>
        <filter-name>AuthorizationFilter</filter-name>
        <filter-class>giu.AuthorizationFilter</filter-class>
    </filter>
    <filter-mapping>
        <filter-name>AuthorizationFilter</filter-name>
        <servlet-name>FacesServlet</servlet-name>
    </filter-mapping>2) Modify your filter code to check for /faces/protected/*

Similar Messages

  • My MacBook Pro doesn't start; in safe mode shift CMD V the message "disk0s2: media is not present" is written on the screen repeatedly but the MacBook doesn't start.  Do you have any ideas of why this should be or what I should do to resolve this?

    My MacBook Pro doesn't start; in safe mode <shift CMD V> the message "disk0s2: media is not present" is written on the screen repeatedly but the MacBook doesn't start.  Do you have any ideas of why this should be or what I should do to resolve this?  Thanks  Eamonn

    Thanks for these suggestions: I have tried safe mode re-starts (both "verbose" and simple "shift" + power) to no avail.  I get the error message "disk0s2: media is not present".  Following this I inserted the installation disc and from there ran disc utility.  The "Verify Disk" indicated an error " invalid sibling link" which it could not repair.
    I also tried to completely re-format/erase the disk, but again got an error message "disk object invalid or unable to serialize".
    Any ideas of what could be causing this or the best solution?  I fear I am fast running out of options.

  • I have an ipod touch 8gb model number MA623LL. How do I install apps on my ipod? Is it capable of transferring/running apps? Why doesn't my ipod touch have the basic-beginning app on the beginning screen after i erased/wiped my ipod and started new?

    i have an ipod touch 8gb model number MA623LL. How do I install apps on my ipod? Is it capable of transferring/running apps? Why doesn't my ipod touch have the basic-beginning app on the beginning screen after i erased/wiped my ipod and started new?

    Googling shows that you have the 1G iPod.  For apps you need at least iOS 2. The iG can go as far os 3.1.3 that you get here:
    Purchasing iOS 3.1 Software Update for iPod touch (1st generation)
    Just be aware that there are presently not that many apps that work with a 1G with iOS 3.1.3

  • Why Java Web Start doesn't support Pack200 out-of-the-box?

    Hello All,
    Why Java Web Start doesn't support Pack200 out-of-the-box? I was hoping that Java 6 would make things easier by adding direct support for Pack200 in Java Web Start and JNLP without needing to use servlets, etc.? All my clients are Java 5 or above so I can't push the Pack200 compressed version of the jar to every single one of them and there is no selection process needed. But I can't do it because of the servlet or complex Apache server setup requirement (it would be a headache to get customers' web server admins to set up Apache or whatever web server that way).
    My question is why is there unwillingness to add Pack200 support directly to Java Web Start and JNLP so that you can start Pack200 compressed jars just like you would start any jar using Java Web Start? Is te a technical problem?
    Thank you,
    Mete Kural

    Hallo,
    I didn�t try it, but the webstart FAQ�s read:
    Can I use Pack200 compression with the JnlpDownloadServlet?
    Yes. The JnlpDownloadServlet distributed in the samples directory of the JDK now supports Pack200. If you deploy yourfile.jar along with yourfile.jar.pack.gz the packed file will be downloaded when the client is running Java Web Start 1.5.0 or later.
    http://java.sun.com/javase/6/docs/technotes/guides/javaws/developersguide/faq.html#217
    For further information you may want to look at
    http://java.sun.com/javase/6/docs/technotes/guides/javaws/developersguide/downloadservletguide.html#pack200
    The configuration of the server and the the servlet (as described in the second link) is as easy as it seems.
    I got it working on the first try and it was my first experience with websevers at all.
    Bye Schippe
    Message was edited by:
    Schippe

  • SUP 2.0 Why the sybase Messageing Service doesn't start?

    Hellow experts,
    SUP 2.0 Why the sybase Messageing Service doesn't start?
    When I start the service, it starts and ends indicating "if they are not in use by other services or programs; it will end automatically"
    What should I do for this?
    Thanks
    Prabakar

    sometimes you only have to restart your pc. STOP SUP SERVICE ( AS ADMINISTRATOR ) and START SERVICE ( AS ADMINISTRATOR AGAIN ) ...
    That happens to me very often!

  • My LR5 doesn't start. Why?

    my LR5 doesn't start. Why?

    Good evening Jeff A Wright,
                   I must use my LR5 not in CC, but in CS. I have deleted the existing LR5 and I have reinstalled the DVD of LR5 without link to Creative Cloud. Tanks you for your mail. Best regards.
    Paolo Franceschini
    Il giorno 02/lug/2014, alle ore 18:50, Jeff A Wright <[email protected]> ha scritto:
    my LR5 doesn't start. Why?
    created by Jeff A Wright in Creative Cloud Download & Install - View the full discussion
    PaoloFranceschini do you receive any specific error messages?  What operating system are you using?  Have you updated to Lightroom 5.5?
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6516812#6516812
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
    To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Creative Cloud Download & Install by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • Why doesn't my TestStand deployment installation show up under my Windows start menu of my target machine?

    Why doesn't my TestStand deployment installation show up under my Windows start menu of my target machine?
    I have successfully installed working deployments to target machines. However, I was expecting to see the installation listed as "My TestStand System A" in my start menu, but it is not. Am I misunderstanding something here?
    Also, if I peform a different second deployment to the target station like "My TestStand System B", all of the LabVIEW files from my previous installation for "My TestStand System A" disappear from the target directory (c:\Program Files\My TestStand System A).
    I am using TestStand 4.2.1 Professional on the development station with Windows XP and LabVIEW 2009.
    Solved!
    Go to Solution.

    Thanks Paul,
    That solved my second problem and inspired me to search deeper for the answer to my first problem. The answer is in the "Distributed Files" tab, "installer properties", "Create a Program Item" checkbox:
    Wouldn't it be nice if this was automatically checked by default for the main sequence files? Wouldn't it also be nice if "Upgrade Code" was automatically regenerated by default whenever we saved the *.tsd file under a different name?
    Thanks again,
    Eugene
    Message Edited by Eugene12 on 05-06-2010 04:27 PM

  • Bea Workshop JSF Tutorial - deployed app doesn't start on Tomcat 5.0

    I've followed the BEA tutorial up to section 5 - Running the application.
    When the application is deployed from a WAR to Tomcat the application doesn't start in Tomcat 5.0
    The error message from the Tomcat console is :
    INFO: Installing web application at context path /workshop-jsf-tutorial from URL
    jar:file:/D:/Tomcat 5/jakarta-tomcat-5.0.28/webapps/workshop-jsf-tutorial.war!/
    log4j:WARN No appenders could be found for logger (org.apache.commons.digester.D
    igester).
    log4j:WARN Please initialize the log4j system properly.
    11-Dec-2006 13:45:51 org.apache.catalina.core.StandardContext listenerStart
    SEVERE: Skipped installing application listeners due to previous error(s)
    11-Dec-2006 13:45:51 org.apache.catalina.core.StandardContext start
    SEVERE: Error listenerStart
    11-Dec-2006 13:45:51 org.apache.catalina.core.StandardContext start
    SEVERE: Context startup failed due to previous errors
    Can you advise what the error is please ?

    Ram,
    Thanks for your reply. I was creating a WAR file using the Export>J2EE>WAR option.
    I've since found out you shouldn't do this for Tomcat from Bea Workshop.
    So now I am running the application in exploded mode as you suggested
    (ie. 'Run modules directly from the workspace' is checked)
    When I run pages/register.jsp - two things happen :
    1-the browser that opens WITHIN Bea Workshop has an exception :
    javax.servlet.ServletException: No faces context?!
    (I believe this is because web.xml has *.jsf as the url pattern that maps to the faces servlet, so register.jsp doesn't invoke the faces servlet. But the tutorial hasn't said anything about amending the web.xml servlet mapping.)
    2-a separate browser opens OUTSIDE of BEA workshop and the url is "http://localhost:8080/"
    I don't understand what's happening here.
    The tutorial should be very reliable, not throw up errors.
    If you or anyone else can throw any light on this I'd be grateful.
    Thanks Steve

  • Handles on subclips doesn't start at beginning...why?

    I am using FCP 7.  I make a subclip.  Then I put the subclip into my timeline.  From my understanding, if you open up a subclip, the IN-point should be at the very beginning and the OUT-point should be all the way the end (by default). 
    My problem is when I double-click on the subclip on the timeline and SOMETIMES, not all the time, the IN-point doesn't start at the beginning.  Sometimes it's a few frames from the beginning and sometimes it's a second.  The OUT-point is all the way at the end, where it's supposed to be, so that's not a problem.
    Can anyone tell me why my IN-point is not at the beginning?
    Thanks

    Click on the subclip that is demonstrating this problem in the Browser, and once it is selected type Command+9 to see the item properties. Post a screen shot of the item properties here.
    Next click anywhere on the timeline, and type Command+0 {zero} to see the Sequence settings. Post a screen shot of your sequence settings here.
    In the meantime, anytime FCP begins acting strangely, trashing preferences is a usually recommended as the first step. You can download Preference Manager from Digital Rebellion (free) at:
    http://www.digitalrebellion.com/prefman/
    which will allow you to save your exisiting preference before trashing in case you want to return to them.
    MtD

  • Why doesn't Personal.xlsb start when opening a different SS

    I have my personal.xlsb installed in the following folder;
    C:\Users\Toni Chaffin\AppData\Roaming\Microsoft\Excel\XLSTART
    Why when I open a already completed WorkBook, say stats.xlsm why doesn't my personal workbook open so I can run macros that I have saved in there
    Thanks
    Toni Chaffin aka Talisa

    I am experiencing the same exact issue. Running Office 2010 and whenever I open an xlsm file by double clicking on it in Windows Explorer, it opens in Excel but the macros do not open. If I open the VBA editor, only the current document is shown in there
    and not the macros.
    Opening Excel first and then dragging the spreadsheet file from Windows Explorer into Excel does work, and while the answers here are workarounds, they are far from solutions and are a very cumbersome workaround when dealing with multiple files.
    Can anyone help with a proper solution to the issue? I've tried adding my XLSTART folder to the "At startup, open all files in:" setting in the Advanced options menu, and that has done nothing.
    Thanks,
    Mike

  • Why do my creative cloud app don't start? I can't uppdate my apps, haven't been able for weeks. I have a fast internet, but the app doesn't start. It sucks!

    I can't uppdate my apps, haven't been able for weeks. I have a fast internet, but the app doesn't start. It sucks!

    Can you give us more to go on. Your OS? Which Creative Cloud app? Any error messages. You can download the Creative Cloud Cleaner tool and restart from scratch if you like.
    Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6

  • UB12 DRC error filter manager doesn't save filters

    In a PCB design, I have about 30 DRC errors that cannot be corrected due to the nature of the design (overlapping parts). These DRCs are listed in the results tab and the DRC tab of the spreadsheet view.
    On the DRC tab of the spreadsheet view, If I right-click the DRC list and select add to filter, the DRCs disappear from the list, and the DRC markers disappear from the workspace. - Cool.  I then switch to the results tab of the spreadsheet view, right click and clear the results list.  Then I run the DRC and netlist check.  Still no DRC markers in the workspace, no DRCs listed in the DRC tab of the spreadsheet view, no DRCs listed in the results tab of the spreadsheet view.  Just a note about filtered DRCs.
    I right click on the DRC list box in the spreadsheet view and select filter manager.  Filter manager appears and the filter I just created is shown.  I close the filter manager, then I save all and close UB. 
    I start UB again and open the same project and electronic design, the DRC markers show again in the workspace.  However, the DRC errors are not listed in the DRC tab of the spreadsheet view.  Even if I run a DRC and netlist check.  However, the DRCs are listed in the results tab of the spreadsheet view.  If I right click in the results list, I cannot filter the DRCs.  If I right click in the DRC list I can select add to filter, but nothing happens.  If I open the filter manager, no filter is shown.  If I use the task bar to switch to another program, then switch back, that's when the DRC error re appear in the DRC list. 
    What's with this coo-coo behavior, and why doesn't the filter manager save my DRC filters?
    Thanks
    Regards,
    Who

    Hi,
    The filters applied to the design should be removed everytime you re-open the design. These filters do not get saved along with the design. I tried out the filter manager and it seems to show the DRC errors right away after I re-open the design.
    Hope this helps.
    Regards,
    Tayyab R,
    National Instruments.

  • Maintaining Macs--Why doesn't Apple tell you more?

    This is not a problem that I need to solve but just something I've been wondering about. Why doesn't Apple tell people the routines they need to use to maintain their Macs?
    If you do a search on "maintenance" in Support the fourth item is Mac Maintenance Quick Assist:
    http://docs.info.apple.com/article.html?artnum=303602
    The things they tell you to do are:
    1) Keep Things Up to Date; 2) Put Your Files Away; 3) Name Your Files; 4) Prune Through Your Files; 5) Back Up Your Files; 6) Check for Viruses; 7) Clean the Outside
    Where is anything about running the maintenance scripts, checking permissions, checking your preferences, updating the databases, cleaning caches, or anything else that software programs like Onyx, Cocktail, etc make their purpose? Why don't they mention getting a program like Disc Warrior and running it periodically?
    The first item on their list is Keep Things Up to Date, meaning download system and application updates. Well after looking at these forums for a while I would have to say that is the worst thing you could do, as so many posts start, " Help! I updated my software and now things don't work...." Even if you look at this article about updating your software...
    http://docs.info.apple.com/article.html?artnum=106704
    ...nowhere does it mention repairing your permissions! Yet everywhere on this forum that is mentioned as one of the first things to do...unfortunately AFTER people are crazy with problems.
    I don't get it. Even in the manuals that come with the computers none of this stuff is mentioned (last time I looked) except in the troubleshooting section. Would you buy a car where the owner's manual had "change the oil regularly" listed in a section on what to do after you've blown your engine?
    Granted, a lot of people on this forum know all these things and do them regularly, but I have several friends with Macs who never do any regular maintenance because they've never been told to. One just called me last week because his iMac auto-updated and he had all sorts of problems.
    So why is this? Why isn't basic Mac maintenance explained to people better? Going back to the car analogy, people have been taught they have to give their cars tune-ups or face an eventual breakdown. Why not with Macs?
    I have been using Macs for years and enjoy looking into this geeky stuff. And I rarely have any serious problems. I would think it has a lot to do with the fact that I don't automatically update without checking MacFixit first and seeing what problems people are having and running a few simple maintenance routines periodically, plus backing up for good measure. Why isn't Apple more upfront with people about maintaining their Macs? Am I off-base here?
    ibook G3, imac G5   Mac OS X (10.4.9)  

    I'll provide you with several references you will find interesting reading:
    http://www.macfixit.com/article.php?story=20060413075624652
    http://www.macworld.com/2006/08/secrets/repairpermissions/index.php
    http://www.macworld.com/2006/03/secrets/tcopermissions/index.php
    http://www.atomicbird.com/node/view/29
    The document to which you referred is an old one that dates back a ways when permissions repairs were often still needed because many installers improperly changed permissions or caused permissions to change through other improper operations. In reality the only thing permissions repair affects are the permissions on OS X installed software for which there are receipts in the /Library/Receipts/ folder and third-party software that install a receipt that includes information on resetting permissions for that software. The vast majority of third-party applications provide no such information and repairing permissions has no impact on them.
    As for maintenance scripts they are now supposed to be run automatically regardless of whether the computer is turned on in the early AM, but this is an implementation with Tiger because Tiger introduced a new method of task launching. It's not 100 percent effective but it's better than it was. However, it's an easy problem to solve because there are some excellent utilities that solve the problem: Macaroni, Anacron, and Pseudo Anacron - VersionTracker or MacUpdate. I use Macaroni on all my Macs.
    Kappy's Personal Suggestions for OS X Maintenance
    For disk repairs use Disk Utility. For situations DU cannot handle the best third-party utilities are: Disk Warrior; DW only fixes problems with the disk directory, but most disk problems are caused by directory corruption; Disk Warrior 4.0 is now Intel Mac compatible. TechTool Pro provides additional repair options including file repair and recovery, system diagnostics, and disk defragmentation. TechTool Pro 4.5.2 is Intel Mac compatible; Drive Genius is similar to TechTool Pro in terms of the various repair services provided. The current version, 1.5.1, is Intel Mac compatible.
    OS X performs certain maintenance functions that are scheduled to occur on a daily, weekly, or monthly period. The maintenance scripts run in the early AM only if the computer is turned on 24/7 (no sleep.) If this isn't the case, then an excellent solution is to download and install a shareware utility such as Macaroni, JAW PseudoAnacron, or Anacron that will automate the maintenance activity regardless of whether the computer is turned off or asleep.
    OS X automatically defrags files less than 20 MBs in size, so unless you have a disk full of very large files there's little need for defragmenting the hard drive. As for virus protection there are few if any such animals affecting OS X. You can protect the computer easily using the freeware Open Source virus protection software ClamXAV. Personally I would avoid most commercial anti-virus software because of their potential for causing problems.
    I would also recommend downloading the shareware utility TinkerTool System that you can use for periodic maintenance such as removing old logfiles and archives, clearing caches, etc.
    For emergency repairs install the freeware utility Applejack. If you cannot start up in OS X, you may be able to start in single-user mode from which you can run Applejack to do a whole set of repair and maintenance routines from the commandline.
    When you install any new system software or updates be sure to repair the hard drive and permissions beforehand. I also recommend booting into safe mode before doing system software updates.
    Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
    1. Retrospect Desktop (Commercial - not yet universal binary)
    2. Synchronize! Pro X (Commercial)
    3. Synk (Backup, Standard, or Pro)
    4. Deja Vu (Shareware)
    5. PsynchX 2.1.1 and RsyncX 2.1 (Freeware)
    6. Carbon Copy Cloner (Freeware - 3.0 is a Universal Binary)
    7. SuperDuper! (Commercial)
    The following utilities can also be used for backup, but cannot create bootable clones:
    1. Backup (requires a .Mac account with Apple both to get the software and to use it.)
    2. Toast
    3. Impression
    4. arRSync
    Apple's Backup is a full backup tool capable of also backing up across multiple media such as CD/DVD. However, it cannot create bootable backups. It is primarily an "archiving" utility as are the other two.
    Impression and Toast are disk image based backups, only. Particularly useful if you need to backup to CD/DVD across multiple media.
    Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore.
    Additional suggestions will be found in Mac Maintenance Quick Assist.
    Referenced software can be found at www.versiontracker.com and www.macupdate.com.
    I know that Joe Average has no clue, but it's not Apple's responsibility to provide Joe Average with clues on how to use a computer. No more than it's not GM's responsibility to teach you how be an automotive mechanic or how to drive. Some things you have to take responsibility for yourself. It's just that Joe Average is too lazy to read the User Guide, buy a book, or in any other way learn about computers before buying one.
    As you can tell I am somewhat heavy handed about personal responsibility. Computers are essentially toys that aren't dangerous, but the person playing with them is. What really scares the crap out of me is that same Joe Average has a driver's license and may be old enough to drink liquor. When it comes to driving or drinking and driving Joe Average is no more competent.

  • Why doesn't version 17.0.0.169 show up in IE11 8.1 64-bit Manage Add-Ons?

    KB3044132 shows as installed for Flash Player update, and the Control Panel Flash Player icon for 32-bit shows 17.0.0.169 installed (I have 64-bit and 32-bit), but the Manage Add-Ons for Shockwave is Enabled and showing version 17.0.0.134! When I check the version using Adobe it only shows 17.0.0 and not the important part, so I cannot tell if Adobe detects 17.0.0.169 or 17.0.0.134! I think I need to know if IE11 64-bit has 17.0.0.169 also. Please advise because Microsoft technical support says to contact Adobe about this. Please delete my entry in Adobe general forums, Bridge general discussion as michaelh94875078. I did not see Flash Player on the list of communities provided during my first post.

    It occurs to me that maybe Microsoft will not allow their 17.0.0.169 KBitem to go out until their next update on the second Tuesday of May for their convenience and reputation! I want any update for Flash Player to be installed immediately for security. That is why I tend to use Firefox with NoScript and Web of Trust when I use a Google search. I will be watching the next Microsoft update to note if the KBitem it said was not appropriate for my computer - goes in!
    Sent from Yahoo Mail on Android
    From:"m_vargas" <[email protected]>
    Date:Wed, Apr 22, 2015 at 4:15 PM
    Subject:[Using Flash Player] Why doesn't version 17.0.0.169 show up in IE11 8.1 64-bit Manage Add-Ons?
    Why doesn't version 17.0.0.169 show up in IE11 8.1 64-bit Manage Add-Ons?
    created by m_vargas in Using Flash Player - View the full discussion
    Hi michaelh94875078,
    I'm sorry, I misread your previous post and thought it had been installed. From my experience with Microsoft Updates is that some times they depend on some update being installed.  I'll run Windows Updates and install all updates, then run Windows Updates again after all updates finish installing. Sometimes it finds new updates that weren't there before, and sometimes it doesn't.  You can try that route, or download the Microsoft update posted at the bottom of the Flash Player Issues | Windows 8 page.  Download the one that corresponds with your OS version. You may want to bookmark this tech note for future reference in case Microsoft Updates fails to detect the update is available for your system.
    Maria
    If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7467865#7467865 and clicking ‘Correct’ below the answer
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
    Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7467865#7467865
    To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following"      
    Start a new discussion in Using Flash Player by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.

  • [SOLVED] Xorg doesn't start after upgrade to 1.17.1

    Archlinux i686
    Intel Core 2 Duo 6600
    01:00.0 VGA compatible controller: NVIDIA Corporation G71 [GeForce 7900 GT/GTO] (rev a1)
    After following upgrades:
    [2015-02-26 03:27] [PACMAN] Running 'pacman -S mesa mesa-demos mesa-libgl'
    [2015-02-26 03:27] [ALPM] transaction started
    [2015-02-26 03:28] [ALPM] upgraded mesa (10.4.2-1 -> 10.4.5-1)
    [2015-02-26 03:28] [ALPM] upgraded mesa-libgl (10.4.2-1 -> 10.4.5-1)
    [2015-02-26 03:28] [ALPM] upgraded mesa-demos (8.2.0-3 -> 8.2.0-4)
    [2015-02-26 03:28] [ALPM] transaction completed
    [2015-02-26 03:28] [PACMAN] Running 'pacman -S xorg-server xorg-server-common'
    [2015-02-26 03:29] [ALPM] transaction started
    [2015-02-26 03:29] [ALPM] removed xf86-video-vesa (2.3.2-5)
    [2015-02-26 03:29] [ALPM] removed xf86-video-nouveau (1.0.11-2)
    [2015-02-26 03:29] [ALPM] removed xf86-video-modesetting (0.9.0-2)
    [2015-02-26 03:29] [ALPM] upgraded xorg-server-common (1.16.3-2 -> 1.17.1-3)
    [2015-02-26 03:29] [ALPM] upgraded xorg-server (1.16.3-2 -> 1.17.1-3)
    Xorg doesn't start after reboot and I found following kernel message:
    kernel: [drm:drm_mmap_locked] *ERROR* Could not find map
    and /var/log/Xorg.0.log looks like this:
    [ 5.591]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 5.591] X Protocol Version 11, Revision 0
    [ 5.591] Build Operating System: Linux 3.18.6-1-ARCH i686
    [ 5.591] Current Operating System: Linux emeria7 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:59:29 CET 2015 i686
    [ 5.591] Kernel command line: root=/dev/disk/by-label/archroot rw
    [ 5.591] Build Date: 22 February 2015 12:52:47PM
    [ 5.591]
    [ 5.592] Current version of pixman: 0.32.6
    [ 5.592] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 5.592] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 5.592] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 26 14:58:35 2015
    [ 5.597] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 5.597] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 5.598] (==) ServerLayout "ServerLayout0"
    [ 5.598] (==) No screen section available. Using defaults.
    [ 5.598] (**) |-->Screen "Default Screen Section" (0)
    [ 5.598] (**) | |-->Monitor "<default monitor>"
    [ 5.599] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 5.599] (**) | |-->Device "Device0"
    [ 5.599] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 5.599] (**) Option "BlankTime" "0"
    [ 5.599] (**) Option "StandbyTime" "0"
    [ 5.599] (**) Option "SuspendTime" "0"
    [ 5.599] (**) Option "OffTime" "0"
    [ 5.599] (==) Automatically adding devices
    [ 5.599] (==) Automatically enabling devices
    [ 5.599] (==) Automatically adding GPU devices
    [ 5.608] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 5.608] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 5.608] (**) Extension "Composite" is disabled
    [ 5.608] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 5.608] (II) Loader magic: 0x829e700
    [ 5.608] (II) Module ABI versions:
    [ 5.608] X.Org ANSI C Emulation: 0.4
    [ 5.608] X.Org Video Driver: 19.0
    [ 5.608] X.Org XInput driver : 21.0
    [ 5.608] X.Org Server Extension : 9.0
    [ 5.611] (EE) systemd-logind: failed to get session: PID 995 does not belong to any known session
    [ 5.611] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 5.612] (--) PCI:*(0:1:0:0) 10de:0291:107d:2a62 rev 161, Mem @ 0xfd000000/16777216, 0xc0000000/268435456, 0xfc000000/16777216, I/O @ 0x0000ac00/128, BIOS @ 0x????????/131072
    [ 5.612] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 5.613] (II) LoadModule: "glx"
    [ 5.616] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 5.632] (II) Module glx: vendor="X.Org Foundation"
    [ 5.632] compiled for 1.17.1, module version = 1.0.0
    [ 5.632] ABI class: X.Org Server Extension, version 9.0
    [ 5.632] (==) AIGLX enabled
    [ 5.632] (==) Matched nouveau as autoconfigured driver 0
    [ 5.632] (==) Matched nv as autoconfigured driver 1
    [ 5.632] (==) Matched nouveau as autoconfigured driver 2
    [ 5.632] (==) Matched nv as autoconfigured driver 3
    [ 5.632] (==) Matched modesetting as autoconfigured driver 4
    [ 5.632] (==) Matched fbdev as autoconfigured driver 5
    [ 5.632] (==) Matched vesa as autoconfigured driver 6
    [ 5.632] (==) Assigned the driver to the xf86ConfigLayout
    [ 5.632] (II) LoadModule: "nouveau"
    [ 5.632] (WW) Warning, couldn't open module nouveau
    [ 5.632] (II) UnloadModule: "nouveau"
    [ 5.632] (II) Unloading nouveau
    [ 5.632] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 5.633] (II) LoadModule: "nv"
    [ 5.633] (WW) Warning, couldn't open module nv
    [ 5.633] (II) UnloadModule: "nv"
    [ 5.633] (II) Unloading nv
    [ 5.633] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 5.633] (II) LoadModule: "modesetting"
    [ 5.633] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 5.634] (II) Module modesetting: vendor="X.Org Foundation"
    [ 5.634] compiled for 1.17.1, module version = 1.17.1
    [ 5.634] Module class: X.Org Video Driver
    [ 5.634] ABI class: X.Org Video Driver, version 19.0
    [ 5.634] (II) LoadModule: "fbdev"
    [ 5.634] (WW) Warning, couldn't open module fbdev
    [ 5.634] (II) UnloadModule: "fbdev"
    [ 5.634] (II) Unloading fbdev
    [ 5.634] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 5.634] (II) LoadModule: "vesa"
    [ 5.634] (WW) Warning, couldn't open module vesa
    [ 5.634] (II) UnloadModule: "vesa"
    [ 5.634] (II) Unloading vesa
    [ 5.634] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 5.634] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 5.634] (++) using VT number 7
    [ 5.635] (II) modeset(0): using drv /dev/dri/card0
    [ 5.635] (II) modeset(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 5.636] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
    [ 5.636] (==) modeset(0): RGB weight 888
    [ 5.636] (==) modeset(0): Default visual is TrueColor
    [ 5.636] (II) Loading sub module "glamoregl"
    [ 5.636] (II) LoadModule: "glamoregl"
    [ 5.636] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 5.647] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 5.647] compiled for 1.17.1, module version = 1.0.0
    [ 5.647] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 5.647] (II) glamor: OpenGL accelerated X.org driver based.
    [ 5.772] (II) glamor: EGL version 1.4 (DRI2):
    [ 5.786] (II) modeset(0): glamor initialized
    [ 5.786] (II) Loading sub module "dri2"
    [ 5.786] (II) LoadModule: "dri2"
    [ 5.786] (II) Module "dri2" already built-in
    [ 5.843] (II) modeset(0): Output DVI-0 has no monitor section
    [ 5.896] (II) modeset(0): Output DVI-1 has no monitor section
    [ 5.950] (II) modeset(0): Output TV-0 has no monitor section
    [ 6.006] (II) modeset(0): EDID for output DVI-0
    [ 6.006] (II) modeset(0): Manufacturer: SAM Model: 76f Serial#: 1110590261
    [ 6.006] (II) modeset(0): Year: 2011 Week: 8
    [ 6.006] (II) modeset(0): EDID Version: 1.3
    [ 6.006] (II) modeset(0): Digital Display Input
    [ 6.006] (II) modeset(0): Max Image Size [cm]: horiz.: 51 vert.: 29
    [ 6.006] (II) modeset(0): Gamma: 2.20
    [ 6.006] (II) modeset(0): DPMS capabilities: Off
    [ 6.006] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 6.006] (II) modeset(0): First detailed timing is preferred mode
    [ 6.006] (II) modeset(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
    [ 6.006] (II) modeset(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
    [ 6.006] (II) modeset(0): Supported established timings:
    [ 6.006] (II) modeset(0): 720x400@70Hz
    [ 6.006] (II) modeset(0): 640x480@60Hz
    [ 6.006] (II) modeset(0): 640x480@67Hz
    [ 6.006] (II) modeset(0): 640x480@72Hz
    [ 6.006] (II) modeset(0): 640x480@75Hz
    [ 6.006] (II) modeset(0): 800x600@56Hz
    [ 6.006] (II) modeset(0): 800x600@60Hz
    [ 6.006] (II) modeset(0): 800x600@72Hz
    [ 6.006] (II) modeset(0): 800x600@75Hz
    [ 6.006] (II) modeset(0): 832x624@75Hz
    [ 6.006] (II) modeset(0): 1024x768@60Hz
    [ 6.006] (II) modeset(0): 1024x768@70Hz
    [ 6.006] (II) modeset(0): 1024x768@75Hz
    [ 6.006] (II) modeset(0): 1280x1024@75Hz
    [ 6.006] (II) modeset(0): 1152x864@75Hz
    [ 6.006] (II) modeset(0): Manufacturer's mask: 0
    [ 6.006] (II) modeset(0): Supported standard timings:
    [ 6.006] (II) modeset(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 6.006] (II) modeset(0): #1: hsize: 1280 vsize 800 refresh: 60 vid: 129
    [ 6.006] (II) modeset(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 6.006] (II) modeset(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 6.006] (II) modeset(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 6.006] (II) modeset(0): #5: hsize: 1440 vsize 900 refresh: 75 vid: 3989
    [ 6.007] (II) modeset(0): #6: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
    [ 6.007] (II) modeset(0): #7: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 148.5 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 6.007] (II) modeset(0): Ranges: V min: 50 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 175 MHz
    [ 6.007] (II) modeset(0): Monitor name: SMBX2331
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 27.0 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 720 h_sync: 732 h_sync_end 796 h_blank_end 864 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 576 v_sync: 581 v_sync_end 586 v_blanking: 625 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 27.0 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 6.007] (II) modeset(0): Number of EDID sections to follow: 1
    [ 6.007] (II) modeset(0): EDID (in hex):
    [ 6.007] (II) modeset(0): 00ffffffffffff004c2d6f0735433242
    [ 6.007] (II) modeset(0): 0815010380331d782aee91a3544c9926
    [ 6.007] (II) modeset(0): 0f5054bfef80714f8100814081809500
    [ 6.007] (II) modeset(0): 950fa940b300023a801871382d40582c
    [ 6.007] (II) modeset(0): 4500fd1e1100001e011d007251d01e20
    [ 6.007] (II) modeset(0): 6e285500fd1e1100001e000000fd0032
    [ 6.007] (II) modeset(0): 4b1f5111000a202020202020000000fc
    [ 6.007] (II) modeset(0): 00534d4258323333310a2020202001ee
    [ 6.007] (II) modeset(0): 02031cf14890041f0514131203230907
    [ 6.007] (II) modeset(0): 078301000066030c00100080011d80d0
    [ 6.007] (II) modeset(0): 721c1620102c2580fd1e1100009e011d
    [ 6.007] (II) modeset(0): 8018711c1620582c2500fd1e1100009e
    [ 6.007] (II) modeset(0): 011d00bc52d01e20b8285540fd1e1100
    [ 6.007] (II) modeset(0): 001e8c0ad090204031200c405500fd1e
    [ 6.007] (II) modeset(0): 110000188c0ad08a20e02d10103e9600
    [ 6.007] (II) modeset(0): fd1e110000180000000000000000004c
    [ 6.007] (II) modeset(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
    [ 6.007] (II) modeset(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
    [ 6.007] (II) modeset(0): Printing probed modes for output DVI-0
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1600x1200"x65.0 175.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (81.2 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1400x1050"x74.8 155.80 1400 1464 1784 1912 1050 1052 1064 1090 +hsync +vsync (81.5 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.0 170.24 1024 1108 1220 1416 768 768 770 801 doublescan -hsync +vsync (120.2 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x60.0 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 6.008] (II) modeset(0): Modeline "960x720"x75.0 148.50 960 1032 1144 1320 720 720 722 750 doublescan -hsync +vsync (112.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "960x720"x60.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "928x696"x75.0 144.00 928 992 1104 1280 696 696 698 750 doublescan -hsync +vsync (112.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "928x696"x60.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
    [ 6.008] (II) modeset(0): Modeline "896x672"x75.0 130.50 896 944 1052 1228 672 672 674 708 doublescan -hsync +vsync (106.3 kHz d)
    [ 6.008] (II) modeset(0): Modeline "896x672"x60.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
    [ 6.008] (II) modeset(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x75.0 101.25 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (93.8 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x70.0 94.50 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (87.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x65.0 87.75 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (81.2 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x60.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 6.008] (II) modeset(0): Modeline "700x525"x74.8 77.90 700 732 892 956 525 526 532 545 doublescan +hsync +vsync (81.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "700x525"x60.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x512"x75.0 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (80.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x512"x60.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x60.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "576x432"x75.0 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (67.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x75.0 39.38 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (60.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
    [ 6.008] (II) modeset(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x75.1 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (46.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x72.8 15.75 320 332 352 416 240 244 246 260 doublescan -hsync -vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x75.0 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (37.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
    [ 6.063] (II) modeset(0): EDID for output DVI-1
    [ 6.116] (II) modeset(0): EDID for output TV-0
    [ 6.116] (II) modeset(0): Output DVI-0 connected
    [ 6.116] (II) modeset(0): Output DVI-1 disconnected
    [ 6.116] (II) modeset(0): Output TV-0 disconnected
    [ 6.116] (II) modeset(0): Using exact sizes for initial modes
    [ 6.116] (II) modeset(0): Output DVI-0 using initial mode 1920x1080
    [ 6.116] (II) modeset(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 6.116] (==) modeset(0): DPI set to (96, 96)
    [ 6.116] (II) Loading sub module "fb"
    [ 6.116] (II) LoadModule: "fb"
    [ 6.117] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 6.118] (II) Module fb: vendor="X.Org Foundation"
    [ 6.118] compiled for 1.17.1, module version = 1.0.0
    [ 6.118] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 6.118] (==) Depth 24 pixmap format is 32 bpp
    [ 6.462] (==) modeset(0): Backing store disabled
    [ 6.462] (==) modeset(0): Silken mouse enabled
    [ 6.464] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 6.535] (==) modeset(0): DPMS enabled
    [ 6.535] (WW) modeset(0): Option "EXANoComposite" is not used
    [ 6.535] (II) modeset(0): [DRI2] Setup complete
    [ 6.535] (II) modeset(0): [DRI2] DRI driver: nouveau
    [ 6.535] (II) modeset(0): [DRI2] VDPAU driver: nouveau
    [ 6.535] (--) RandR disabled
    [ 6.551] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 6.551] (II) AIGLX: enabled GLX_ARB_create_context
    [ 6.551] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 6.551] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 6.551] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 6.551] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 6.551] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 6.551] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 6.551] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 6.552] (II) AIGLX: Loaded and initialized nouveau
    [ 6.552] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 6.559] (II) modeset(0): Setting screen physical size to 507 x 285
    [ 6.741] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 6.741] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.741] (**) Power Button: Applying InputClass "Keyboard Defaults"
    [ 6.741] (II) LoadModule: "evdev"
    [ 6.741] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 6.744] (II) Module evdev: vendor="X.Org Foundation"
    [ 6.744] compiled for 1.16.2, module version = 2.9.1
    [ 6.744] Module class: X.Org XInput Driver
    [ 6.744] ABI class: X.Org XInput driver, version 21.0
    [ 6.744] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.744] (**) Power Button: always reports core events
    [ 6.744] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 6.744] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.744] (--) evdev: Power Button: Found keys
    [ 6.744] (II) evdev: Power Button: Configuring as keyboard
    [ 6.744] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 6.744] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 6.744] (**) Option "xkb_rules" "evdev"
    [ 6.744] (**) Option "xkb_model" "pc104"
    [ 6.744] (**) Option "xkb_layout" "us"
    [ 6.744] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.780] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 6.780] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.780] (**) Power Button: Applying InputClass "Keyboard Defaults"
    [ 6.780] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.780] (**) Power Button: always reports core events
    [ 6.780] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 6.780] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.780] (--) evdev: Power Button: Found keys
    [ 6.780] (II) evdev: Power Button: Configuring as keyboard
    [ 6.780] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
    [ 6.780] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 6.780] (**) Option "xkb_rules" "evdev"
    [ 6.780] (**) Option "xkb_model" "pc104"
    [ 6.780] (**) Option "xkb_layout" "us"
    [ 6.780] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.781] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
    [ 6.781] (II) No input driver specified, ignoring this device.
    [ 6.781] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event10)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event5)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event6)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event7)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event8)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event9)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.784] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event1)
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 6.784] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event1"
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc050
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 6.784] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/0003:046D:C050.0001/input/input1/event1"
    [ 6.784] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 8)
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
    [ 6.785] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
    [ 6.785] (II) No input driver specified, ignoring this device.
    [ 6.785] (II) This device may have been added with another device file.
    [ 6.785] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 6.785] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 6.785] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
    [ 6.785] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 6.785] (**) AT Translated Set 2 keyboard: always reports core events
    [ 6.785] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 6.785] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 6.785] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 6.785] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 6.785] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 6.785] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 6.785] (**) Option "xkb_rules" "evdev"
    [ 6.785] (**) Option "xkb_model" "pc104"
    [ 6.785] (**) Option "xkb_layout" "us"
    [ 6.785] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.803] (EE)
    [ 6.803] (EE) Backtrace:
    [ 6.803] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x132) [0x81df9e2]
    [ 6.804] (EE) 1: ? (?+0x132) [0xb7787cc5]
    [ 6.804] (EE) 2: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x4cd7) [0xb6e2a1c7]
    [ 6.806] (EE) 3: /usr/lib/xorg-server/Xorg (xf86_show_cursors+0x688) [0x80f9008]
    [ 6.806] (EE) 4: /usr/lib/xorg-server/Xorg (xf86DestroyCursorInfoRec+0xcf8) [0x8103fc8]
    [ 6.806] (EE) 5: /usr/lib/xorg-server/Xorg (RamDacHandleColormaps+0x67b) [0x810218b]
    [ 6.807] (EE) 6: /usr/lib/xorg-server/Xorg (miPointerUpdateSprite+0x25d) [0x81c648d]
    [ 6.808] (EE) 7: /usr/lib/xorg-server/Xorg (miPointerUpdateSprite+0x4c1) [0x81c6b31]
    [ 6.808] (EE) 8: /usr/lib/xorg-server/Xorg (CompositeRegisterImplicitRedirectionException+0x4199) [0x8114399]
    [ 6.809] (EE) 9: /usr/lib/xorg-server/Xorg (PanoramiXRenderReset+0x72a) [0x815915a]
    [ 6.810] (EE) 10: /usr/lib/xorg-server/Xorg (ConfineToShape+0x9f1) [0x80843b1]
    [ 6.810] (EE) 11: /usr/lib/xorg-server/Xorg (WindowHasNewCursor+0x3b) [0x8084f2b]
    [ 6.810] (EE) 12: /usr/lib/xorg-server/Xorg (ChangeWindowAttributes+0xb7c) [0x80aa9ec]
    [ 6.811] (EE) 13: /usr/lib/xorg-server/Xorg (ProcBadRequest+0x209) [0x8074a49]
    [ 6.811] (EE) 14: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x3a6) [0x807abf6]
    [ 6.811] (EE) 15: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x42f) [0x807edaf]
    [ 6.811] (EE) 16: /usr/lib/xorg-server/Xorg (miPolyFillRect+0x27f) [0x8068ddf]
    [ 6.814] (EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xde) [0xb72d864e]
    [ 6.814] (EE) 18: /usr/lib/xorg-server/Xorg (_start+0x21) [0x8068bd9]
    [ 6.814] (EE)
    [ 6.814] (EE) Segmentation fault at address 0x0
    [ 6.814] (EE)
    Fatal server error:
    [ 6.814] (EE) Caught signal 11 (Segmentation fault). Server aborting
    [ 6.814] (EE)
    [ 6.814] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 6.814] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 6.814] (EE)
    [ 6.815] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 6.817] (EE) Server terminated with error (1). Closing log file.
    Note the segfault in modesetting_drv.so!
    Any help?
    I tried to reinstall dependencies of xorg-server and mesa. And then I even went through with the whole system update which I postponed for a few weeks because of the KDE changes. Sadly even the whole system update didn't help.
    Is it possible that any old config files can cause this?
    EDIT:
    I tried kernel parameter "nouveau.modeset=0" but it didn't help.
    Last edited by cro (2015-02-26 16:33:19)

    Ok, I guess I solved it by reinstalling xf86-video-nouveau.
    Funny business! Why did the upgrade to xorg-server 1.17.1 force me to remove it when it is still needed??
    And why does that lead to mysterious error messages and segfault??
    I discovered it accidentally when I stumbled upon the fact that the package was still installed on my newer x86-64 Arch installation despite being on xorg-server 1.17.1.

Maybe you are looking for

  • Incoming attachment documents in MS Word not readable

    Just purchased new Mac with 10.5 operating system.  Had contents of hard drive transferred to new computer.  Incoming attachments in MS Word are not readable - letters and symbols interspersed with readable parts of document.  Had an older version of

  • Sequencing Java

    Hi all I googled how to sequence java using app-v 5 however its a rather confusing as one article will talk about how to use the deployment. properties file another will talk about using power shell to use only the current version of java in the bubb

  • Xmltype.transform() with stylesheet that includes another stylesheet

    I' trying to use xmltype.transform() with a stylesheet that includes/imports another stylesheet. But this results in a 'ORA-03113: End of communication channel'. Is xsl:include or xsl:import supported? This is the first stylesheet: <?xml version="1.0

  • Merge times in publisher catalog merge

    I using Publisher Catalog merge to create certificates for our swimming club with the kids times recorded on them. But when I merge times with hundreds of seconds that are over 60 seconds the hundreds of seconds are rounded up - for example 1.75 will

  • Problem viewing online bills etc

    I am having problems viewing my online account - for the the last two weeks I have been unable to view any of my details - the webpage says "thankyou for registering blah blah your billing details will be available in 3 days" I have called up and spo