Monitoring Clementine with DBus

Hello,
I'm trying to achieve a result similar to the solution proposed here, but with Clementine instead of Rhythmbox, and since I'm not familiar with DBus (at all) I figured I'd try replacing only the parameters.
Basically, I want to have a function executed when the playing track changes.
It goes OK until the connection to the signal
player.connect_to_signal ("playingUriChanged", playing_song_changed)
because of the playingUriChanged
I looked for the equivalent for Clementine with qdbus and found this
signal void org.freedesktop.MediaPlayer.TrackChange(QVariantMap)
but I don't really know what to do with it since it takes a parameter.
Anyone knows how to achieve that? Or will I have to switch to Rhythmbox and forget about that nice rain sound?
Edit: Sorry, I just realized there is a 'Programming & Scripting' forum for that... woops
Last edited by HeroRAT (2013-02-10 22:07:37)

What MeatLink notes are you expecting? OEM documentation is at tahiti.oracle.com. Tivoli documentation is provided by the vendor. MetaLink has a rich search engine.

Similar Messages

Problem with dbus

Hi!
I have a problem with dbus and libnotify :?
I've added dbus to rc.conf
DAEMONS=(metalog network netfs crond alsa dbus)
and starts gnome with
exec dbus-launch --exit-with-session gnome-session
but dbus-monitor says
My problem is the session bus seems to be missing...
If i started gnome and gajim from root account (bleh), i saw correct dbus-monitor message like:
signal sender=org.freedesktop.DBus -> dest=:1.0 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
string ":1.0"
method call sender=:1.0 -> dest=org.freedesktop.DBus path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='method_call'"
method call sender=:1.0 -> dest=org.freedesktop.DBus path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='method_return'"
method call sender=:1.0 -> dest=org.freedesktop.DBus path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='error'"
but gajim dbus notification still dont work.
I have
[#] pacman -Q |grep dbus
dbus 0.93-1
dbus-glib 0.71-1
dbus-python 0.71-1
in my two Arch Linux setups, but notification dont work (in my Gentoo linux install it works pretty well :?).
Cheers.
PS: When i exec this in Gentoo
notify-send -i gtk-dialog-question -u critical -t 20000 TEST tralalala
I get this, but in Arch i dont get anything :?

I'm not sure, because i guess same problem would affect other apps that need this file, not just terminal. But you may be right, i really don't know.
I'm using the official packages (testing), not shadowhand's ones.

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

My external monitor worked with my MacBook Pro before I took it on a little trip, now it won't work. Any suggestions?

My external monitor worked with my MacBook Pro before I took it on a little trip, now it won't work. Any suggestions?

Never mind. Sorry. It fixed itself.

Dual monitor setup with seperate resolutions

hey guys!
i currentley run thye latest version of archlinux with the cinnamon desktop environment and an nvidia geforce 7300SE graphics card.
im running a dual monitor setup with one 27" 1920x1080 monitor and one 27" 1024X768 monitor
because they have the same physical size they line up perfectley but because the resolution is different programs/mouse cursor movement doesnt, is there any way (without changing the resolutions) to compensate this effect so that in the eyes of linux/cinnamon the monitors line up so that for example dragging a window goes seamlessley between the 2 monitors.
i HAVE found out the panning option in the nvidia x server settings, but that really isnt what i am looking for...
Last edited by RikSolo (2014-08-04 11:25:02)

A magnifier following the window down to the pixel, zooming to the exact size of 540 pixels the 384 pixels window could create an illusion of just that. It would be highly impractical however, not mention all the hacking time. Even if you would manage to get two screen with different sized icons, so that they match visually, the windows and fonts resizing on the fly, wmctrl might help with windows alone, no their themes (buttons, borders thickness etc.), you would still be left with a visually differently sized mouse cursor. Technically such a feat should be possible, but who is going to code it? Nvidia?
Last edited by emeres (2014-08-04 18:48:59)

I have tried to view videos created in premiere elements 10 and I get the following message: "this file type is not supported, or the required codec is not installed. When it opens there is a red screen in the monitor panel with Korean writing which als

I have tried to view videos created in premiere elements 10 and I get the following message: "this file type is not supported, or the required codec is not installed. When it opens there is a red screen in the monitor panel with Korean writing which also appears in the place of each clip in the video. I tried uninstalling and reinstalling premiere elements 10, but that did not have any effect on the video. Do you have any suggestions? I researched codec, but do not understand them at all.

gloucester
In case you did not find it, the following is a copy/paste of the Announcement on Premiere Elements 19/NVIDIA GeForce
that appears at the top of this forum.
Premiere Elements 10 NVIDIA Video Card Driver Roll Back
If you are a Premiere Elements 10 user whose Windows computer uses a NVIDIA GeForce video card and you are experiencing
Premiere Elements 10 display and/or unexplained program behavior, then your first line of troubleshooting needs to be rolling
back the video card driver version instead of assuring that it is up to date.
Since October 2013 to the present, there have been a growing number of reports about display and unexplained workflow
glitches specific to the Premiere Elements 10 user whose Windows computer has a NVIDIA GeForce video card. If this applies
to you, then the “user to user” remedy is to roll back the NVIDIA GeForce video card driver as far as is necessary to get rid of
the problems. The typical driver roll back has gone back as far as March – July 2013 in order to get a working Premiere
Elements 10. Neither NVIDIA nor Adobe has taken any corrective action in this regard to date, and none is expected moving forward.
Since October 2013, the following thread has tried to keep up with the Premiere Elements 10 NVIDIA reports
http://forums.adobe.com/thread/1317675
Older NVIDIA GeForce drivers can be found
http://www.nvidia.com/Download/Find.aspx?lang=en-us
A February 2014 overview of the situation as well as how to use the older NVIDIA GeForce drivers for the driver roll back can be found
http://atr935.blogspot.com/2014/02/pe10-nvidia-video-card-roll-back.html
ATR

Dual monitor issue with 10.8 and Windows 7 (bootcamp)

I've a read a lot of threads here about people having nightmare-ish problems after upgrading. Thankfully, this isn't one of them, just a frustration that I'd like advice on.
My system: 2010 13" MBP, 2.4GHz Intel Core 2 Duo, 8GB RAM, 320GB HD. Work setup has external 17" Dell Widescreen monitor connected with VGA to miniDisplay adapter. Home theater setup has 23" Dell monitor connected with HDMI to miniDisplay cable.
I upgraded from 10.6.8 to 10.8, as I like to stay up to date and it seemed ML fixed many of the Lion issues. After finding out Front Row is completely gone I just about reverted (my laptop doubles as my home theater control). I found XBMC, and it works, sort of (anyone with news on whether Front Row will be returned to us, let me know!).
Enough babbling, my issue:
When I switch from bootcamp windows 7 back to OS X, my second monitor's resolution is all screwed up (very low) and the dock and menu bar are BOTH on the second (Dell 17") screen, though it's not in a mirror mode.
Usually the dock is on the laptop screen, and the menu bar is on the second.
All I have to do is unplug the miniDisplay port and plug it back in, but is there a setting I'm missing to keep me from having to do this? Also, I've never used Windows at home, so I've never had to switch with the 23 inch monitor connected. Don't really want to try as that system is working quite well right now.
Thanks!
-Rob

It's NVidia GeForce 320M.
Just checked the drivers page and the Mac side only lists up to 10.6.8
Should I assume that the update needs to be on the Windows 7 side? At one point last November I tried to update on the Windows side and it caused all sorts of **** on my system causing me to have to reinstall both OS X and 7.
May be worth another try?
-Rob

Is the LG 22EN33S-B 22-inch LED 1920 x 1080 VGA Monitor compatible with mac via a vga to thunderbolt connection

Is the LG 22EN33S-B 22-inch LED 1920 x 1080 VGA Monitor compatible with mac via a vga to thunderbolt adapter?

The 1080p and 1080i options only appear on the HDMI display settings, the display settings for the thunderbolt to vga adaptor has 1920 x 1080.
Via the HDMI output of the Mini via an HDMI cable to a HDMI input on the Samsung the display fills the screen but the text looks vile.
The options for picture adjustement on the samsung include fill screen as you suggest
Using the thunderbolt to VGA adaptor the text looks as it should, crisp and clear but the display is shitfted to the right.
The options for picture adjustment on the Samsung does not have the 'fill screen' option available when the VGA input is selected. However a new option called 'pc screen adjustment' appears and you can nudge the display over to the left a bit but not enough to cover the whole screen.
I remind you the pc worked perfectly 1920 x 1080 on the same VGA cable and input to the samsung.

External Monitor blurry with MacBook Pro

Good day, I have searched the forums but have not found a solution to my problem...
I recently purchased a Dell 2005FWP External Monitor and plugged it in (DVI to VGA) to my MacBook Pro. It automatically adjusted to a 800x600 resolution which of course is not ideal. The menu gives a long list of display resolutions but most of them are "not available" when I click on them. I have tried switching the docks and the monitors to the opposite sides on "Arrangement" of displays but I still don't get a different menu. I can't seem to find the menu of resolutions for the MacBook Pro either.
Please let me know what I am doing wrong...Sorry, I know I am clueless!!
Thank you!

I have a ViewSonic VX2035wm display connected to my MacBook Pro - the image on the external monitor shows ghosting and double images like we used to see on old tube TVs.
Here is a post from MacFixIt.com that details my problem.
http://www.macfixit.com/article.php?story=20081020231611468
Late-2008 MacBooks: Image problems on external displays with mini-DisplayPort converters
The new MacBooks and MacBook Pros come with a Mini-DisplayPort adaptor for external video, and Apple supplies various adaptors (DP to DVI, and DP to VGA) to accommodate current monitors. Some users are having difficulties with their adaptors when connected to certain monitors.
Apple Discussions poster Ocell writes:
"I have the exact same problem with my Viewsonic VG2030wm 20" LCD. I've ruled out bad DVI cables. The Macbook Pro works with my 12" Cintiq's display, and the Viewsonic works with my Intel iMac, so the video out/mini displayport adaptor/dvi cable/viewsonic display are all operational. It's just the specific combination of the Macbook Pro and Viewsonic that doesn't work."
This problem has been found to frequently occur with DVI adaptors attached to their computers, however it has also happened with users connecting to the VGA adaptors. In these cases, unlike the DVI situation where no signal gets through, users have noticed the screen blinking or shutting off at random times. While drivers may definitely be suspect, the problem appears to be hardware-related since users have experienced the issue both in Mac OS X as well as in Windows via Boot Camp.
The DisplayPort connections used on the new MacBooks have slight differences in their protocols than other connection types, which allows for expanded functions in smaller connectors, but also can run users into difficulties, especially when older connetion types are used. While there could be software involvement in this problem, it sounds like there's most likely a firmware-related problem that hopefully can be patched by Apple, or at least be accommodated for in a driver update.
Things to Try
Reset the monitor to defaults If there is a method for fully resetting the monitor, try doing that first. Most have a menu option to reset to factory defaults, but in addition there may be a way to fully reset the device such as unplugging it for an extended period of time. This information may be available on the manufacturer's website, or users can just try unplugging the device for an extended period such as 20-30 minutes.
Toggle various monitor setups In the "Displays" system preferences, toggle desktop mirroring on and off to see if the monitor is not just extending the desktop to the second monitor. Especially if users have black wallpaper on their desktops, secondary monitors that are just serving as extended desktops may appear to be off when connected. Alternatively users can try dragging documents off the sides of their main monitor to see if they go over to the second monitor.
Reset the computer Users might try resetting the computer's PRAM (which does contain some graphics parameters) by holding the options, command, P, and R keys down at bootup until the computer resets and makes the boot chimes again. Release the keys and allow the computer to boot normally. Additionally, users might try resetting the computer's system management controller. Here is an Apple Support article on how to do that.
Use a different monitor Unfortunately, with hardware problems such as this users will not be able to do much, so if another monitor is available that works then users should switch to that.
Try another adaptor Many monitors support both VGA and DVI inputs, and there is potential for users to get things working by using another connection type. Additionally, while it may be a long shot, users might also try chaining together various adaptors. For instance, users might try going from displayport to DVI, and then using a DVI to VGA adaptor as the next connection, to see if that somehow sends a proper signal to the monitor.

Dual Monitor Problems with Vista

I have a Lenovo T61 laptop running Vista ultimate 32 bit, SP1. I schlep this back and forth from home to work and put it in docking stations at each location. The docking stations have external monitors attached. At work I have a Viewsonic VX2035wm 20" Wide screen, (16:10) monitor with optimum resolution of 1680x1050. At home I have a Viewsonic VA912b 19" standard aspect ratio monitor with a suggested resolution of 1280x1024.
I typically run in dual monitor mode using my laptop display and the external monitor and extend the display across both monitors. Sometimes I run with the laptop display as the primary monitor, sometimes the external is the primary.
When I take my system from one location to another, generally upon boot or resume it recognizes the different monitor configurations and adjusts the display properties accordingly. However, about once a week I have a problem. For example, I shutdown at home, came into work and attempted to boot the system. Upon boot my external monitor displayed a frequency out of range error and did not display anything else. I suspect that the external port was configured to a setting that was not supported by the monitor. It appears that this was the primary display because my laptop only showed the background and the desktop did not display. Since nothing was displayed, I couldn't click the start menu, any icons, etc. I tried to adjust the monitor configuration by right clicking the laptop screen and selecting personalize, but the personalization dialog would not show up and I suspect that it went to the blanked out external monitor.
Please advise on how I can handle this situation. Is there any way to move the display from the external to the notebook when this happens? I noticed that Viewsonic has Vista drivers listed on their web site. Would it help to download and install these? Is there anything else you can suggest?

The main point of posting this topic was to point out the appalling service offered by Adobe but, of course resolving this issue would be nice also.
So here goes;
Dual monitor issue (Applies to CS4 applications; Photoshop, Illustrator, InDesign etc. but not Flash or Dreamweaver or any other manufacturers software).
I have 2 monitors installed with Windows Vista 64bit, using Nvidia Quadro FX 1700:
-1280 x 1024 (primary display on the left) &
-1440 x 900 (on the right)
With a CS4 application maximised in the larger monitor, all the drop down menus display fine, if the chosen drop-down menu is taller than the height of the monitor (fonts, for instance), an arrow appears at the bottom of the menu so that I can scroll down the rest of the menu. If I then reduce the size of the CS4 application window, move it to the smaller monitor and maximised it again, the drop-down menu (which displayed and functioned fine in the primary monitor) is cropped off so I can't access the rest of the menu.
This might seem a minor irritation, but for batch-processing of merged files (the main purpose for having 2 monitors) CS4 makes the 2nd monitor redundant.
Another, less irritating issue (again, only with the applications named above) is that the window when maximised in the secondary monitor 'hangs over' into the primary monitor.

Integrate Business Activity Monitoring (BAM) with Oracle Forms Recognition

Hi All,
As per project requirement, I have to integrate Business Activity Monitoring (BAM) with Oracle Forms Recognition.
Does anyone have an idea how can this be achievable from OFR Verifier?
Thanks,
Moumi.

Hi All,
Apart from my previous queries, I found that there is an sample reporting program - Oracle Application Express application has been developed and tested using version 4.1 of AppExpress.
To access OFR tables I run the below script in below sequence in my local IPM environment as found in this link- http://workplacedba.blogspot.in/2012/11/ofr-odc-installation.html
Seq 1 - 01-OFR-AP-Tables_Oracle.sql
Seq 2 - 02-OFR-AP-Reporting_Oracle.sql
Seq 3 - 03-XX_ROUND_IT.fnc
Seq 4 - 04-XX_ROUNDDOWN.fnc
Seq 5 - 05-XX_ROUNDUP.fnc
Seq 6 - 06-OFR-AP-EBS-Views.sql
Seq 7 - 07-INVOICE_NUMBER_FORMATS_INS.sql
Seq 8 - 08-Insert Into Company.sql
I couldn't found the below queries in my installables -
Seq 3 - 03-XX_ROUND_IT.fnc
Seq 4 - 04-XX_ROUNDDOWN.fnc
Seq 5 - 05-XX_ROUNDUP.fnc
Seq 7 - 07-INVOICE_NUMBER_FORMATS_INS.sql
Seq 8 - 08-Insert Into Company.sql
can anyone provide me these sql scripts?
Thanks,
Moumi

Will a Mac cinema display monitor work with an Acer hard drive

Will a Mac cinema display monitor work with an Acer hard drive?

Hello,
Which exact Cinema Display & which Acer HDD?

Does LR handle a dual monitor setup with different aspect ratios (16:9 and 16:10)?

Does LR 5 handle a dual monitor setup with different aspect ratios (16:9 and 16:10)?
I'm planing to buy a 27" 16:9 monitor and use it as primary together with a 22" 16:10. Does any have any idea?
Thanks

Moreover, the two monitors can have completely different characteristics. As always, you really need to calibrate/profile any monitor (with a hardware tool - Spyder, Colormunki etc). That's no more important with two monitors, but you see for sure if you don't, as two dissimilar monitors will then probably look different.

Secondary monitor displays with colorshift

secondary monitor displays with colorshift in LR4.1rc2. this is on windows 7/64.
Both my monitors i have are calibrated with spyder3, one is hardwarecalibrated eizo CG243, the other a HP2475 calibrated with spyder4 elite software.
Colorshift shows same characteristics when i switch LR app window with secondary window.
IT looks as if sRGB profile is applied to the secondary preview, because of the strong/overly saturated colors.
It seems to me a softwarebug, which makes secondary display inusable.
How is color management supposed to work in LR4?

It works fine with me (LR4.1 RC2, but previously used RC1, LR4.0, LR3.6... all worked the same).
I have a wide-gamut HP LP2475w (approx Adobe RGB gamut) and a Samsung193P (approx sRGB). Both calibrated/profiled with Color Munki Display, but I've previously used Eye One and Spyder units. After calibration/profiling, LR main and secondary display look the same in both Loupe and Develop view, and no matter which is LR's primary display. (Obviously, colours outside sRGB gamut don't look the same!)
I've just checked, and it still seems to be the case on my set up (W7 64-bit).
I can't think what the problem might be. I guess you've checked in Control Panel / Color Management that the correct profiles are assigned to each monitor. And I guess that you've got a video card with dual LUTs that allows separate calibration (mind you, I've never come across any cards that don't have separate LUTs, but apparently there are some).
PS - Web view might be different, as I think LR uses IE for rendering in web view only, and IE doesn't colour-manage properly.

Monitoring Clementine with DBus

Similar Messages

Maybe you are looking for