search for: autolaunch

...ied this, I could type a win .exe file from the console and run it without typing wine [win_exe_name]. I could run a win exe from Konqueror by just clicking on it. That doesn't work now, with a new install. Did I set something up wrong? Or is there another version that handles the "autolaunch" by detecting the executable type and running WINE automatically? Thanks! Hal

Dear all, I'm trying to run function "qvalue" that requires Tcl/Tk interface. But after loaded the "tcltk" package, it would automatically launch "point-and-click" that forces me to run analysis in a new window whenever I want to use the function. I would be grateful if anyone knows how to remove the auto-launch operation in R so that I can run the function

Dear All, Apologies for this simple question and thanks in advance for any help given. I want to make from my .R script an .exe file. Is there any way to transfort my script to an autolaunch file? It means it runs the script by double clicking on it. p.s.: I'm using windows -- View this message in context: http://www.nabble.com/executable-script-tf4806651.html#a13751752 Sent from the R help mailing list archive at Nabble.com.

...em is with either Tracker or Samba. I also tried with Debian 10, Samba 4.11.13 and Tracker 2.1 and I get this when opening the share: [2020/10/02 16:15:27.269248, 1] ../../source3/rpc_server/mdssvc/mdssvc.c:739(tracker_con_cb) Could not connect to Tracker: Failed to load SPARQL backend: Cannot autolaunch D-Bus without X11 $DISPLAY So this points more to a DBus problem. I even tried to run Tracker under the root account but no change. The last time I tried Tracker backend was about two years ago and I got it working then, not sure what?s the problem this time. Any pointers? Thanks.

...to socket /tmp/dbus-yhDz4m8loi By the way the same message as I get from qdbus. There are no files called /tmp/dbus* on my system but some dbus applications are running: linux-dev:~# ps ax | grep dbus 1774 ? Ss 0:00 /usr/bin/dbus-daemon --system 2436 ? S 0:00 dbus-launch --autolaunch 1996d3ce005bf1ed73cca8164d21a0b5 --binary-syntax --close-stderr 2437 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session The error-message-box containing: most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.or...

...tc. The server log shows this: 2019-04-29 15:32:07.306+0000: 20863: info : libvirt version: 5.2.0 2019-04-29 15:32:07.306+0000: 20863: info : hostname: koji 2019-04-29 15:32:07.306+0000: 20863: error : virDBusGetSessionBus:169 : internal error: Unable to get DBus session bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 2019-04-29 15:32:24.534+0000: 20852: error : qemuConnectOpen:1127 : internal error: unexpected QEMU URI path '/system', try qemu:///session 2019-04-29 15:32:24.534+0000: 20851: error : virNetSocketReadWire:1803 : End of file while reading data: Input...

=========== process 5496: arguments to dbus_connection_ref() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2497. This is normally a bug in some application using the D-Bus library. org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to autolaunch D-Bus session: PuTTY X11 proxy: wrong authentication protocol attemptedAutolaunch error: X11 initialization failed. It seems to me even in the console environment, DISPLAY has to be set for d-bus to work. Is it mandatory? Any work around? Thanks in advance ------=_NextPart_000_006...

I'm new to Linux/Ubuntu and need some help getting Legions: Overdrive (http://www.legionsoverdrive.com/) with PlayOnLInux and WINE. Legions: Overdrive is a sci-fi FPS game, Freedom of movement returns in this spiritual successor to Tribes. Travel by jetpack and ski over foreign landscapes, dodging grenades and shooting enemies in deathmatch mode. Sharpen your shooting accuracy or prepared to

...: > > 2019-04-29 15:32:07.306+0000: 20863: info : libvirt version: 5.2.0 > 2019-04-29 15:32:07.306+0000: 20863: info : hostname: koji > 2019-04-29 15:32:07.306+0000: 20863: error : virDBusGetSessionBus:169 : > internal error: Unable to get DBus session bus connection: Unable to > autolaunch a dbus-daemon without a $DISPLAY for X11 > 2019-04-29 15:32:24.534+0000: 20852: error : qemuConnectOpen:1127 : > internal error: unexpected QEMU URI path '/system', try qemu:///session > 2019-04-29 15:32:24.534+0000: 20851: error : virNetSocketReadWire:1803 : > End of file while...

...gt; I also tried with Debian 10, Samba 4.11.13 and Tracker 2.1 > and I get this when opening the share: > > [2020/10/02 16:15:27.269248, 1] > ../../source3/rpc_server/mdssvc/mdssvc.c:739(tracker_con_cb) > Could not connect to Tracker: Failed to load SPARQL > backend: Cannot autolaunch D-Bus without X11 $DISPLAY > > So this points more to a DBus problem. I even tried to run > Tracker under the root account but no change. The last time I > tried Tracker backend was about two years ago and I got it > working then, not sure what?s the problem this time. > >...

...r or Samba. > > I also tried with Debian 10, Samba 4.11.13 and Tracker 2.1 and I get this when opening the share: > > [2020/10/02 16:15:27.269248, 1] ../../source3/rpc_server/mdssvc/mdssvc.c:739(tracker_con_cb) > Could not connect to Tracker: Failed to load SPARQL backend: Cannot autolaunch D-Bus without X11 $DISPLAY > > So this points more to a DBus problem. I even tried to run Tracker under the root account but no change. The last time I tried Tracker backend was about two years ago and I got it working then, not sure what?s the problem this time. > > Any pointers? &gt...

I am trying to use d-bus (client) inside a CGI perl environment where X11 DISPLAY is not set.

I want to run libvirtd as a special user, and allowing users that belong to a special group to connect via qemu+unix:///system (eg: unix socket). I did everything necessary to do so: created a libvirt user and group, added the libvirt user to the kvm group, added my normal user to the libvirt group, and made sure the socket is owned by libvirt:libvirt with permissions set to 770. libvirtd starts

...psd 2637 1 ... /usr/bin/dummy-ups -a heartbeat upsd 2641 1 ... /usr/sbin/upsd root 2645 1 ... /usr/sbin/upsmon upsd 2646 2645 ... /usr/sbin/upsmon upsd 3217 1 ... /usr/sbin/upssched UPS Eaton at localhost: On battery upsd 3236 1 ... dbus-launch --autolaunch=d1cd...ca5d2 ... upsd 3237 1 ... /bin/dbus-daemon --fork --print-pid 5 ... upsd 3241 1 ... /usr/lib/xfce4/notifyd/xfce4-notifyd upsd 3243 1 ... /usr/lib/xfce4/xfconf/xfconfd Thje last 4 lines are due to the use of notify-send. Note that the xfce4-notifyd daemon is r...

Yes, you are right. Listen, as the documentation is not very exaustive, can you explain briefly to me how a guest agent works? After installing it via the apt-get on the hypervisor (I am using ubuntu as host system) how can I create a script which would do this? That is waiting for an acpi signal and actually shut down the guest. And what other operation can you actually do with a guest agent? I