NullPointerException in 1.4.2 for some Colors
When trying to get my app to build with 1.4.2, I noticed that I am getting a nullpointer exception when trying to get some colors from the tree, such as "Tree.selectionBorderColor". I looked in the source, and it seems that there has been a change which now maps some of these colors to other things, in this case, focusHighlightBorder. Previously, these colors were mapped to explicit colors. This happens with both the new windows and gtk lnfs.
Anyone have a fix for this issue?
I'm using 1.4 and 1.3 and most of my programs run fine, but to be on the safe side use the deprecate option with the java byte code compiler.
ie. c:\javac app.java -deprecation (win32)
./javac app.java -deprecation (Linux OS)
use the -deprecation option if you get a deprecated API warning when you compile your code, since you are using 1.4.1 API function/methods.
Similar Messages
-
Palm Desktop 4.2 - Text of color coded calendar entries are hidden for some colors
Environment:
Treo 680
Palm Desktop 4.2 running on Windows XP Pro
Color coded calendar entries have been working great since I got my phone over a year ago. When I added a new color category (bringing my total to 7 categories) I noticed that some of my calendar entries showed the color coded bar for the appointment, but the text for the entry was hidden. Nor was I able to edit the entry using Palm Desktop since any attempt to select the entry tries to create a new entry.
Thinking that I had exceeded a limit for the number of color categories I deleted the new category (so the entries were now unfiled). Now, all but one of my color categories are affected (color bar for appointment, but no text visible), including those marked with a category of "undefined".
The only color that now shows the text for calendar entries is my default category (not unfiled). This affects all of my existing calendar entries and any new ones I create, regardless of whether I create them on the Treo or using Palm Desktop.
If I press <tab> to cycle through my appointments on the page, it selects only those for my default color cateogry where the text of the entry is visible (i.e. it skips all the other appointments).
The calendar entries are all visible on my Treo, thankfully.
I have not installed any new apps or updates.
I've not been able to find anyone else reporting this problem.
My next step will be to restore my backup from last week, but I was hoping to avoid that if possible, so any advice would be greatly appreciated.
Thanks in advance!
Post relates to: Treo 680 (AT&T)
This question was solved.
View Solution.Pardon my ignorance, but where do I set categories to all?
Tools > Categories
Whichever category I select here becomes the default category and its entries will be visible, but all other categories will be hidden. My only other options are New, Delete, Rename and Help.
The only other configuration setting for categories that I can find is under
Tools -> Preferences
I have the checkbox "Display color-coded categories" checked
Thanks!
Post relates to: Treo 680 (AT&T) -
S:TextArea How change color for some chars in text?
I have s:TextArea and i need in runtime change color for some chars displayed in text.
How i must to do this correctly?pcardinale wrote:
Initially, a control has no caption. It's not just that the caption string is empty and the caption not visible, but the caption object does not exist.
I think this should probably be changed in future versions, because even if each control had a caption, it would still be a negligible small part of the VI. The current behavior made sense many years ago where HD and memory space was very precious. Not any more!
This issue comes up often enough that it warrants addressing the root of the problem.
It is hard to convince the casual that the caption does not exist if he can simply do a "show caption" at edit time and it will show in all glory, even with the default set to the current label. It is confusing!
There is even an idea about this that seems worth supporting (also read the link in the discussion).
What do you think?
LabVIEW Champion . Do more with less code and in less time . -
For some reason, "HSL" is gone from my develop panel. I used to be able to adjust specific colors (blues, greens etc) for saturation, luminance and so on. But that option is now gone from my develop panel. How do I get it back?
Right-click the title bar of any of the panels in the righthand column of the Develop module (for example, the Basic panel) and choose "Adjustments" from the panel list that appears.
-
Photoshop CS6 save for web some colors change?
I have a picture with large area of color: #fffdfd, when I save it for web (jpg) this color is changed to #fefcfd (in JPG).
I just can not save as JPG with #fffdfd.
(was trying uncheck convert to sRGB, do not embed color profile - always #fffdfd changes to #fefcfd when save for web)
However, color #fefcfd when save for web , does not change.
Why some colors change and some not? Is it a bug ?
Window7 64bit, Photoshop CS6Save for Web & Devices will strip some color data from the file.
Browsers aren't color managed. Most file formats on browsers assume they're sRGB. While Photoshop gives you an option of embedding sRGB to the document color space, it also strips off data that is not relevant. This is a common occurence.
PNG-24 on the other hand will give you the exact color match.
Also, Save for W&D, JPG quality matters a lot - The same color at Quality 10,20,30,40,50...100 wil give you different color reproductions on the JPG end output.
If you're concerned that much about an offset of +/- 1 hex value to your RGB colorspace, dont save for web & devices. Do a 'Save As' instead. Then use an image editing/ resizing application such as ResizeMe to resize the quality of your document. This, in most cases will retain colorspace information but just drop the resolution and quality of the image - giving you a lesser filesize.
On a sidenote, You may also want to read this article on how to best manage color spaces: http://viget.com/inspire/the-mysterious-save-for-web-color-shift -
I have CS3 and after I chose a color with the eye dropper tool, the filler fills in a grayer version of the color for some reason. Everything was fine till I accidentally picked the color sampler tool instead of the eye dropper tool. I undid that, but then after that everything with the regular eye dropper tool and the fill tool got messed up. How can I fix it?
Sorry, I am new to the forum, and a novice with not much knowledge about computers. Sorry if some terms that I use here may not be entirely correct, as I am ignorant of terms of the trade. My Operating system is Mac 10.6.8. I am using Photoshop 10.0.1. I am doing a many layered color RGB setting artwork from scanned and photo images, 8 bits/channel. I have been working on this project for a month without any problems. I was using the eye dropper tool. I selected a color in my artwork and it showed up in the background color box, in the tools window, as a match from the sample that I had taken. Then I selected an area, with the lasso tool, and I accidentally picked the tool called "color sample tool", that puts a little target on the sample area and then a box pops up with numbers that move when the tool moves. That wasn't what I wanted, so I got out of there and chose the eye dropper, I selected the color, it looked good in the box in the tools window, but then when I went up to the fill command and chose fill ( which was set at 100%). I filled the selection, but it was not the color I chose that is in box, it was a grayed and lightened version of the one that I chose. I checked the layers setting and the opacity and fill were at 100%, as was the fill setting. I can't figure out what is making it not fill in the color that is chosen in the tools color window. Does anyone on this forum have an idea of what might be happening and how to fix it?
-
Canon MP780 Color Option, Quality and Media, etc crossed out for SOME apps
Hi,
I have a Canon MP 780 attached to an old G4 macbook (running 10.4.11) that I'm using as a print server via printer sharing. I'm sending print jobs from a MBPro 2.4 GHz Core Duo running Snow Leopard (10.6.2)
Before I updated to Snow Leopard, all the MP 780 printer functions worked perfectly. Now the Color Options, Quality and Media, Duplex Printing, Special Effects, Borderless Printing and Duplex Printing are crossed out for some application, but not for others. For example, I can print in Duplex from Microsoft Word and Pages, but not from Preview or Safari.
If I do the print job directly from the old MB that's acting as the print server, all the options are available, so this seems to be related to either Snow Leopard or printer sharing.
I have downloaded and installed all the latest drives/software I could find in the CanonUSA website.
Any thoughts on how to get these print services up and running for all my applications?
Thanks!
PeteHello Pete,
What you are seeing is a result of using a 32bit driver when using a 64bit application. Preview and Safari are 64bit, while MS Word and Pages are 32bit.
The solution is to use a driver that is written for 64bit (or more so the plugins used with the driver, such as Quality & Media, are 64bit). However, checking the Canon web site, there does not appear to be a 64bit driver available for your model.
So, you could look at forcing the 64bit apps, like Preview and Safari, to open in 32bit mode. With the application closed, find its icon in Finder > Application. Select it and perform a Get Info (File > Get Info or Command I). The Info window that appears will have a button that shows 'Open in 32-bit mode'. Tick this checkbox, close the Info window and then open the application. Now you should find that the Canon plugins such as Quality & Media should be available without the line through them.
Pahu -
Color in fcp7 changes to crushed blacks and warm skin tones for some reason
So I have a MBP Retina, 2.6 GHZ, 16GB memory, 512 SSD. I have two external displays LG IPS LED ones connected via hdmi. For some strange reason, when I perform a given function or just randomly the color of my video becomes highly contrasted, and warm. When I first begin my project everything looks great, but say for example I go to Window>Arrange>Standard, the windows will orgainze themsleves as usual, but then the color will become drastically crushed (see before and after photos below) The image becomes heavily contrasted as well as very warm in the red spectrum. When I disconnect the monitor to see if it is an issue of the external display and just view FCP on my laptop, the images remain the same, crushed blacks and warm/redish skin tones. But everything looks fine, if I close the program, disconnect the external displays and then recconnect them again and open FCP 7 again. It will NOT do this if I stay on my laptop only, seems to only do it when I have either one or two external displays attached.
Not sure if anyone has come accross this yet, any clues? The first photo is how it normally looks, the second is with the strange color annomily.In FCP, go to the menu Final Cut Pro > System Settings and click on the Playback Control Tab.
Make sure the Gamma Correction is set to Approximate:
MtD -
Display color problem - asking for a color solution
So I have this serious problem with my Macbook Pro.
Some months ago I suddenly saw green colors in black area's and pink line colors in white areas.
Text on white background was extremely frustrating to read, since it was surrounded with small pink lines and flickering.
Note this was only near max white and max black areas of the screen.
I found out that it was due to a hardware failure, since slightly bending the laptop (!!) would remove the problem
Attaching an external monitor doesn't show the defect, and booting in Windows 7 (bootcamp) still shows the same screen problem.
Searching the web, it appears that it was a NVidia related heat problem, known to my model, but the offer to get it fixed for free by apple (since it was a known issue) had already run out december 2012 (!!). I think my laptop is about 3-4 years old, and the battery pretty much died on me the first year, probably due to heavy usage and the graphic card getting too hot. There are small sweat/corosion marks of where my hand are placed when typing, on the aluminium, due to how hot my laptop got. It sometimes got so hot I couldn't touch the aluminium on the top left corner near the 1-2-Q-W keys.
Fixing my Macbook is too expensive. Just getting someone to look at it to diagnose it (without repairing it), costs a lot in my country, and we have no official apple store, only authorized resellers. I know it's probably the motherboard, because I tried to unscrew the backlid and gently touch certain area's on the motherboard with a pen, while the computer was still running, to find out where the short circuit was. I only started this kind of trying to "self service" it, because I knew how expensive replacing the motherboard would be (if that was even the issue?).
I have multiple times tried to place something up against the sensitive area's on the motherboard, and then screw back the backlid, to put some pressure on it, which at first worked brilliantly and removed the color issue for some weeks, before it started reappearing. I think the heat from the laptop slowly makes the motherboard adapt, and the problem returns. Extremely frustrating indeed.
I hope I can one day afford a Macbook Air, but until then, I don't want to throw more money after my poor macbook (which I pronbably can't sell anyway, like previous mac's I've owned, the day get a new. It's too worn out + battery got only 5min on a full charge).
I think it's wisest to rather save the money for a Macbook Air, and try to survive until then. Therefor I was hoping someone could help me with a temporary solution.
In Windows 7, using the Nvidia Control Panel to apply color management, I was able to adjust the individual color output values, and thereby remove the the screen issue! Maybe the colors are not as good anymore, but it sure beats not getting a headache after 10minutes trying to read an article.
I tried the same thing on the mac, using Preferences>Displays>Color>Calibrate, but this guide is much harder to use to get a decent result (since only the last 2 options really makes a difference, but changes the colors completely, which I can't change by going back to the first color settings since then it just undos the last step I just did. I'm currently writing this with a very blue pale screen.
I also tried to use ColorSync Utility, expecting to enter values manually, but contrary to the articles I read about using ColorSync, I cannot edit the values in the color profile I created (I can only change the ASCII text input fields). Trying to save the profile gives me the error 'The Document "screenbug.icc" could not be saved.'
I tried to look for alternative color calibration software, but most of them required hardware, or expensive full version to unlock the settings I needed (like SuperCal).
I hope some tech savy users out there that can help me, or at least make my life with my macbook less of a pain.
All help is much appreciated!!
PS: I've been a loyal Mac user since always. Few things I've learned is:
1) Don't buy the first version of new hardware. Wait about a month for reviews, to check for issues. I had a problem with an expensive MacPro that had to be replaced, but luckily for free since it was Apple's mistake. Sometimes Apple products also get minor internal changes/fixes without announcements, to help solve reported issues from early buyers.
3) Take care of you Mac, especially so because you can often sell your used Mac's for quite a value the day you want to upgrade. I've sold about 3 Mac's in my lifetime, for quite a gain, though I don't expect this macbook to do as well, if at all. But it's normally something to be cautious about.
3) Don't order custom configurations from the Apple Store, if you can live without it (+ it's usually crazy overprices). I payed extra to get the NVidia GeForce 9600M, and was happy with it for the first couple of years, but is now causing me all the problems I have today + made my Macbook worthless.
Stick with what the default configuration if possible, as other configurations might not have been tested carefully.Who exactly is your comment "I am asking you to fix this problem soon" directed at?
Remember that you are posting on a user to user forum so nobody can really help you. If you want to give feedback to Apple, then contact them directly at http://www.apple.com/feedback.
Also, if you have an iPhone 3G and iOS 4.2.1 is the latest software that you can install on your phone, then there is absolutely nothing that anyone can do to fix the problem if you want to install Skype that requires iOS 4.3 - what do you think anyone can magically do?
iPhone 3G is a very old phone now and if you want to install Skype on your phone, then you need to go out and buy a new iPhone - either a 4s or a 5. Nothing more to it. Buy a new phone. -
A different take on the "Save For Web" color shift issue...
Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
Nothing new here.
Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
Anyone know of such a beast? I would gladly pay for a plug-in that really works and fixes the problem.
And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
Anyone got a decent solution for this?Sorry, I think I'm being unclear. This has nothing to do with individual monitor profiles. In Proof Setup, "Monitor RGB" amounts to turning off ALL color management, and simply letting the monitor do what it will. It is what the vast majority of web browsers do (even if the operating system provides color management, the browsers don't take advantage of it), so that is what you need to consider for images that will be viewed on a web browser. If you convert your image to sRGB, select Monitor RGB in Proof Set up, and turn on Proof Colors, you will see the image as it would appear on a web browser (after you save it as a jpg or use "Save For Web/Devices" to save it as a jpg). Since almost everyone is running different uncalibrated monitors, there will be lots of variation in how it will look to them, so precise control of the color is unimportant.
That said, I would expect the color on a calibrated monitor (such as the one I use when editing) to be reasonably close to the colors I am seeing while editing in PS. To the extent a monitor deviates from "calibrated", those colors will vary, but a good monitor should show good colors. Unfortunately, this is NOT the case, as my previous post shows. The colors produced by the steps above are oversaturated and significantly shifted in hue. There is, to my mind, anyway, no reason for this. Adobe clearly knows what the mapping is between the colors as it displays them in PS and the un-controlled "Monitor RGB" -- that is, it is the color map they are using during normal editing display. If they were to reverse-apply that map prior to saving it as a jpg, then the image would appear on a browser on that same (presumably calibrated) monitor very similar to what you set up when editing. Anyone else viewing the image on a web browser with a calibrated monitor would also see good colors. To the extent other viewers' monitors are out of calibration, their colors will suck, but there's nothing you can do about that.
I guess in some sense I AM "asking for a Color-Mamangement-solution for a "non-Color-Management-situation", but specifically I'm asking for PS Color Management to do the best it can for non-Color-Managed situations that we all face every day.
Does that make more sense? -
Looking for a better solution to the "Save for web" color shift issue
Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
Nothing new here.
Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
Anyone know of such a beast? I would gladly pay for a plug-in that really works and fixes the problem.
And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
Anyone got a decent solution for this?Chris
I spent all day Googling and doing side by side comparisons of my old and new systems.
My display is a Dell U2410. It has several presets, including sRGB and Adobe RGB. I've been using sRGB.
On my OLD system, (Win XP, PsCS2, DwCS4) there seems to be no distinction between color managed and non color managed apps, even on this wide gamut display. I could capture (digital camera) in Adobe RGB, open and edit in PsCS2, save as .psd, convert to CMYK for print, or convert to sRGB for SFW. All images looked identical and they printed and displayed perfectly. I thought this was normal, and seemed logical. This also seems to be the source of my incorrect assumptions. I was trying to get my new machine to behave like my old one.
So I get this new machine (Windows 7, PsCS5, DwCS5) and now (still in sRGB display mode) all color managed apps appear de-saturated. Non color managed apps are OK. If I switch the display to Adobe RGB, color managed apps are OK, but non color managed apps are way too saturated. From my investigation, I believe this is normal behavior on a wide gamut display. I've tried changing the Control Panel > Display > Screen Resolution > Advanced settings > Color Management options, but to no avail. Either I'm missing something, or Windows 7 is doing color management differently.
It seems my only option now is to use Adobe RGB display setting for Ps, etc. and switch to sRGB for Dw and non color managed apps. Or, have 2 separate files for print and web. I've Googled 'til my eyes are numb and still not sure I'm getting this. Any enlightenment would be greatly appreciated.
Finally, I don't see an edit function here, so I can't remove my previous incorrect reply. Moderator, please feel free to do so.
Thanks -
[SOLVED] Getting freezes after using dwm for some time and exiting it
Hello, I have an Asus Ux51, with a fresh (less than a month) arch installation. If I recall correctly I had a couple of freezes in other occasions but I don't remember much about those so I rather focus on the only freeze I can more or less reproduce and I've been having lately. After using dwm for some time with a couple of programs opened (rTorrent, browser, and some terminals for instance), if I close dwm or just press the power button to shut down, it starts closing everything and either stays with a black screen, or hangs while X prints the log information. It's not always though, for example, if I just boot it, open dwm and close it without giving it much use it usually closes fine.
Tried googling a bit to see the usual ways to troubleshoot this but didn't get really far.
This is my /var/log/Xorg.0.log
[ 7.573]
X.Org X Server 1.14.2
Release Date: 2013-06-25
[ 7.573] X Protocol Version 11, Revision 0
[ 7.573] Build Operating System: Linux 3.9.7-1-ARCH x86_64
[ 7.574] Current Operating System: Linux arch 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64
[ 7.574] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=74e92d67-41b6-4911-8ceb-009ae8c9cdab ro quiet add_efi_memmap i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=!Windows 2012"
[ 7.574] Build Date: 01 July 2013 10:48:42AM
[ 7.574]
[ 7.574] Current version of pixman: 0.30.0
[ 7.574] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 7.574] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 7.574] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 10 19:08:34 2013
[ 7.574] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 7.575] (==) No Layout section. Using the first Screen section.
[ 7.575] (==) No screen section available. Using defaults.
[ 7.575] (**) |-->Screen "Default Screen Section" (0)
[ 7.575] (**) | |-->Monitor "<default monitor>"
[ 7.575] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 7.575] (==) Automatically adding devices
[ 7.575] (==) Automatically enabling devices
[ 7.575] (==) Automatically adding GPU devices
[ 7.578] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 7.578] Entry deleted from font path.
[ 7.578] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 7.578] Entry deleted from font path.
[ 7.578] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 7.578] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 7.578] Entry deleted from font path.
[ 7.578] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 7.578] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/
[ 7.578] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 7.578] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 7.578] (II) Loader magic: 0x7fdc20
[ 7.578] (II) Module ABI versions:
[ 7.578] X.Org ANSI C Emulation: 0.4
[ 7.578] X.Org Video Driver: 14.1
[ 7.578] X.Org XInput driver : 19.1
[ 7.578] X.Org Server Extension : 7.0
[ 7.578] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 7.579] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 7.580] (--) PCI:*(0:0:2:0) 8086:0166:1043:15a7 rev 9, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 7.580] (--) PCI: (0:1:0:0) 10de:0fd1:1043:15a7 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 7.580] Initializing built-in extension Generic Event Extension
[ 7.580] Initializing built-in extension SHAPE
[ 7.580] Initializing built-in extension MIT-SHM
[ 7.580] Initializing built-in extension XInputExtension
[ 7.580] Initializing built-in extension XTEST
[ 7.580] Initializing built-in extension BIG-REQUESTS
[ 7.580] Initializing built-in extension SYNC
[ 7.580] Initializing built-in extension XKEYBOARD
[ 7.580] Initializing built-in extension XC-MISC
[ 7.580] Initializing built-in extension SECURITY
[ 7.580] Initializing built-in extension XINERAMA
[ 7.580] Initializing built-in extension XFIXES
[ 7.580] Initializing built-in extension RENDER
[ 7.581] Initializing built-in extension RANDR
[ 7.581] Initializing built-in extension COMPOSITE
[ 7.581] Initializing built-in extension DAMAGE
[ 7.581] Initializing built-in extension MIT-SCREEN-SAVER
[ 7.581] Initializing built-in extension DOUBLE-BUFFER
[ 7.581] Initializing built-in extension RECORD
[ 7.581] Initializing built-in extension DPMS
[ 7.581] Initializing built-in extension X-Resource
[ 7.581] Initializing built-in extension XVideo
[ 7.581] Initializing built-in extension XVideo-MotionCompensation
[ 7.582] Initializing built-in extension XFree86-VidModeExtension
[ 7.583] Initializing built-in extension XFree86-DGA
[ 7.583] Initializing built-in extension XFree86-DRI
[ 7.584] Initializing built-in extension DRI2
[ 7.584] (II) LoadModule: "glx"
[ 7.585] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 7.586] (II) Module glx: vendor="X.Org Foundation"
[ 7.586] compiled for 1.14.2, module version = 1.0.0
[ 7.586] ABI class: X.Org Server Extension, version 7.0
[ 7.586] (==) AIGLX enabled
[ 7.587] Loading extension GLX
[ 7.587] (==) Matched intel as autoconfigured driver 0
[ 7.587] (==) Matched nouveau as autoconfigured driver 1
[ 7.587] (==) Matched nvidia as autoconfigured driver 2
[ 7.587] (==) Matched nv as autoconfigured driver 3
[ 7.587] (==) Matched intel as autoconfigured driver 4
[ 7.587] (==) Matched vesa as autoconfigured driver 5
[ 7.587] (==) Matched modesetting as autoconfigured driver 6
[ 7.587] (==) Matched fbdev as autoconfigured driver 7
[ 7.587] (==) Assigned the driver to the xf86ConfigLayout
[ 7.587] (II) LoadModule: "intel"
[ 7.588] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 7.592] (II) Module intel: vendor="X.Org Foundation"
[ 7.592] compiled for 1.14.2, module version = 2.21.12
[ 7.592] Module class: X.Org Video Driver
[ 7.592] ABI class: X.Org Video Driver, version 14.1
[ 7.592] (II) LoadModule: "nouveau"
[ 7.592] (WW) Warning, couldn't open module nouveau
[ 7.592] (II) UnloadModule: "nouveau"
[ 7.592] (II) Unloading nouveau
[ 7.592] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 7.592] (II) LoadModule: "nvidia"
[ 7.592] (WW) Warning, couldn't open module nvidia
[ 7.592] (II) UnloadModule: "nvidia"
[ 7.592] (II) Unloading nvidia
[ 7.592] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 7.592] (II) LoadModule: "nv"
[ 7.592] (WW) Warning, couldn't open module nv
[ 7.592] (II) UnloadModule: "nv"
[ 7.592] (II) Unloading nv
[ 7.592] (EE) Failed to load module "nv" (module does not exist, 0)
[ 7.592] (II) LoadModule: "vesa"
[ 7.593] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 7.593] (II) Module vesa: vendor="X.Org Foundation"
[ 7.593] compiled for 1.14.0, module version = 2.3.2
[ 7.593] Module class: X.Org Video Driver
[ 7.593] ABI class: X.Org Video Driver, version 14.1
[ 7.593] (II) LoadModule: "modesetting"
[ 7.593] (WW) Warning, couldn't open module modesetting
[ 7.593] (II) UnloadModule: "modesetting"
[ 7.593] (II) Unloading modesetting
[ 7.593] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 7.593] (II) LoadModule: "fbdev"
[ 7.593] (WW) Warning, couldn't open module fbdev
[ 7.593] (II) UnloadModule: "fbdev"
[ 7.593] (II) Unloading fbdev
[ 7.593] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 7.593] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), HD Graphics, HD Graphics 4600,
Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
HD Graphics 4600, Iris(TM) Pro Graphics 5200,
Haswell CRW Server (GT1), Haswell CRW Server (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, ValleyView PO board
[ 7.594] (II) VESA: driver for VESA chipsets: vesa
[ 7.594] (++) using VT number 1
[ 7.594] (WW) Falling back to old probe method for vesa
[ 7.594] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 7.594] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 7.594] (==) intel(0): RGB weight 888
[ 7.594] (==) intel(0): Default visual is TrueColor
[ 7.594] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
[ 7.594] (**) intel(0): Relaxed fencing enabled
[ 7.594] (**) intel(0): Wait on SwapBuffers? enabled
[ 7.594] (**) intel(0): Triple buffering? enabled
[ 7.594] (**) intel(0): Framebuffer tiled
[ 7.594] (**) intel(0): Pixmaps tiled
[ 7.594] (**) intel(0): 3D buffers tiled
[ 7.594] (**) intel(0): SwapBuffers wait enabled
[ 7.594] (==) intel(0): video overlay key set to 0x101fe
[ 7.594] (II) intel(0): Output eDP1 has no monitor section
[ 7.595] (--) intel(0): found backlight control interface /sys/class/backlight/acpi_video1
[ 7.596] (II) intel(0): Output VGA1 has no monitor section
[ 7.596] (II) intel(0): EDID for output eDP1
[ 7.596] (II) intel(0): Manufacturer: LGD Model: 323 Serial#: 0
[ 7.596] (II) intel(0): Year: 2012 Week: 0
[ 7.596] (II) intel(0): EDID Version: 1.4
[ 7.596] (II) intel(0): Digital Display Input
[ 7.596] (II) intel(0): 6 bits per channel
[ 7.596] (II) intel(0): Digital interface is DisplayPort
[ 7.596] (II) intel(0): Max Image Size [cm]: horiz.: 35 vert.: 19
[ 7.596] (II) intel(0): Gamma: 2.20
[ 7.596] (II) intel(0): No DPMS capabilities specified
[ 7.596] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 7.596] (II) intel(0): First detailed timing is preferred mode
[ 7.596] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 7.596] (II) intel(0): redX: 0.629 redY: 0.350 greenX: 0.349 greenY: 0.614
[ 7.596] (II) intel(0): blueX: 0.154 blueY: 0.112 whiteX: 0.313 whiteY: 0.329
[ 7.596] (II) intel(0): Manufacturer's mask: 0
[ 7.596] (II) intel(0): Supported detailed timing:
[ 7.596] (II) intel(0): clock: 138.0 MHz Image Size: 345 x 194 mm
[ 7.596] (II) intel(0): h_active: 1920 h_sync: 1952 h_sync_end 1988 h_blank_end 2088 h_border: 0
[ 7.596] (II) intel(0): v_active: 1080 v_sync: 1085 v_sync_end 1090 v_blanking: 1102 v_border: 0
[ 7.596] (II) intel(0): LG Display
[ 7.596] (II) intel(0): LP156WF4-SPB1
[ 7.596] (II) intel(0): EDID (in hex):
[ 7.596] (II) intel(0): 00ffffffffffff0030e4230300000000
[ 7.596] (II) intel(0): 00160104952313780a25b5a159599d27
[ 7.596] (II) intel(0): 1c505400000001010101010101010101
[ 7.596] (II) intel(0): 010101010101e83580a8703816402024
[ 7.596] (II) intel(0): 550059c2100000180000000000000000
[ 7.596] (II) intel(0): 00000000000000000000000000fe004c
[ 7.596] (II) intel(0): 4720446973706c61790a2020000000fe
[ 7.596] (II) intel(0): 004c503135365746342d535042310069
[ 7.596] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 7.597] (II) intel(0): Printing probed modes for output eDP1
[ 7.597] (II) intel(0): Modeline "1920x1080"x60.0 138.00 1920 1952 1988 2088 1080 1085 1090 1102 -hsync -vsync (66.1 kHz eP)
[ 7.597] (II) intel(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[ 7.597] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz d)
[ 7.597] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz d)
[ 7.597] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 7.597] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 7.597] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 7.597] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 7.598] (II) intel(0): EDID for output VGA1
[ 7.598] (II) intel(0): Output eDP1 connected
[ 7.598] (II) intel(0): Output VGA1 disconnected
[ 7.598] (II) intel(0): Using exact sizes for initial modes
[ 7.598] (II) intel(0): Output eDP1 using initial mode 1920x1080
[ 7.598] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 7.598] (II) intel(0): Kernel page flipping support detected, enabling
[ 7.598] (==) intel(0): DPI set to (96, 96)
[ 7.598] (II) Loading sub module "fb"
[ 7.598] (II) LoadModule: "fb"
[ 7.598] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 7.599] (II) Module fb: vendor="X.Org Foundation"
[ 7.599] compiled for 1.14.2, module version = 1.0.0
[ 7.599] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7.599] (II) Loading sub module "dri2"
[ 7.599] (II) LoadModule: "dri2"
[ 7.599] (II) Module "dri2" already built-in
[ 7.599] (II) UnloadModule: "vesa"
[ 7.599] (II) Unloading vesa
[ 7.599] (==) Depth 24 pixmap format is 32 bpp
[ 7.599] (II) intel(0): [DRI2] Setup complete
[ 7.599] (II) intel(0): [DRI2] DRI driver: i965
[ 7.599] (II) intel(0): Allocated new frame buffer 1920x1080 stride 7680, tiled
[ 7.599] (II) UXA(0): Driver registered support for the following operations:
[ 7.599] (II) solid
[ 7.599] (II) copy
[ 7.599] (II) composite (RENDER acceleration)
[ 7.599] (II) put_image
[ 7.599] (II) get_image
[ 7.599] (==) intel(0): Backing store disabled
[ 7.599] (==) intel(0): Silken mouse enabled
[ 7.600] (II) intel(0): Initializing HW Cursor
[ 7.600] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 7.600] (==) intel(0): DPMS enabled
[ 7.600] (==) intel(0): Intel XvMC decoder enabled
[ 7.600] (II) intel(0): Set up textured video
[ 7.600] (II) intel(0): [XvMC] xvmc_vld driver initialized.
[ 7.600] (II) intel(0): direct rendering: DRI2 Enabled
[ 7.600] (==) intel(0): hotplug detection: "enabled"
[ 7.613] (--) RandR disabled
[ 7.634] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 7.634] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 7.634] (II) AIGLX: enabled GLX_ARB_create_context
[ 7.634] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 7.634] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 7.634] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 7.634] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 7.634] (II) AIGLX: Loaded and initialized i965
[ 7.634] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 7.634] (II) intel(0): Setting screen physical size to 508 x 285
[ 7.669] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[ 7.669] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 7.669] (II) LoadModule: "evdev"
[ 7.669] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 7.670] (II) Module evdev: vendor="X.Org Foundation"
[ 7.670] compiled for 1.14.2, module version = 2.8.1
[ 7.670] Module class: X.Org XInput Driver
[ 7.670] ABI class: X.Org XInput driver, version 19.1
[ 7.670] (II) Using input driver 'evdev' for 'Video Bus'
[ 7.670] (**) Video Bus: always reports core events
[ 7.670] (**) evdev: Video Bus: Device: "/dev/input/event9"
[ 7.670] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 7.670] (--) evdev: Video Bus: Found keys
[ 7.670] (II) evdev: Video Bus: Configuring as keyboard
[ 7.670] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input10/event9"
[ 7.670] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[ 7.670] (**) Option "xkb_rules" "evdev"
[ 7.670] (**) Option "xkb_model" "pc104"
[ 7.670] (**) Option "xkb_layout" "us"
[ 7.684] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
[ 7.684] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 7.684] (II) Using input driver 'evdev' for 'Video Bus'
[ 7.684] (**) Video Bus: always reports core events
[ 7.684] (**) evdev: Video Bus: Device: "/dev/input/event8"
[ 7.684] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 7.684] (--) evdev: Video Bus: Found keys
[ 7.684] (II) evdev: Video Bus: Configuring as keyboard
[ 7.684] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input9/event8"
[ 7.684] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 7.684] (**) Option "xkb_rules" "evdev"
[ 7.684] (**) Option "xkb_model" "pc104"
[ 7.684] (**) Option "xkb_layout" "us"
[ 7.684] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 7.685] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.685] (II) Using input driver 'evdev' for 'Power Button'
[ 7.685] (**) Power Button: always reports core events
[ 7.685] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 7.685] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 7.685] (--) evdev: Power Button: Found keys
[ 7.685] (II) evdev: Power Button: Configuring as keyboard
[ 7.685] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event2"
[ 7.685] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 7.685] (**) Option "xkb_rules" "evdev"
[ 7.685] (**) Option "xkb_model" "pc104"
[ 7.685] (**) Option "xkb_layout" "us"
[ 7.685] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 7.685] (II) No input driver specified, ignoring this device.
[ 7.685] (II) This device may have been added with another device file.
[ 7.685] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 7.685] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 7.685] (II) Using input driver 'evdev' for 'Sleep Button'
[ 7.685] (**) Sleep Button: always reports core events
[ 7.685] (**) evdev: Sleep Button: Device: "/dev/input/event3"
[ 7.685] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 7.685] (--) evdev: Sleep Button: Found keys
[ 7.685] (II) evdev: Sleep Button: Configuring as keyboard
[ 7.685] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event3"
[ 7.685] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 7.685] (**) Option "xkb_rules" "evdev"
[ 7.685] (**) Option "xkb_model" "pc104"
[ 7.685] (**) Option "xkb_layout" "us"
[ 7.685] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 7.685] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 7.686] (II) config/udev: Adding input device USB2.0 HD UVC WebCam (/dev/input/event6)
[ 7.686] (**) USB2.0 HD UVC WebCam: Applying InputClass "evdev keyboard catchall"
[ 7.686] (II) Using input driver 'evdev' for 'USB2.0 HD UVC WebCam'
[ 7.686] (**) USB2.0 HD UVC WebCam: always reports core events
[ 7.686] (**) evdev: USB2.0 HD UVC WebCam: Device: "/dev/input/event6"
[ 7.686] (--) evdev: USB2.0 HD UVC WebCam: Vendor 0x4f2 Product 0xb36e
[ 7.686] (--) evdev: USB2.0 HD UVC WebCam: Found keys
[ 7.686] (II) evdev: USB2.0 HD UVC WebCam: Configuring as keyboard
[ 7.686] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input6/event6"
[ 7.686] (II) XINPUT: Adding extended input device "USB2.0 HD UVC WebCam" (type: KEYBOARD, id 10)
[ 7.686] (**) Option "xkb_rules" "evdev"
[ 7.686] (**) Option "xkb_model" "pc104"
[ 7.686] (**) Option "xkb_layout" "us"
[ 7.686] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event5)
[ 7.686] (II) No input driver specified, ignoring this device.
[ 7.686] (II) This device may have been added with another device file.
[ 7.686] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 7.686] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 7.686] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 7.686] (**) AT Translated Set 2 keyboard: always reports core events
[ 7.686] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 7.686] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 7.686] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 7.686] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 7.686] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 7.686] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 7.686] (**) Option "xkb_rules" "evdev"
[ 7.686] (**) Option "xkb_model" "pc104"
[ 7.686] (**) Option "xkb_layout" "us"
[ 7.686] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event7)
[ 7.686] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev touchpad catchall"
[ 7.686] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[ 7.687] (**) ETPS/2 Elantech Touchpad: Applying InputClass "Default clickpad buttons"
[ 7.687] (II) LoadModule: "synaptics"
[ 7.687] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 7.687] (II) Module synaptics: vendor="X.Org Foundation"
[ 7.687] compiled for 1.14.1, module version = 1.7.1
[ 7.687] Module class: X.Org XInput Driver
[ 7.687] ABI class: X.Org XInput driver, version 19.1
[ 7.687] (II) Using input driver 'synaptics' for 'ETPS/2 Elantech Touchpad'
[ 7.687] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 7.687] (**) Option "Device" "/dev/input/event7"
[ 7.810] (II) synaptics: ETPS/2 Elantech Touchpad: found clickpad property
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: x-axis range 0 - 3260 (res 32)
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: y-axis range 0 - 2119 (res 32)
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: pressure range 0 - 255
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: finger width range 0 - 15
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: buttons: left double triple
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: Vendor 0x2 Product 0xe
[ 7.810] (**) Option "TapButton1" "1"
[ 7.810] (**) Option "TapButton2" "2"
[ 7.810] (**) Option "TapButton3" "3"
[ 7.810] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[ 7.810] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 7.853] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input8/event7"
[ 7.853] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 12)
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MinSpeed is now constant deceleration 2.5
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MaxSpeed is now 1.75
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) AccelFactor is now 0.051
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) keeping acceleration scheme 1
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration profile 1
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[ 7.853] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[ 7.853] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse0)
[ 7.853] (**) ETPS/2 Elantech Touchpad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 7.853] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 7.853] (II) No input driver specified, ignoring this device.
[ 7.853] (II) This device may have been added with another device file.
Found this recent thread in the forums, I'll give REISUB a try late, but the times it freezed I remember trying to blindly reboot it, or switching off virtual console and couldn't.
In case it's of any use, this is my # uname -a
Linux arch 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux
Could it have something to do with the nvidia optimus setup that this laptop has? When installing arch I found out that there was no support yet for it so I'm just using the intel drivers (following what the arch wiki said).
Any ideas or advice to point me in the right direction would be very much appreciated.
Thanks in advance.
Last edited by contiver (2013-08-16 20:25:34)I don't start st in my .xinitrc. I launch it from dmenu and usually everything is fine. If I launch it from dwm's internal command using Alt-Shf-Return, X freezes 100% of the time. A workaround was suggested by st's main developer to call st like this:
static const char *termcmd[] = { "/bin/sh", "-c", "st", NULL };
but it didn't work for me.
Very rarely X will freeze anyway. I haven't been able to pin it down. When X fails, my journal returns this:
BUG: unable to handle kernel paging request at ffffc90014ce8000
IP: [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
PGD 7c00b067 PUD 7c018067 PMD 7b3eb067 PTE 0
Oops: 0002 [#1] PREEMPT SMP
Modules linked in: nls_cp437 vfat fat snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device snd_pcm snd_page_alloc snd_timer
CPU: 1 PID: 7520 Comm: X Not tainted 3.10.5-1-ck #1
Hardware name: /D410PT, BIOS MOPNV10N.86A.0155.2009.1106.0430 11/06/2009
task: ffff88007aa786b0 ti: ffff8800797ee000 task.ti: ffff8800797ee000
RIP: 0010:[<ffffffff812bfe7f>] [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
RSP: 0018:ffff8800797efaa8 EFLAGS: 00010212
RAX: 0000000003ffff5c RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000003ffff5c RSI: ffffc90014901520 RDI: ffffc90014ce7fe0
RBP: ffff8800797efab8 R08: 00000000ffffd700 R09: 0000000003f83204
R10: 0000000000000000 R11: ffffc90014ce7fd8 R12: ffffffffffffffff
R13: ffffc90014901520 R14: ffffffff812bfdf0 R15: 0000000000000320
FS: 00007fb350033880(0000) GS:ffff88007ea80000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffc90014ce8000 CR3: 000000007b104000 CR4: 00000000000007e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Stack:
0000000000000000 ffff88007a4d3000 ffff8800797efb28 ffffffff812bfbb9
ffffffff00000000 ffff88007c00c000 0000000000000000 ffffffff8186f240
0000000000000000 ffffffff00000006 ffffd700797efb58 ffff88007a4d3000
Call Trace:
[<ffffffff812bfbb9>] cfb_fillrect+0x1c9/0x400
[<ffffffff812ba2e5>] bit_clear_margins+0x165/0x190
[<ffffffff812b3633>] fbcon_clear_margins+0x63/0x90
[<ffffffff812b7a9f>] fbcon_switch+0x3df/0x570
[<ffffffff813200bd>] redraw_screen+0x17d/0x240
[<ffffffff812b6eeb>] fbcon_blank+0x20b/0x2d0
[<ffffffff81320767>] do_unblank_screen+0xa7/0x1b0
[<ffffffff813175d1>] vt_ioctl+0x10d1/0x1170
[<ffffffff8130b407>] tty_ioctl+0x277/0xb90
[<ffffffff8118fb21>] ? mntput_no_expire+0x41/0x150
[<ffffffff81183a3e>] do_vfs_ioctl+0x2de/0x4c0
[<ffffffff8117328e>] ? ____fput+0xe/0x10
[<ffffffff8107766c>] ? task_work_run+0x9c/0xe0
[<ffffffff81183ca3>] SyS_ioctl+0x83/0xa0
[<ffffffff814bab9d>] system_call_fastpath+0x1a/0x1f
Code: 08 45 01 d8 31 d2 44 89 c0 41 f7 f1 83 f8 07 89 c2 76 4f 44 8d 08 48 8d 3e 0f 1f 00 4c 89 17 4c 89 57 08 4c 89 57 10 4c 89 57 18 <4
RIP [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
RSP <ffff8800797efaa8>
CR2: ffffc90014ce8000
---[ end trace aff6cb5ad5097aef ]--- -
End of the road for my Color Classic???
Greetings. Lifelong Mac user here who, in the wake of Jobs’ passing, retrieved my Color Classic from the attic, thinking it would surely boot right up. It worked as recently as maybe 4-5 years ago, but all attempts over the past month to successfully boot it up have been in vain. After one purchase from Radio Shack and three from eBay, I’m 99 percent done throwing any more money at it. But I’d like to see if any of you could maybe help me out before I give up the ghost. I don’t have long, since I’ll need to return the internal HD I just bought off eBay soon if I want a refund. Here’s the rundown:
** Initially, it would boot up without the startup chime, show a grey screen for a minute or two (no icons at all), then give the eight-tone chimes of death.
** Buying a new PRAM battery led to it giving the startup chime and showing the smiling Mac, but that would give way to the flashing question mark over the floppy icon. I tried resetting PRAM, which did lead to the three successive startup chimes, but still got the question mark afterward.
** Next thing I did was buy a complete set of 7.1 discs off eBay. Using either the Disk Tools disc or the Install Me First disc, I would get the startup chime and smiling Mac, but then I couldn’t get past this message: “This startup disk will not work with this Macintosh. Use the latest installer to update this disk for this model.” For some reason, the mouse wouldn’t work when doing this, so I’d have to power off with the main switch and then eject the floppy with a paper clip. I would later learn that these discs apparently wouldn’t work on the CC because of a missing System Enabler.
** Next step: buying 7.6 Disk Tools discs off eBay. This time, the startup chime and happy Mac gave way to a sad Mac icon, a "0000000F / 00000066" error message and four-tone chimes of death. That led me to believe my factory HD was bad, sooooo …
** I bought an internal HD off eBay with 7.5 already installed on it. I had high hopes that this would finally do the trick. The heavens would open up and I would see the desktop. But ... after the swap, I was greeted once again with the flashing question mark. I disconnected and reattached the data and power cables to the HD three times, but to no avail. I tried booting off the 7.6 Disk Tools with this new HD, but got the sad Mac / "0000000F / 00000066" sequence once more. I tried booting off the 7.6 Disk Tools with no HD attached and got the same thing. This was the most depressing night of all.
** Today, with the new HD installed, I tried booting off of old 7.0.1 and 7.1 startup floppies my dad made back in the day -- and one or both of them actually progresses past the smiling Mac to the "Welcome to Macintosh" screen. But then, the "use the latest installer" screen takes over.
So this is where things stand. I'm holding out hope that I can having a working CC without spending any more money, but I'm not optimistic. Tonight I might trying washing the logic board in the dishwasher, as well as booting with the logic board disconnected and then pushing it in shortly after the startup chime (which I had tried with the factory HD without success).
Any thoughts? Ideas? Or should I call it a day, put it back on the side mantle in my living room, and go the Macquarium (or MacAntFarm) route down the road? Thanks in advance for your help!The Color Classic is pretty straight forward to work on because the motherboard is just a matter of pulling it out.
But I don't think it's a bad motherboard so that is the good news. Sounds like the original hard drive died but before you toss it try seeing if it is just a matter of the heads being stuck. Take it in hand and gently swish it back and forth a few times to see if it that will unstick the heads. If you had a clean room I would say open the drive and gently turn the platters than zip it back up and see if it will work.
The "new' hard drive you bought sounds like it is pooched as those clicking sounds are usually an indication of a bad drive so return it ASAP for a working one or a refund. But just in case if you look at your old hard drive does it have terminators on it, they will look like two long black strips with multiple prongs attaching them to the motherboard of the hard drive. Now look at the new one, does it have any or a place for them? Though my memory is foggy on SCSI drives but that 700 might have a jumper instead but that could be wrong.
In terms of the OS, you can run System 8 on it. But you must buy the Apple release version for all Macs which comes with a floppy disk to boot your CC as well as a CD with the system SW on it. The CD is white but you will need a SCSI CD drive to install the sw. The error messages tell me that those disks are the wrong ones and not something wrong with your CC.
Now if you were into experimenting..... the following motherboards from other compact Macs will work in your CC.
The motherboard from the LC 525 is a straight swap in and even the ports on the board mate up with the holes on the rear cover. The LC 550 as well, which was actually the motherboard that the CC II used.
The motherboard from the LC 575 will also work and that adds a 68040 cpu into the mix plus the upgrade to 72 pin simms which allows you to add up to 128mb of ram with a modification to the case of the CC. The two other boards I mentioned also take 72 pin simms so you can bump up your CC from 10mb to 32mb.
I wrote a short page on my experiments here, http://www.kevinomura.com/macs/colorclassic/index.html .
In any event I think it's just your hard drive that is the problem since your video sounds good, don't toss that CC as there are still collectors out there looking for them.
On other thought, since the hard drive is on a caddy with a zif socket it's possible that some of the pins have a bit of corrosion on them. Check the one's on the hard drive side and see if they look clean, if not clean them. on the computer side that will be tougher since it's deep in the case but a few insertions of the drive might be enough to knock some of the corrosion off and make a better contact. -
This program won't work for some reason
I'm having trouble with getting this program to do what I want. It reads in a file and identifies certain parts that follow the rules I've given. The first version below is one that works. It simply prints out the string if it meets the conditions in the if statements. The second one will compile but shows no data. I know it stores the values in the arrays sortstem and sortdg becuase I put the println statement directly after the code for storing them and it worked. However, when I put it where it is now, it will not work. Any suggestions? Also, I get an error after the program runs for both versions: It says exception in thread "main" Java.lang.NullPointerException at tokens.main(tokens.java.69) (this was for the first program).
import java.io.*;
import java.util.*;
class tokens {
public static void main(String args[]) throws IOException {
int i; //int to read in the data from the text file
int count = -1;
int countt = -1;
int countc = 0; //int to put data into a char array
FileInputStream fin; //input stream
char array[] = new char[10000]; //array to hold chars from the text file
String s; //chars are transfered to this String
int index; //index of the names I'm searching for in the string
String tokens[] = new String[10000];
try {
fin = new FileInputStream(args[0]);
} catch (FileNotFoundException e) {
System.out.println("File not Found");
return;
} catch (ArrayIndexOutOfBoundsException e) {
System.out.println("Usage: ShowFile File");
return;
do {
i = fin.read();
if (i != -1) {
if (count==array.length-1) { //this expands the array if more space is needed
char temp[] = new char[array.length+5000];
for (int j = 0; j < array.length; j++) temp[j] = array[j];
array = temp;
array[++count] = (char) i;
else
array[++count] = (char) i;
} while(i != -1);
fin.close();
s = new String(array);
StringTokenizer st = new StringTokenizer(s);
while (st.hasMoreTokens()) {
if (countt==tokens.length-1) { //this expands the array if more space is needed
String temp1[] = new String[tokens.length+5000];
for (int j = 0; j < tokens.length; j++) temp1[j] = tokens[j];
tokens = temp1;
tokens[++countt] = st.nextToken();
else
tokens[++countt] = st.nextToken();
if (tokens[4].startsWith("stem")) {
if (tokens[4].equals(tokens[201])) { //Skip this one
else
if ((tokens[9].equals("32")) && (tokens[15].equals("31"))
&& (tokens[21].equals("30")) && (tokens[27].equals("29"))
&& (tokens[33].equals("28")) && (tokens[39].equals("27"))) {
System.out.println(tokens[4]);
for (int k = 201; k < tokens.length-198; k++) {
if (tokens[k].startsWith("stem")) {
if ((tokens[k].equals(tokens[k+197])) || (tokens[k].equals(tokens[k-197]))) {
//Skip this one
else
if ((tokens[k+5].equals("32")) && (tokens[k+11].equals("31"))
&& (tokens[k+17].equals("30")) && (tokens[k+23].equals("29"))
&& (tokens[k+29].equals("28")) && (tokens[k+35].equals("27"))) {
System.out.println(tokens[k]);
}This one below compiles but doesn't print to the screen.
import java.io.*;
import java.util.*;
class tokenstest {
public static void main(String args[]) throws IOException {
int i; //int to read in the data from the text file
int count = -1;
int countt = -1;
int countc = 0; //int to put data into a char array
FileInputStream fin; //input stream
char array[] = new char[1000000]; //array to hold chars from the text file
String s; //chars are transfered to this String
int index; //index of the names I'm searching for in the string
String tokens[] = new String[200000];
String sortdg[] = new String[500];
String sortstem[] = new String[500];
try {
fin = new FileInputStream(args[0]);
} catch (FileNotFoundException e) {
System.out.println("File not Found");
return;
} catch (ArrayIndexOutOfBoundsException e) {
System.out.println("Usage: ShowFile File");
return;
do {
i = fin.read();
if (i != -1) {
if (count==array.length-1) { //this expands the array if more space is needed
char temp[] = new char[array.length+5000];
for (int j = 0; j < array.length; j++) temp[j] = array[j];
array = temp;
array[++count] = (char) i;
else
array[++count] = (char) i;
} while(i != -1);
fin.close();
s = new String(array);
StringTokenizer st = new StringTokenizer(s);
while (st.hasMoreTokens()) {
if (countt==tokens.length-1) { //this expands the array if more space is needed
String temp1[] = new String[tokens.length+5000];
for (int j = 0; j < tokens.length; j++) temp1[j] = tokens[j];
tokens = temp1;
tokens[++countt] = st.nextToken();
else
tokens[++countt] = st.nextToken();
if (tokens[4].startsWith("stem")) {
if (tokens[4].equals(tokens[201])) { //Skip this one
else
if ((tokens[9].equals("32")) && (tokens[15].equals("31"))
&& (tokens[21].equals("30")) && (tokens[27].equals("29"))
&& (tokens[33].equals("28")) && (tokens[39].equals("27"))) {
sortstem[countc] = tokens[4];
sortdg[countc] = tokens[3];
countc++;
for (int k = 201; k < tokens.length-198; k++) {
if (tokens[k].startsWith("stem")) {
if ((tokens[k].equals(tokens[k+197])) || (tokens[k].equals(tokens[k-197]))) {
//Do nothing
else
if ((tokens[k+5].equals("32")) && (tokens[k+11].equals("31"))
&& (tokens[k+17].equals("30")) && (tokens[k+23].equals("29"))
&& (tokens[k+29].equals("28")) && (tokens[k+35].equals("27"))) {
sortstem[countc] = tokens[k];
sortdg[countc] = tokens[k-1];
countc++;
for (int z = 0; z < countc; z++) {
System.out.println(sortstem[z]);
for (int z = 0; z < countc; z++) {
for (int y = z+1; y < countc; y++) {
if (sortdg[z].compareTo(sortdg[z]) > 0) {
String tdg = sortdg[z];
String tstem = sortstem[z];
sortdg[z] = sortdg[y];
sortstem[z] = sortstem[y];
sortdg[y] = tdg;
sortstem[y] = tstem;
for (int j = 0; j < 20; j++) {
System.out.println(sortstem[j] + ": dG = " + sortdg[j]);
System.out.println("Test");
}I'm still having trouble with the println in this program. For some reason, in this section of the code, if I put System.out.println(sortstem[0]); inside the for loop, it works fine. But if I try to do it ouside of this loop, it will not work. The only thing I can think of is that the variable is only available inside the loop but I just can't figure it out. Can anyone enlighten me?
for (int k = 201; k < tokens.length-198; k++) {
if (tokens[k].startsWith("stem")) {
if ((tokens[k].equals(tokens[k+197])) || (tokens[k].equals(tokens[k-197]))) {
//Do nothing
else
if ((tokens[k+5].equals("32")) && (tokens[k+11].equals("31"))
&& (tokens[k+17].equals("30")) && (tokens[k+23].equals("29"))
&& (tokens[k+29].equals("28")) && (tokens[k+35].equals("27"))) {
sortstem[countc] = tokens[k];
sortdg[countc] = tokens[k-1];
countc++;
[code/] -
App errors for some kind of PDF-documents
Hello,
we are getting java.lang.NullPointerExceptions for some PDF-documents
to be Rights Management protected by using com.adobe.livecycle.rightsmanagement.RightsManagementService.applyPolicy()
Client-side gets this exception:
System.Web.Services.Protocols.SoapException: com.adobe.edc.sdk.SDKException: Error during the closing
of document listeners. -- Internal server error(error code bin: 1032, hex: 0x408)
Part of the server-side stack trace is:
2009-07-29 15:09:09,728 ERROR [com.adobe.idp.Document] DOCS001: Unexpected exception. Custom DocumentWriterEx.onDisconnect() throws: java.lang.NullPointerException.
java.lang.NullPointerException
at com.adobe.internal.pdftoolkit.pdf.document.PDFCosFactory.getUserData(PDFCosFactory.java:6 5)
at com.adobe.internal.pdftoolkit.pdf.document.PDFCosFactory.getInstance(PDFCosFactory.java:2 18)
at com.adobe.internal.pdftoolkit.pdf.document.PDFDocumentInfo.getInstance(PDFDocumentInfo.ja va:68)
at com.adobe.internal.pdftoolkit.pdf.document.PDFDocument.getDocumentInfo(PDFDocument.java:4 63)
at com.adobe.internal.pdftoolkit.services.xmp.DocumentMetadataImpl.commit(DocumentMetadataIm pl.java:1039)
at com.adobe.internal.pdftoolkit.services.xmp.DocumentMetadataImpl.message(DocumentMetadataI mpl.java:233)
at com.adobe.internal.pdftoolkit.pdf.document.listener.DocumentListenerRegistryBase.sendMess age(DocumentListenerRegistryBase.java:220)
at com.adobe.internal.pdftoolkit.pdf.document.listener.GroupDocumentListener.message(GroupDo cumentListener.java:120)
at com.adobe.internal.pdftoolkit.pdf.document.listener.DocumentListenerRegistryBase.sendMess age(DocumentListenerRegistryBase.java:220)
at com.adobe.internal.pdftoolkit.pdf.document.PDFDocument.finish(PDFDocument.java:342)
at com.adobe.pdfdocumentmanager.SharedPdfDocumentInternal$PDFCheckinImpl.checkinPDF(SharedPd fDocumentInternal.java:493)
at com.adobe.pdfdocumentmanager.PDFDocumentVsDocumentCore$Data.getDoc(PDFDocumentVsDocumentC ore.java:333)
at com.adobe.pdfdocumentmanager.SharedPdfDocumentInternal$Writer.write(SharedPdfDocumentInte rnal.java:673)
at com.adobe.pdfdocumentmanager.SharedPdfDocumentInternal$Writer.onDisconnect(SharedPdfDocum entInternal.java:871)
at com.adobe.pdfdocumentmanager.PDFDocumentVsDocumentCore$WriterProxy.onDisconnect(PDFDocume ntVsDocumentCore.java:249)
at com.adobe.idp.DocumentCacheID.unregister(DocumentCacheID.java:73)
at com.adobe.idp.Document.dispose(Document.java:2217)
at com.adobe.pdfdocumentmanager.client.SharedPdfDocumentContext.releasePDFDocument(SharedPdf DocumentContext.java:233)
at com.adobe.pdfdocumentmanager.client.SharedPdfDocumentContext.clear(SharedPdfDocumentConte xt.java:297)
at com.adobe.pdfdocumentmanager.client.SharedPdfDocumentContext.exitScope(SharedPdfDocumentC ontext.java:222)
at com.adobe.pdfdocumentmanager.client.SharedPdfDocumentContext.endScope(SharedPdfDocumentCo ntext.java:161)
at com.adobe.livecycle.rightsmanagement.RightsManagementService.applyPolicy(RightsManagement Service.java:207)
at com.adobe.livecycle.rightsmanagement.RightsManagementService.applyPolicy(RightsManagement Service.java:463)
What might be the reason for those documents to get errors during
Thanks for any hints!
DilettantoThank you Steve,
enclosed are my answers:
1) What versions are you using (Rights Management ES, Acrobat etc...)
--> RightsManagement Server 8.2
2) Does this occur an ALL pdfs? If not please postone that causes the error.
--> No - this occurs only to some PDF-documents that come from external sources and that have been PDF-stamped by some
external tool.
Other documents can be RightsManagement-protected just fine
But how to tell, what part of those documents is the reason for the null-pointer-exception?
3) Can you successfully apply a policy manually using Acrobat Pro?
will try this right now
4) Are you only trying to apply a policy or is it part of a larger process?
Regarding LiveCycle Server, ApplyPolicy is the only action to be done
We are using code based on the ApplyPolicy Sample
Maybe you are looking for
-
Hi I have the Tour 9630 what OS system should I be running? Also, has the new OS fixed the ringtone problems? Also, should I install QuickPull and run it daily? Also, there is a delay from my inbox on my computer to getting emails on my phone...is
-
All, I have 10-12 users for file sharing on an open directory PowerMac G4 and jsp websites on an Xserve G5. I want to use RAID for storing the home directories as well as other shared folders and quickime movies that need to be accessed by the Xserve
-
Issue Unlocking Gamer's Club Card
I purchased a game online and the gamer's club at the same time back in June. They sent me the gamer's club and was told I needed to unlock it at a physical store. I went to my local BB and they could not figure out how to unlock it without charging
-
I'm running a fresh installation of Arch 64 + Gnome. Something is failing at boot. I'm not 100% sure what it is (flashes up the screen too fast), but I think it's dbus. Alsa loads after it, and dbus is right before alsa in my rc.conf. First of all,
-
External MIDI recorded as Audio is early
Why is it when I record MIDI data sent from Logic 8.02 to an external synth module and recorded back to Logic as audio is the audio earlier in time than the MIDI? I played with various delay comp settings and this didn't seem to help. Many thanks! Al