Strange stack behaviour with referenced files

I have just started to notice peculiar behaviour with referenced images within stacks. I have been reviewing last years pictures with a view to clearing out the junk.What I have found is rather alarming in that on clicking a stack to open it all the images within the stack were the wrong pictures, wrong as in taken with a different camera in a different year.The top picture does not seem to be affected.On attempting to find the correct files using 'manage referenced files' all the wrong images are shown as found in the list view with their own file names at the same time the thumbnails (top right hand pane) show the original correct file names but with the wrong thumbnails,Aperture does not realise that it is referencing the wrong files and so will not let me reconnect to the correct files.
Anyone with a similar problem or a cure for this behaviour?

Ok I have deleted and rebuilt thumbnails files to no avail.
What appears to be happening is that aperture is using the wrong file-path for the affected pictures.
I keep all pictures arranged by date order so for example where the correct file path for an image would be;
Raid Zero/Pictures/2006/0609/060928/pict3722
Aperture is giving a file path of
Picture Library/2007/0712/071223/_DCS1023
in the manage referenced files pane it shows the wrong path as above, the thumbnail picture is of the wrong file but the thumbnail name and date is correct.
Interestingly since rebuilding the thumbs it is now possible to reconnect to the correct original file whereas before the reconnect option was not available, however it is only possible to do this one file at a time,the re-connect all function does not work presumably because Aperture is not aware that its filepath is wrong.
Oh dear.... Aperture has just crashed,this immediately after reconnecting 6 files and waiting for the files to update to the correct image in viewer mode.
GRRRRRRRRR!

Similar Messages

Strange DW Behaviour with local file includes

Can anyone please help?!?
I've been using DW for many years, and we've just moved over
local files to a new server. Unfortunately, during this copy, some
of the files have started behaving very strangely...the virtual
includes are no longer showing in the WSIWIG display. There's
nothing wrong with the files - if I upload them to the web server,
they work.
Here's the example:
1) I set up a new web site in DW. I don't specify a remote
site at this stage.
2) I copy in 2 of the "problem files" into the local
directory, page1.asp and includefile.asp
3) Page1.asp looks like this:
<%@LANGUAGE="VBSCRIPT" CODEPAGE="1252"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />
<title>Untitled Document</title>
</head>
<body>
</body>
</html>
This page does not display the includefile in the design view
as it should.
If I go to "new web page" and copy and paste the exact code
into the new page, it works fine and displays the include file.
Both files are in the same directory.
If I strip both newpage.asp and page1.asp down to just
"", one works and
one doesn't!!
This led me to believe it was some sort of permissions
problem from transferring the files and folders around, but if you
look at newpage.asp and page1.asp, they have exactly the same
permissions.
It's driving me mad - we have a load of web sites behaving
like this, so I can't just create a new page for every page and
copy in the code!
Is there some strange hidden permissions I'm not aware of?
Thanks!!!

You can report this to Apple here:
http://www.apple.com/feedback/macosx.html

Strange repaint behaviour with JList & Keyboard actions

Hi everyone,
This is my first post to the forum. You guys have been a great help in the past and I hope to contribute more in the future.
Anyways, I've encountered some strange repainting behaviour with a JDialog that uses a JList and a JButton. The dialog is fairly straight-forward and basically this is how it works (like an open file dialog - yes I'm implementing my own filechooser of sorts):
* JList lists a number of simple items that the user can select from.
* Once a selection is made, an Open button (JButton) is enabled.
* <ENTER> key is registered (using registerKeyboardAction()) with a JPanel which is used as the main content pane in the dialog.
* The user can either click on the Open Button or hit the <ENTER> key which then closes the dialog and runs whatever logic that needs to.
Now, the repaint problem comes in when:
1. User selects an item.
2. User hits the <ENTER> button
3. Dialog closes
4. User brings the dialog back up. This entails reloading the list by removing all elements from the list and adding new ones back in.
5. Now... if the user uses the mouse to select an item lower in the list than what was done in step #1, the selection is made, but the JList doesn't repaint to show that the new selection was made.
I didn't include a code sample because the dialog setup is totally straight-forward and I'm not doing anything trick (I've been doing this kind of thing for years now).
If I remove the key registration for the <ENTER> key from the dialog, this problem NEVER happens. Has anyone seen anything like this? It's a minor problem since my workaround is to use a ListSelectionListener which manually calls repaint() on the JList inside the valueChanged() method.
Just curious,
Huy

Oh, my bad. I'm actually using a JToggleButton and not a JButton, so the getRootPane().setDefaultButton() doesn't apply because it only takes JButton as an input param. I wonder why it wasn't implemented to take AbstractButton. hmmm.

In Aperture 3.4.1, I am not able to connect with referenced files on a network

I am running OS X 10.8.2 and Aperture 3.4.1, and am unable to connect with referenced files on a network. Specifically, the referenced files reside on my iMac and I am attempting to connect to them from my MBP. They appear in red in the dialogue box. While I know this has been a long standing issue in other versions, I was hoping it had been solved by now. Any assistance will be appreciated.
Thanks -
Dudley

http://support.apple.com/kb/HT5922
If you want to mirror your desktop, see:
http://support.apple.com/kb/HT5404
Regards.

Help with referenced files and importing

This might be more complex than can be addressed here, but I'm struggling with the organization of aperture.
Because I'm not sure I want use aperture forever, and because I occasionally like to use other photo editors, I've opted for a referenced file setup. I typically arrange my pictures into year/month sub folders, with additional folders for special subjects, like my kids. I've been doing this for a long time, it works for me, and I don't want to change.
Problem #1 - avoiding duplicates when I import. When I stick the card in my computer I want to copy just the new files to the directory I specify. Image capture only looks for duplicates in the target directory, which is no help if I'm importing files to "November" from a card that has files that were previously imported to "October." The easiest solution would be to delete the images off of the card after importing, but I can't do that - my wife also wants to copy the pix to her computer and she may not copy for several weeks or months at a time.
I tried using aperture's import feature to copy files directly from my camera's memory card. The import worked, but when I tried to locate the files on disk, aperture told me there were no referenced files. Any idea where they are?
Problem #2 - import. Is there any way to make Aperture watch referenced directories and automatically add new files to the the appropriate project? It's a pain to keep manually importing files.
Problem #3 - Organization. Is there any way to set up aperture so that a project = a physical folder on my drive? I get that Aperture is trying to abstract the physical location of my files, but I don't want them abstracted. Also, why is my aperture primary library 6.2 GB when I do all my work with referenced files? Where are my edited files stored? Are these in the primary library? Where are the files from my photostreams (from my phone) stored?
Would any or all of these issues be resolved by moving to a managed file set up?
Finally, if I can't get Aperture working the way I need it, any insight into how I'd use it as an external editor to something like Picasa? I really like the aperture editing tools - that's why I bought it. But the workflow is just killing me.
Any insights would be appreciated. Thanks.

It is not as complex as you are making it. Aperture is not per se an editor. It is for storing and organizing, and quickly decoding RAW images. It is a pretty good editor, but it has the feature to allow you to specify an External Editor to which you can send images for more complex editing, and back -- all from within Aperture.
You don't want to have your images referenced so you can also edit them with other programs. That destroys the non destructive design of Aperture. If you want Referenced images, you mostly want them so they can be on a different hard drive from that used by the Library for keeping track and storing the adjustments, and not so other programs can access them.
You need to read further as to how and why Aperture works the way it does.
Ernie

View Master mode strange behaviour with jpg files

Hy all,
I'm using Aperture, and I'm tweakin a lot the SW to discover all secrets ....
I'm really concerned about a strange behaviour of the SW in view mode.
If I open a jpg file, do not apply ANY modification, and apply the "show master" command (pressing M), there's a subtle behaviour :
*the images get sharper !!!!*
It behaves as if an "edge sharpening" was applied !!!!!!
With _RAW files this thing doesn't happen at all._
Even stranger, if I zoom to full definition (by pressing Z), and toggle between normal view and "show master" view, the immage remains the same !
The effect is not so evident with all images, but sometimes it is !!
Anyway, I expect not to have such kind of things with a professional SW.
With professional cameras and good quality files it's really annoying not to beeing sure what's the REAL content of the jpg image.
Has anyone noted this thing ? Is there a reasonable explanation ?
The only one I tried to figure out is the following : may be Aperture applies some kind of resampling algorithm with jpg files (bicubic, bilinear, etc).
May be this resampling is not applied with 100% magnification, as weel as with raw files.
But it's only my guessing. Now, I'm tweaking other viewers and other SW to understand what's the real jpg image stored in the file : the blurer one form normal view or the sharper one with "show master" mode.
I stress once again : of course, the jpg file I'm talking about have no settings at all, just imported and toggled with M button.
Thanks in advance.
Regards,
Enzo

Hy,
I'm afraid I'm not been clear.
The problem is this :
1) jpg image opened in normal view mode, no zoom, (no quick preview, of course) : image with a certain amount of blour
2) jpg image opened in show master mode, no zoom, (no quick previre, of course) : image SHARPER with respect with the previous.
No edit applied from import, so "show master" command shouln't apply any change in rendering, should it ?
The only thing I said on 100% view is that such difference (between normal mode e show mastermode) is not present with 100% magnification.
That was the issue.
Enzo

Strange layout behaviour with TilePane

here is the demo
1.rootLayout have 2 child,controlbox and contentLayout
2.3 button on controlbox
3.contentLayout will add content,when press deffrent button on controlbox
4.watch button "Add TilePane" , strange layout behaviour , what is the matter?
layout picture
|--------------------------------|
|           |                    |
|           |                    |
|           |                    |
|           |                    |
|controlbox | contentLayout     |
| (VBox)    |   (StackPane)      |
|           |                    |
|           |                    |
|           |                    |
|           |                    |
|--------------------------------|
                                        the code
import javafx.application.Application;
import javafx.event.EventHandler;
import javafx.geometry.Pos;
import javafx.scene.Group;
import javafx.scene.Scene;
import javafx.scene.control.Button;
import javafx.scene.control.Label;
import javafx.scene.control.ListView;
import javafx.scene.input.MouseEvent;
import javafx.scene.layout.StackPane;
import javafx.scene.layout.TilePane;
import javafx.scene.layout.VBox;
import javafx.stage.Stage;
public class testTilePaneLayout extends Application {
     StackPane contentLayout = new StackPane();
     //add content with 2 Button
     public void addContent(){
          VBox vbox = new VBox();
          contentLayout.getChildren().clear();
          contentLayout.getChildren().add(vbox);
          StackPane.setAlignment(vbox,Pos.CENTER);
          Button btn = new Button("Button1");
          Button btn2= new Button("Button2");
          vbox.getChildren().add(btn);
          vbox.getChildren().add(btn2);
     //add content with 2 Button & 1 ListView
     public void addListViewContent(){
          VBox vbox = new VBox();
          contentLayout.getChildren().clear();
          contentLayout.getChildren().add(vbox);
          StackPane.setAlignment(vbox,Pos.CENTER);
          Button btn = new Button("Button1");
          Button btn2= new Button("Button2");
          vbox.getChildren().add(btn);
          vbox.getChildren().add(btn2);
          @SuppressWarnings("rawtypes")
          ListView listView = new ListView();
          vbox.getChildren().add(listView);
     //add content with 2 Button & 1 TilePane
     public void addTilePaneContent(){
          VBox vbox = new VBox();
          contentLayout.getChildren().clear();
          contentLayout.getChildren().add(vbox);
          StackPane.setAlignment(vbox,Pos.CENTER);
          Button btn = new Button("Button1");
          Button btn2= new Button("Button2");
          vbox.getChildren().add(btn);
          vbox.getChildren().add(btn2);
          TilePane tilePane = new TilePane();
          tilePane.setMaxSize(100,100);
          Label lbl = new Label("Label on TilePane");
          tilePane.getChildren().add(lbl);
          vbox.getChildren().add(tilePane);
     public void start(Stage stage) {
          stage.setResizable(false);
          stage.centerOnScreen();
          Group root = new Group();
          Scene scene = new Scene(root,800,600);
          stage.setScene(scene);
          //root Layout = StackPane
          StackPane rootLayout = new StackPane();
          root.getChildren().add(rootLayout);
          rootLayout.setMinSize(800,600);
          rootLayout.setMaxSize(800,600);
          //content StackPane
          rootLayout.getChildren().add(contentLayout);
          contentLayout.setMinSize(100, 100);
          contentLayout.setMaxSize(200, 200);
          StackPane.setAlignment(contentLayout,Pos.CENTER);
          //control VBox
          VBox controlBox = new VBox();
          rootLayout.getChildren().add(controlBox);
          controlBox.setMaxSize(100, 200);
          StackPane.setAlignment(controlBox,Pos.CENTER_LEFT);
          //3 control button
          Button btn1 = new Button("Add button");
          Button btn2= new Button("Add Listview");
          Button btn3= new Button("Add TilePane");
          controlBox.getChildren().add(btn1);
          controlBox.getChildren().add(btn2);
          controlBox.getChildren().add(btn3);
          btn1.setOnMousePressed(new EventHandler<MouseEvent>() {
               @Override
               public void handle(MouseEvent arg0) {
                    addContent();
          btn2.setOnMousePressed(new EventHandler<MouseEvent>() {
               @Override
               public void handle(MouseEvent arg0) {
                    addListViewContent();
          btn3.setOnMousePressed(new EventHandler<MouseEvent>() {
               @Override
               public void handle(MouseEvent arg0) {
                    addTilePaneContent();
          stage.show();
     public static void main(String[] args) {
          Application.launch(args);
}Edited by: noregister on Oct 4, 2011 11:30 AM
Edited by: noregister on Oct 4, 2011 11:31 AM

Oh, my bad. I'm actually using a JToggleButton and not a JButton, so the getRootPane().setDefaultButton() doesn't apply because it only takes JButton as an input param. I wonder why it wasn't implemented to take AbstractButton. hmmm.

File opened in external editor not stored with referenced files

If I open a referenced raw file in an external editor (CS2) and work on the image adding layers etc., the image is not stored where I have all the other referenced files. It gets stored in the Aperture Library. Is there a way around this. I want to keep all my files together. This can be done in Lightroom, but I am trying to make Aperture work for my workflow.
Thanks,
gary
mac book, G5 Mac OS X (10.4.7)

Well, here's the feedback I submitted to Apple:
With the introduction of Aperture 1.5, you offered users the ability to manage their own libraries, and for Aperture to work with 'referenced' images. In fact, because of this very reason, many of us consumers decided to buy Aperture 1.5.
Most of us photographers also use Adobe Photoshop routinely.
But there is a huge problem/bug for us users who manage our own library (force Aperture to work with 'referenced' images) AND use Photoshop (or any external editor for that matter). When we open a file in an external editor via Aperture, Aperture creates a new 'master' for editing -- but does so in its own 'managed' library! When we save from Photoshop, the image remains in the 'managed' library! So now we have one 'master' in our own directory, and the externally-edited 'master' in Aperture's 'managed' library! This is very CONFUSING and renders external editing via Aperture USELESS... no one in their right mind would want one version of their image in an organized directory, and an edited version in Aperture's managed library (where it is difficult to find manually)! No, it makes much more sense to create the edited 'master' in the same location as the original 'master'!
PLEASE fix this bug ASAP! Aperture already has a good method for automatically renaming files by adding (1) or (2) or (3) or so forth when it is relocating files and finds a file with the same file-name. The same logic can be applied when creating a new 'master' for external-editing: that is, it should just create another .tiff (or .psd, or what have you) file with the same name but with a (1) or (2) tagged on. For example, if my master image is \Pictures\Seattle\SpaceNeedle.tiff, then when I open this image in an external editor, Aperture should automatically make the file: \Pictures\Seattle\SpaceNeedle (1).tiff, and open that file in the external editor... rather than create SpaceNeedle.tiff in its own managed library where I can't even find it using Finder or Windows Explorer, etc.
Many of us have this complaint (just search Apple discussions)... PLEASE rectify this problem ASAP as it is completely messing up our workflows by requiring us to manually save through the external editor and then having to manually remove every 'managed' file that Aperture makes. This is really a pain and seriously makes me want to switch to a different image management program... though I love Aperture thus far and would love to stick to it as I believe it is visionary and shaping the future of how photographers will manage their digital workflows!
Many thanks in advance for your time!
Best,
Rishi

Working with referenced files

http://homepage.mac.com/bagelturf/files/4b81e05732a308e2f72cdae27ec816c7-705.htm l
The website linked above which I think is wonderful describes the difficulties of exporting referenced files. The third last paragraph mentions, "To export all of my hundreds of five-star images in one go I must mount all of the DVDs that contain those images at the same time! So if I have five DVDs that contain the images, I need five DVD players all plugged into my computer at the same time. The same is true of Firewire disks. Unless I can mount all of them at once, I cannot export a selection of images that spans them."
My question has to do with the latter part of this quote dealing with Firewire disks. Would daisy-chaining a number of Firewire disks solve this problem, or are there drawbacks to doing this? Daisy-chaining the disks would ensure that they are all always connected therefore the images will always be online. Is this a viable option, or will I encounter problems down the road? I just want to find a way to keep all my photo's "online" even though they are in different drives (too many photos for one hard drive therefore I can't have Aperture manage them all in one location like I would like to do). Ah, if only Aperture allowed for disk spanning...maybe some day I guess, but for now, will my workaround described above work?
Mac OS X (10.4.8)

These days, with hard drives extremly cheap (price per gigabyte), I don't see why someone would have masters on DVDs, apart from backups.
As the previous post says, having a firewire chain of multiple HDs solves that problem.

Strange account behaviour with active sync

Hi all,
i determined a strange behaviour with Active Sync:
I deleted an Account in IDM but in the active sync log i can always see the account information??
Thnx Michael

Although, now that you are doing this
My workaround is to use an additional offscreen buffered image, do all of my rendering to that, and then at the end copy that image in one go to the drawGraphics from the buffer strategy.you no longer need to use BufferStrategy.Yes, good point. That didn't occur to me.
The way my implementation is I have a pluggable rendering strategy (i.e. the strategy pattern) where I can choose an implementation that will use the frame's bufferStrategy and drawGraphics, or my own BufferedImage back buffer. In light of what you've said I can easily change my implementation to not use the buffer strategy at all and I should save some rendering time.
I've found all sorts of weird behaviour when I use active rendering and have the OpenGL pipeline enabled (I need the pipeline enabled because I want accelerated images), e.g. even setting rendering hints can sometimes cause drawString to not output any text after the first frame.
I was really using BufferStrategy because I wanted to use hardware page flipping and sync my screen updates to the vertical blanking interval which, as it happens, I can't actually get to work - but that's a problem for another day/topic.
Anyway, I appreciate your follow-up, thanks.

Externally edited image not stored with referenced files?

When I open an image in the external editor, do my work in PS, and then save, the new file is located in the Aperture Library even though the master for the image is a referenced file. Is there any way to change this so the new images will be placed in the same folder as the referenced images? Thanks...gary
mac book, G5 dual Mac OS X (10.4.8)

I'm afraid for the moment you have to do it manually by selecting the image and going to File/Relocate Master.
We should have and option in Aperture to allow us to have ALL the images in an external location.

Strange Behaviour with JPEG files on Premiere Cs5 Timeline

Whew! Have not seen this problem before. Have been using Premiere since Ver 3.
I am in a project where I am dropping Jpeg images on the time line and creating a slideshow.
I am doing lots of motion with keyframes on scale., position etc .
When I render the project some images disappear and another image appears several times in their place.
Here is the link to the uncompleted video :
http://youtu.be/GA6iSXkFhK0
Notice the image of the bride and groom at front of the car keeps repeating itself, whereas other images were placed in the timeline.
Help would be appreciated. I have redone the project 4 times.

BTW, this issue should be fixed in Premiere Pro CS5.5. Users of Premiere Pro CS5 will need to use the workaround that Colin mentioned.

Strange tty behaviour with xorg 1.8

So, my girlfiend has an ooooold machine, I've decided to
install arch on it -
and I'm stuck with a strange thing there - when I start Xorg ( with startx, which works fine ),
I cannot switch back to tty1-6 (e.g. I think, I can, but it shows nothing )
There are no hints in /var/log/Xorg.log nor in dmesg or in /var/log/kernel.log
What is happening there???
( Girlfriend is not really a terminal user, thanx for the advice )
Last edited by scar (2010-06-22 17:25:15)

Edit 12:53 See my next post - yyou need either the nouveau or the nv driver installed and configured in xorg.conf
The 'nouveau' in the kernel is not the X driver. You need to install that explicitly (xf86-video-nouveau). If you are running without an xorg.conf file you must create one with the following:
Section "Device"
Identifier "n"
Driver "nouveau"
EndSection
Otherwise you must edit the 'Device' section in your xorg.conf to specify the nouveau driver.
In your dmesg you should see some lines at the end (after all the hdd stuff) like so:
nouveau 0000:01:00.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
[drm] nouveau 0000:01:00.0: Detected an NV10 generation card (0x011000b2)
[drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PROM
[drm] nouveau 0000:01:00.0: ... appears to be valid
[drm] nouveau 0000:01:00.0: BMP BIOS found
[drm] nouveau 0000:01:00.0: BMP version 5.20
[drm] nouveau 0000:01:00.0: Bios version 03.11.01.24
[drm] nouveau 0000:01:00.0: Found Display Configuration Block version 1.5
[drm] nouveau 0000:01:00.0: Raw DCB entry 0: f0003f00 000088b8
[drm] nouveau 0000:01:00.0: Raw DCB entry 1: f2204301 ffffffff
[drm] nouveau 0000:01:00.0: Raw DCB entry 2: f2244301 ffffffff
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0xAAD2
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0xB1AE
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0xAAED
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0xB155
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0xAB80
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 5 at offset 0xACC2
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 6 at offset 0xABA5
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 7 at offset 0xAC5D
[drm] nouveau 0000:01:00.0: Detected 64MiB VRAM
This is for a PCI MX400 - I haven't installed Arch on my really old machine with an AGP card yet.
And in your Xorg.0.log file (with the vouveau driver specified as above) you should see something like:
[ 15.149] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 15.162] (II) Module nouveau: vendor="X.Org Foundation"
[ 15.162] compiled for 1.8.0.902, module version = 0.0.16
[ 15.162] Module class: X.Org Video Driver
[ 15.162] ABI class: X.Org Video Driver, version 7.0
[ 15.162] (II) NOUVEAU driver
[ 15.162] (II) NOUVEAU driver for NVIDIA chipset families :
[ 15.162] RIVA TNT (NV04)
[ 15.162] RIVA TNT2 (NV05)
[ 15.162] GeForce 256 (NV10)
[ 15.162] GeForce 2 (NV11, NV15)
[ 15.162] GeForce 4MX (NV17, NV18)
[ 15.162] GeForce 3 (NV20)
[ 15.162] GeForce 4Ti (NV25, NV28)
[ 15.162] GeForce FX (NV3x)
[ 15.162] GeForce 6 (NV4x)
[ 15.162] GeForce 7 (G7x)
[ 15.162] GeForce 8 (G8x)
[ 15.162] (++) using VT number 7
[ 15.165] (II) Primary Device is: PCI 01@00:00:0
[ 15.165] drmOpenDevice: node name is /dev/dri/card0
[ 15.165] drmOpenDevice: open result is 7, (OK)
[ 15.165] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 15.165] drmOpenDevice: node name is /dev/dri/card0
[ 15.165] drmOpenDevice: open result is 7, (OK)
[ 15.165] drmOpenByBusid: drmOpenMinor returns 7
[ 15.165] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 15.165] (II) [drm] nouveau interface version: 0.0.16
[ 15.165] (II) Loading sub module "dri"
[ 15.166] (II) LoadModule: "dri"
[ 15.166] (II) Reloading /usr/lib/xorg/modules/extensions/libdri.so
[ 15.166] (II) NOUVEAU(0): Loaded DRI module
[ 15.166] drmOpenDevice: node name is /dev/dri/card0
[ 15.166] drmOpenDevice: open result is 8, (OK)
[ 15.166] drmOpenDevice: node name is /dev/dri/card0
[ 15.166] drmOpenDevice: open result is 8, (OK)
[ 15.166] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 15.166] drmOpenDevice: node name is /dev/dri/card0
[ 15.166] drmOpenDevice: open result is 8, (OK)
[ 15.166] drmOpenByBusid: drmOpenMinor returns 8
[ 15.166] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 15.166] (II) [drm] DRM interface version 1.3
[ 15.166] (II) [drm] DRM open master succeeded.
[ 15.166] (--) NOUVEAU(0): Chipset: "NVIDIA NV11"
[ 15.166] (**) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 15.166] (==) NOUVEAU(0): RGB weight 888
[ 15.167] (==) NOUVEAU(0): Default visual is TrueColor
[ 15.167] (==) NOUVEAU(0): Using HW cursor
[ 15.272] (II) NOUVEAU(0): Output VGA-1 using monitor section Monitor0
[ 15.379] (II) NOUVEAU(0): EDID for output VGA-1
[ 15.379] (II) NOUVEAU(0): Manufacturer: GSM Model: 436f Serial#: 45946
[ 15.379] (II) NOUVEAU(0): Year: 2005 Week: 1
[ 15.379] (II) NOUVEAU(0): EDID Version: 1.3
[ 15.379] (II) NOUVEAU(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 15.379] (II) NOUVEAU(0): Sync: Separate Composite SyncOnGreen
[ 15.379] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34 vert.: 27
[ 15.379] (II) NOUVEAU(0): Gamma: 2.20
[ 15.379] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 15.379] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 15.379] (II) NOUVEAU(0): redX: 0.641 redY: 0.342 greenX: 0.292 greenY: 0.611
[ 15.379] (II) NOUVEAU(0): blueX: 0.147 blueY: 0.068 whiteX: 0.313 whiteY: 0.329
[ 15.380] (II) NOUVEAU(0): Supported established timings:
[ 15.380] (II) NOUVEAU(0): 720x400@70Hz
[ 15.380] (II) NOUVEAU(0): 640x480@60Hz
[ 15.380] (II) NOUVEAU(0): 640x480@75Hz
[ 15.380] (II) NOUVEAU(0): 800x600@60Hz
[ 15.380] (II) NOUVEAU(0): 800x600@75Hz
[ 15.380] (II) NOUVEAU(0): 832x624@75Hz
[ 15.380] (II) NOUVEAU(0): 1024x768@60Hz
[ 15.380] (II) NOUVEAU(0): 1024x768@75Hz
[ 15.380] (II) NOUVEAU(0): 1280x1024@75Hz
[ 15.380] (II) NOUVEAU(0): 1152x864@75Hz
[ 15.380] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 15.380] (II) NOUVEAU(0): Supported standard timings:
[ 15.380] (II) NOUVEAU(0): #0: hsize: 640 vsize 480 refresh: 75 vid: 20273
[ 15.380] (II) NOUVEAU(0): #1: hsize: 800 vsize 600 refresh: 75 vid: 20293
[ 15.380] (II) NOUVEAU(0): #2: hsize: 1024 vsize 768 refresh: 75 vid: 20321
[ 15.380] (II) NOUVEAU(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 15.380] (II) NOUVEAU(0): Supported detailed timing:
[ 15.380] (II) NOUVEAU(0): clock: 108.0 MHz Image Size: 338 x 270 mm
[ 15.380] (II) NOUVEAU(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
[ 15.380] (II) NOUVEAU(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
[ 15.380] (II) NOUVEAU(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 140 MHz
[ 15.380] (II) NOUVEAU(0): Monitor name: L1715S
[ 15.380] (II) NOUVEAU(0): Monitor name:
[ 15.380] (II) NOUVEAU(0): EDID (in hex):
[ 15.380] (II) NOUVEAU(0): 00ffffffffffff001e6d6f437ab30000
[ 15.380] (II) NOUVEAU(0): 010f01036e221b78ea2ee5a4574a9c25
[ 15.380] (II) NOUVEAU(0): 115054a56b80314f454f614f81800101
[ 15.380] (II) NOUVEAU(0): 010101010101302a009851002a403070
[ 15.380] (II) NOUVEAU(0): 1300520e1100001e000000fd00384b1e
[ 15.380] (II) NOUVEAU(0): 530e000a202020202020000000fc004c
[ 15.380] (II) NOUVEAU(0): 31373135530a202020202020000000fc
[ 15.380] (II) NOUVEAU(0): 000a20202020202020202020202000df
[ 15.380] (II) NOUVEAU(0): EDID vendor "GSM", prod id 17263
[ 15.381] (II) NOUVEAU(0): Using hsync ranges from config file
[ 15.381] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 15.381] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 15.381] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 15.381] (II) NOUVEAU(0): Printing probed modes for output VGA-1
[ 15.381] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 15.381] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 15.382] (II) NOUVEAU(0): Output VGA-1 connected
[ 15.382] (II) NOUVEAU(0): Using user preference for initial modes
[ 15.382] (II) NOUVEAU(0): Output VGA-1 using initial mode 1280x1024
[ 15.382] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 15.382] (--) NOUVEAU(0): Virtual size is 1280x1024 (pitch 1280)
[ 15.382] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.0 kHz, 75.0 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 15.382] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
[ 15.382] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 15.383] (**) NOUVEAU(0): Display dimensions: (340, 270) mm
[ 15.383] (**) NOUVEAU(0): DPI set to (95, 96)
[ 15.383] (II) Loading sub module "fb"
[ 15.383] (II) LoadModule: "fb"
[ 15.383] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 15.397] (II) Module fb: vendor="X.Org Foundation"
[ 15.397] compiled for 1.8.1.902, module version = 1.0.0
[ 15.397] ABI class: X.Org ANSI C Emulation, version 0.4
[ 15.397] (II) Loading sub module "exa"
[ 15.397] (II) LoadModule: "exa"
[ 15.398] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 15.399] (II) Module exa: vendor="X.Org Foundation"
[ 15.399] compiled for 1.8.1.902, module version = 2.5.0
[ 15.399] ABI class: X.Org Video Driver, version 7.0
[ 15.399] (II) Loading sub module "shadowfb"
[ 15.399] (II) LoadModule: "shadowfb"
[ 15.399] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 15.400] (II) Module shadowfb: vendor="X.Org Foundation"
[ 15.400] compiled for 1.8.1.902, module version = 1.0.0
[ 15.400] ABI class: X.Org ANSI C Emulation, version 0.4
[ 15.400] (--) Depth 24 pixmap format is 32 bpp
[ 15.405] (II) NOUVEAU(0): Opened GPU channel 1
[ 15.406] (II) NOUVEAU(0): [DRI2] Setup complete
[ 15.406] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau_vieux
[ 15.406] (II) NOUVEAU(0): GART: 64MiB available
[ 15.688] (II) NOUVEAU(0): GART: Allocated 16MiB as a scratch buffer
[ 15.702] (II) EXA(0): Driver allocated offscreen pixmaps
[ 15.702] (II) EXA(0): Driver registered support for the following operations:
[ 15.702] (II) Solid
[ 15.702] (II) Copy
[ 15.702] (II) Composite (RENDER acceleration)
[ 15.702] (II) UploadToScreen
[ 15.702] (II) DownloadFromScreen
[ 15.714] (==) NOUVEAU(0): Backing store disabled
[ 15.714] (==) NOUVEAU(0): Silken mouse enabled
[ 15.721] (II) NOUVEAU(0): NVEnterVT is called.
[ 15.721] (**) NOUVEAU(0): DPMS enabled
[ 15.721] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 15.722] (--) RandR disabled
I think the bit about uninstalling the xf86-video-vesa driver was a red herring - but if you uninstall that and the xf86-video-nv driver you know they can't be messing things up. Do a 'cat /var/log/pacman.log | grep xf86-video*' to see what you've got installed.
Pete
Last edited by shetland_breeder (2010-07-02 11:55:01)

Strange Keyboard behaviour with Pressure on Body

Any else experience this problem?
Basically when I am typing and I lean with my palms on the body of the macbook (not overly hard) the keyboard starts acting really strange. Keys I press won't work, and other keys will just randly start being hit. If I lift my hands off the body of the macbook all returns to normal. Seems like a short of some sort. Is this a common problem or just on my macbook?

Has no one an idea?

Strange sorting behaviour with Collator

Hi all, I'm sorting a list of Icelandic words using a Collator and I am getting rather peculiar results (the locale is is_IS, using jdk1.6.0_20).
List<String> list = Arrays.asList(
        "Veiðifélag Hörðudalsár",
        "Veiðifélagið Búrfell (Hólmkelsá)",
        "Veiðifélag Hvammsár",
        "Veiðifélag Jökulsár á Dal",
        "Veiðifélagið Skrauma",
        "Veiðifélag Kiðafellsár",
        "Veiðifélagið Kolka");
Collections.sort(list, Collator.getInstance());Resulting list (incorrectly sorted, with the three 'Veiðifélagið...' items appearing in the middle):
Veiðifélag Hvammsár
Veiðifélag Hörðudalsár
Veiðifélagið Búrfell (Hólmkelsá)
Veiðifélagið Kolka
Veiðifélagið Skrauma
Veiðifélag Jökulsár á Dal
Veiðifélag Kiðafellsár
Collections.sort(list);Resulting list (correctly sorted):
Veiðifélag Hvammsár
Veiðifélag Hörðudalsár
Veiðifélag Jökulsár á Dal
Veiðifélag Kiðafellsár
Veiðifélagið Búrfell (Hólmkelsá)
Veiðifélagið Kolka
Veiðifélagið Skrauma
I'm having a hard time seeing anything logical about this. I've tried playing with (as opposed to learning about/understanding) the strenght/decomposition properties of the Collator instance but that doesn't seem to have any effect.
I feel like I'm totally misunderstanding something here, can anyone help me point out what that is?

That's pretty much all the code, as I'm just using the default Collator returned by Collator.getInstance(), my assumption is that it should sort correctly according to the current locale (is).
public class Test {
public static void main(String[] args) throws Exception {
    List<String> list = Arrays.asList(
            "Veiðifélag Hörðudalsár",
            "Veiðifélagið Búrfell (Hólmkelsá)",
            "Veiðifélag Hvammsár",
            "Veiðifélag Jökulsár á Dal",
            "Veiðifélagið Skrauma",
            "Veiðifélag Kiðafellsár",
            "Veiðifélagið Kolka");
    final Collator collator = Collator.getInstance();
    Collections.sort(list, collator);
    //print list contents... incorrect result
    Collections.sort(list);
    //print list contents... correct result
}

Strange stack behaviour with referenced files

Similar Messages

Maybe you are looking for