Re: [arch-general] Problem install shrew vpn client
Am 26.09.18 um 10:47 schrieb Maykel Franco via arch-general: > Hi, I received this error when compile the program shrew vpn client: > > yaourt -S shrew-vpn-client > > /tmp/yaourt-tmp-maykel/aur-shrew-vpn-client/src/ike/source/libike/manager.file.cpp: > In member function 'bool _CONFIG_MANAGER::file_pcf_load(CONFIG&, const > char*, bool&)': > /tmp/yaourt-tmp-maykel/aur-shrew-vpn-client/src/ike/source/libike/manager.file.cpp:682:19: > error: aggregate 'EVP_CIPHER_CTX ctx_cipher' has incomplete type and > cannot be defined > EVP_CIPHER_CTX ctx_cipher; >^~ should this even be answered here? https://github.com/openssl/openssl/issues/962#issuecomment-427752560 TLDR; >> So, all existing Software must be rewritten just to be able to use 1.1.x ? >> Do you have any idea how many Million lines of code are affected by this crap?? > Yes, applications must be changed to use 1.1.x.
Re: [arch-general] QT apps try to be HiDPI on a non HiDPI monitor
Am 24.04.2018 um 19:27 schrieb Ricardo Band via arch-general: > Ahoi, > > I have a 1920x1080 monitor in my notebook which is afaik not HiDPI. > Even if I launch for example qtpass with: > > env QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCALE_FACTOR=1 > QT_SCREEN_SCALE_FACTORS=1 QT_DEVICE_PIXEL_RATIO=1 > QT_STYLE_OVERRIDE=gtk2 QT_QPA_PLATFORMTHEME=qt5ct GDK_BACKEND=x11 > qtpass > > It looks like this: https://imgur.com/a/jKLbeLF > > I tried everything but it didn't change anything. I'm using i3, so no > fancy desktop environment that could help or not help. ;) > > See this stackexchange: https://unix.stackexchange.com/questions/433385/scaling-hidpi-issue-for-qt5-applications-under-gnome/437467 It also links to https://wiki.archlinux.org/index.php/HiDPI#Qt_5 For seafile this helped me: QT_AUTO_SCREEN_SCALE_FACTOR=0 nohup seafile-applet > /dev/null & I'm using gnome on X and not wayland, maybe that makes a difference.
Re: [arch-general] VirtualBox crashes when adding choose existing to SATA controller
Am 14.10.2016 um 10:01 schrieb Ralf Mardorf: > On Fri, 14 Oct 2016 09:29:08 +0200, Peter Bauer wrote: >> I guess I have to use some Command line to get the machine up again... > > Take a look at the log files. > > The paths are not necessarily those > > .VirtualBox/VBoxSVC.log* > VirtualBox\ VMs/*/Logs/VBox.log* > Obviously I was running gnome-shell (mutter) with wayland, not Xorg. I was able to switch to Xorg in the log-in screen (GDM). Now no crash happens. I will try on Monday with wayland again and try to provide logs. The Windows7 32Bit machine was also constantly crashing on wayland. With xorg, it seems stable till now. > > Btw. regarding to https://bugs.archlinux.org/task/50120 I stay with > 5.0.24. > > [rocketmouse@archlinux ~]$ pacman -Q virtualbox > virtualbox 5.0.24-1 > [rocketmouse@archlinux ~]$ objdump -p /usr/lib/virtualbox/components/* > 2>/dev/null|grep libvpx > NEEDED libvpx.so.3 > [rocketmouse@archlinux ~]$ pacman -Ql libvpx | grep so > libvpx /usr/lib/libvpx.so > libvpx /usr/lib/libvpx.so.4 > libvpx /usr/lib/libvpx.so.4.0 > libvpx /usr/lib/libvpx.so.4.0.0 > [rocketmouse@archlinux ~]$ ls -hl /lib/libvpx.so* > lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so -> libvpx.so.4.0.0 > lrwxrwxrwx 1 root root 15 Jan 16 2016 /lib/libvpx.so.3 -> libvpx.so.3.0.0 > lrwxrwxrwx 1 root root 15 Jan 16 2016 /lib/libvpx.so.3.0 -> libvpx.so.3.0.0 > -rwxr-xr-x 1 root root 3.4M Jan 16 2016 /lib/libvpx.so.3.0.0 > lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so.4 -> libvpx.so.4.0.0 > lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so.4.0 -> libvpx.so.4.0.0 > -rwxr-xr-x 1 root root 3.3M Aug 1 19:41 /lib/libvpx.so.4.0.0 > This is a neat info. But I don't care about the look of the mouse pointer. I get things done (TM) even with an ugly cursor. On the other hand, wayland brings down gnome-shell on my multihead setup. I have a lenovo x230t and two external monitors. Spontaneous log-outs, all input devices dead etc. Backups for the win! With Xorg no big problems. At least it's Friday.
[arch-general] VirtualBox crashes when adding choose existing to SATA controller
The VirtualBox gui crashes when you want to add an existing hard disk to a SATA controller. Steps to reproduce: Select a Machine -> Settings -> Storage -> Controller: SATA -> Add hard disk -> Choose existing disk Then you will see the following message when you have started the Oracle VM VirtualBox Manager in a terminal: % VirtualBox Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile (VirtualBox:7254): Gdk-WARNING **: gdkwindow-x11.c:5554 drawable is not a native X11 window [1]7254 segmentation fault VirtualBox The corresponding machine had no hard disk applied. I guess I have to use some Command line to get the machine up again...
Re: [arch-general] VirtualBox ALT-key problems (especially with Adobe programs)
On gnome you can modify this behavior with the gnome-tweak-tool in the Window section. I changed the Window-Action key from "ALT" to "Super". I faced the same issues with the Layout-software EAGLE on Windows in VirtualBox. Am 09.07.2016 um 17:04 schrieb Bruno Widmann via arch-general: > Try some other window manager, that way you can find out if it's gnome's wm > which is causing the problem. Personally i'm using fvwm, and everything in > my windows vboxes is working fine. Haven't tried photoshop though... > > On Sat, Jul 9, 2016 at 2:11 PM, Klaus Doblmann M.A. wrote: > >> On 2016-07-09 13:18, Ralf Mardorf wrote: >>> On Sat, 9 Jul 2016 12:57:19 +0200, Klaus Doblmann M.A. wrote: I'm having troubles getting the ALT-key to work properly in VirtualBox as a modifier in applications like Photoshop for things like the clone tool, it isn't recognised as the ALT-key. >>> >>> Hi, >>> >>> perhaps the used version of photoshop does work better when using wine. >>> Wine is as easy to use as vbox, it doesn't require graphical desktop >>> sharing by VNC and doesn't require SAMBA to share files or something >>> similar, that is needed by other virtual machines. >>> >> >> Hi Ralf, >> >> Thanks for your reply. I'm very familiar with Wine, however I can't even >> get past installing the Creative Cloud application which works as a >> hub/installer for the main apps. Some people report success on running >> Photoshop on Wine with a lot of tinkering but some of these reports seem >> to use unlicensed versions... ;) >> >> The whole solution to my problem should be rather easy - SOMETHING >> messes with the Alt key on the linux side - it's just a matter of >> finding out what... ;) >> >> Klaus >> >
Re: [arch-general] [Bulk] Re: FS#41424 - Virtualbox 4.3.14, USB doesn't work flawlessly
I accidently upgraded VirtualBox, systemd and linux. The problem I had with USB passtrough are gone. I don't know at which version they were resolved, as reference here my currently installed versions: core/linux 3.18.5-1 (base) community/virtualbox 4.3.20-4 Am 03.12.2014 um 09:46 schrieb Peter Bauer: > I need to downgrad systemd to keep my system working with the older > kernel (3.11.6-1). I received huge amount of errors in when I ran tail > -f /var/log/messages: > > > Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 28 00 00 08 00 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] > Sep 5 18:49:38 localhost kernel: Info fld=0x0 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: > Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 30 00 00 08 00 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] > Sep 5 18:49:38 localhost kernel: Info fld=0x0 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: > Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 38 00 00 08 00 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] > Sep 5 18:49:38 localhost kernel: Info fld=0x0 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] > Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: > Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 40 00 00 08 00 > Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code > > > This could be cause by my internal SD-Card-Reader. I have a Lenovo X230 > tablet. > > I copied old versions from /var/cache/pacman/pkg/ downgraded following > packages: > > pacman -U syslog-ng-3.5.6-1-x86_64.pkg.tar.xz > systemd-sysvcompat-216-3-x86_64.pkg.tar.xz > libsystemd-216-3-x86_64.pkg.tar.xz systemd-216-3-x86_64.pkg.tar.xz > lib32-systemd-216-2-x86_64.pkg.tar.xz > > My IgnPkg line in /etc/pacman.conf is getting ridicolous: > > IgnorePkg = virtualbox virtualbox-guest-iso virtualbox-guest-modules > virtualbox-host-modules linux syslog-ng systemd-sysvcompat libsystemd > systemd lib32-systemd > > All this just to keep USB passtrough working. Hopefully gnome will not > make a dependency on a systemd version. Then I will be really f*. > > > Am 03.09.2014 um 14:10 schrieb Peter Bauer: >> I downgraded and have postive results. >> >> >> Currently installed: >> >> virtualbox 4.2.18-1 >> virtualbox-guest-iso 4.2.18-1 >> virtualbox-host-modules 4.2.18-7 >> linux 3.11.6-1 >> >> >> No USB read/write problems any more. I still get Malformed Packet in >> Wireshark, but this seems unrelated. >> >> However now I receive crashes of my VM when attaching/detaching USB >> devices to my VM often. Guess I have to live with that. >> >> >> Am 03.09.2014 um 12:54 schrieb Peter Bauer: >>> Hi, >>> >>> I have also issues with USB devices on Windows 7 32Bit guest. The >>> devices I use are mainly USB Serial COM ports. On top of that a >>> proprietary binary protocol is used. >>> >>> The applications that communicate with the USB Serial COM ports are >>> constantly having problems reading and writing data. >>> >>> Installed: >>> virtualbox 4.3.14-3 >>> virtualbox-guest-iso 4.3.14-1 >>> virtualbox-guest-modules 4.3.14-5 >>> virtualbox-host-modules 4.3.14-5 >>> Linux localhost 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST >>> 2014 x86_64 GNU/Linux >>> >>> Extension Pack 4.3.14r95030 >>> >>> With usbmon and wireshark I could see a lot of malformed USB packets. >>> I'm afraid I don't kno
Re: [arch-general] [Bulk] Re: FS#41424 - Virtualbox 4.3.14, USB doesn't work flawlessly
I need to downgrad systemd to keep my system working with the older kernel (3.11.6-1). I received huge amount of errors in when I ran tail -f /var/log/messages: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 28 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 30 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 38 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 40 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code This could be cause by my internal SD-Card-Reader. I have a Lenovo X230 tablet. I copied old versions from /var/cache/pacman/pkg/ downgraded following packages: pacman -U syslog-ng-3.5.6-1-x86_64.pkg.tar.xz systemd-sysvcompat-216-3-x86_64.pkg.tar.xz libsystemd-216-3-x86_64.pkg.tar.xz systemd-216-3-x86_64.pkg.tar.xz lib32-systemd-216-2-x86_64.pkg.tar.xz My IgnPkg line in /etc/pacman.conf is getting ridicolous: IgnorePkg = virtualbox virtualbox-guest-iso virtualbox-guest-modules virtualbox-host-modules linux syslog-ng systemd-sysvcompat libsystemd systemd lib32-systemd All this just to keep USB passtrough working. Hopefully gnome will not make a dependency on a systemd version. Then I will be really f*. Am 03.09.2014 um 14:10 schrieb Peter Bauer: > I downgraded and have postive results. > > > Currently installed: > > virtualbox 4.2.18-1 > virtualbox-guest-iso 4.2.18-1 > virtualbox-host-modules 4.2.18-7 > linux 3.11.6-1 > > > No USB read/write problems any more. I still get Malformed Packet in > Wireshark, but this seems unrelated. > > However now I receive crashes of my VM when attaching/detaching USB > devices to my VM often. Guess I have to live with that. > > > Am 03.09.2014 um 12:54 schrieb Peter Bauer: >> Hi, >> >> I have also issues with USB devices on Windows 7 32Bit guest. The >> devices I use are mainly USB Serial COM ports. On top of that a >> proprietary binary protocol is used. >> >> The applications that communicate with the USB Serial COM ports are >> constantly having problems reading and writing data. >> >> Installed: >> virtualbox 4.3.14-3 >> virtualbox-guest-iso 4.3.14-1 >> virtualbox-guest-modules 4.3.14-5 >> virtualbox-host-modules 4.3.14-5 >> Linux localhost 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST >> 2014 x86_64 GNU/Linux >> >> Extension Pack 4.3.14r95030 >> >> With usbmon and wireshark I could see a lot of malformed USB packets. >> I'm afraid I don't know enough to make an exact conclusion whats wrong >> in detail. >> >> I will try a downgrad from 4.3.14-3 to 4.3.12 and report again. >> >> >> >> >> Am 04.08.2014 um 22:05 schrieb Ralf Mardorf: >>> On Mon, 2014-08-04 at 20:15 +0100, Marco Monteiro wrote: >>>> I have experienced problems with USB also. My guest is Windows 8.1. >>>> When I try to access the USB device from Windows, the access fails >>>> and then everything inside the VM seems to start misbehaving. I cannot >>>> properly shutdown the VM - I have to kill the VBox process. >>> >>> Hi Marco, >>> >>> when the USB data transfer paused, the graphic performance and
Re: [arch-general] [Bulk] Re: FS#41424 - Virtualbox 4.3.14, USB doesn't work flawlessly
I downgraded and have postive results. Currently installed: virtualbox 4.2.18-1 virtualbox-guest-iso 4.2.18-1 virtualbox-host-modules 4.2.18-7 linux 3.11.6-1 No USB read/write problems any more. I still get Malformed Packet in Wireshark, but this seems unrelated. However now I receive crashes of my VM when attaching/detaching USB devices to my VM often. Guess I have to live with that. Am 03.09.2014 um 12:54 schrieb Peter Bauer: > Hi, > > I have also issues with USB devices on Windows 7 32Bit guest. The > devices I use are mainly USB Serial COM ports. On top of that a > proprietary binary protocol is used. > > The applications that communicate with the USB Serial COM ports are > constantly having problems reading and writing data. > > Installed: > virtualbox 4.3.14-3 > virtualbox-guest-iso 4.3.14-1 > virtualbox-guest-modules 4.3.14-5 > virtualbox-host-modules 4.3.14-5 > Linux localhost 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST > 2014 x86_64 GNU/Linux > > Extension Pack 4.3.14r95030 > > With usbmon and wireshark I could see a lot of malformed USB packets. > I'm afraid I don't know enough to make an exact conclusion whats wrong > in detail. > > I will try a downgrad from 4.3.14-3 to 4.3.12 and report again. > > > > > Am 04.08.2014 um 22:05 schrieb Ralf Mardorf: >> On Mon, 2014-08-04 at 20:15 +0100, Marco Monteiro wrote: >>> I have experienced problems with USB also. My guest is Windows 8.1. >>> When I try to access the USB device from Windows, the access fails >>> and then everything inside the VM seems to start misbehaving. I cannot >>> properly shutdown the VM - I have to kill the VBox process. >> >> Hi Marco, >> >> when the USB data transfer paused, the graphic performance and access to >> the VDI drive slowed down, for iTunes and other apps running on the XP >> guest. Performance for iTunes always is bad, but other apps usually run >> without issues. I always could shut down Windows, but sometimes much >> time was needed before I could use the menu. If you can't shutdown your >> guest, you could try to shut down the virtual machine by closing the >> VBox window, instead off killing the process. >> >> I add an additional comment to my bug report. >> >> "There isn't an issue for the USB mouse, but data transfer between VBox >> and an iPad2 is broken when I use 4.3.14. There aren't issues anymore, >> after I downgraded all packages to 4.3.12. The whole performance of Vbox >> is slower when syncing iTunes and an iPad with .14 and there are many >> unknown errors and timeouts, if you e.g. try to install 20 applications >> or more from iTunes running on the VBox guest to an iPad. Disconnecting >> the iPad's USB causes VBox to crash, if it is done without unchecking >> the iPad in VBox's devices menu, this doesn't happen when using .12. >> >> The used packages are virtualbox, virtualbox-host-dkms, >> virtualbox-extension-pack and I install the guest additions that fit to >> the installed version of virtualbox. Perhaps the culprit isn't the >> package virtualbox, it might be the package virtualbox-extension-pack, >> since it's needed for USB2 support." - >> https://bugs.archlinux.org/task/41424 >> >> JFTR everything already was ok, when I only downgraded the package >> virtualbox, disabled USB2 support and kept the 4.3.14 guest additions. >> In the mean time I downgraded all packages and add the 4.3.12 guest >> additions, so with the outdated version I now can use USB2 again. >> >> Perhaps you have the time confirm my bug report. >> >> Regards, >> Ralf >> >
Re: [arch-general] [Bulk] Re: FS#41424 - Virtualbox 4.3.14, USB doesn't work flawlessly
Hi, I have also issues with USB devices on Windows 7 32Bit guest. The devices I use are mainly USB Serial COM ports. On top of that a proprietary binary protocol is used. The applications that communicate with the USB Serial COM ports are constantly having problems reading and writing data. Installed: virtualbox 4.3.14-3 virtualbox-guest-iso 4.3.14-1 virtualbox-guest-modules 4.3.14-5 virtualbox-host-modules 4.3.14-5 Linux localhost 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux Extension Pack 4.3.14r95030 With usbmon and wireshark I could see a lot of malformed USB packets. I'm afraid I don't know enough to make an exact conclusion whats wrong in detail. I will try a downgrad from 4.3.14-3 to 4.3.12 and report again. Am 04.08.2014 um 22:05 schrieb Ralf Mardorf: > On Mon, 2014-08-04 at 20:15 +0100, Marco Monteiro wrote: >> I have experienced problems with USB also. My guest is Windows 8.1. >> When I try to access the USB device from Windows, the access fails >> and then everything inside the VM seems to start misbehaving. I cannot >> properly shutdown the VM - I have to kill the VBox process. > > Hi Marco, > > when the USB data transfer paused, the graphic performance and access to > the VDI drive slowed down, for iTunes and other apps running on the XP > guest. Performance for iTunes always is bad, but other apps usually run > without issues. I always could shut down Windows, but sometimes much > time was needed before I could use the menu. If you can't shutdown your > guest, you could try to shut down the virtual machine by closing the > VBox window, instead off killing the process. > > I add an additional comment to my bug report. > > "There isn't an issue for the USB mouse, but data transfer between VBox > and an iPad2 is broken when I use 4.3.14. There aren't issues anymore, > after I downgraded all packages to 4.3.12. The whole performance of Vbox > is slower when syncing iTunes and an iPad with .14 and there are many > unknown errors and timeouts, if you e.g. try to install 20 applications > or more from iTunes running on the VBox guest to an iPad. Disconnecting > the iPad's USB causes VBox to crash, if it is done without unchecking > the iPad in VBox's devices menu, this doesn't happen when using .12. > > The used packages are virtualbox, virtualbox-host-dkms, > virtualbox-extension-pack and I install the guest additions that fit to > the installed version of virtualbox. Perhaps the culprit isn't the > package virtualbox, it might be the package virtualbox-extension-pack, > since it's needed for USB2 support." - > https://bugs.archlinux.org/task/41424 > > JFTR everything already was ok, when I only downgraded the package > virtualbox, disabled USB2 support and kept the 4.3.14 guest additions. > In the mean time I downgraded all packages and add the 4.3.12 guest > additions, so with the outdated version I now can use USB2 again. > > Perhaps you have the time confirm my bug report. > > Regards, > Ralf >
