Kobil M-IDentity usb dongle : no write access anymore since 10.04

[GM_Ubuntu]

Binary package hint: hal

Hi.

I use a Kobil USB dongle to access my netbanking. Since I have upgraded to 10.04, I cannot run the specific piece of software embedded in the dongle. The error message stated that full access to the Kobil device is not granted. This happens even if run as root. I guess it means write access. This used to work in Karmic.

Here is the mount output for that particular device :
------------------
/dev/sr1 on /media/M-IDentity type iso9660 (ro,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500)
------------------

Here is the device file in the /dev directory :
------------------
brw-rw----+ 1 root cdrom 11, 1 2010-05-02 15:28 /dev/sr1
------------------

Also, as a workaround I tried to manually unmount the device and mount it elsewhere as root, It only mounts in ro mode anyway and I get the same permission issue eventually.

Not sure if Hal or Udev ... or whatever ?

Please note : this is not a duplicate of bug #432215, related to the same Kobil device, which seems to be fixed in Lucid.

[Carrupts (samuel-carrupt)]

Hi,

I also use this kind of key with MigrosBank and I've exactly the same problem.

I tried this hack as indicated on the website of the bank (http://www.migrosbank.ch/fr/MBancNet/MIDentity/FAQ.htm#), but it doesn't work.

Ubuntu Linux - Version 9.04 et ultérieures
Chemin: "/lib/udev/rules.d
Fichier: 50-udev-default.rules
Modifier la ligne: SUBSYSTEM==“usb“, <…> MODE=“0664“ en:
SUBSYSTEM==“usb“, <…> MODE=“0666“

I don't know if it's a Hal or Udev problem ???

[Patrick (patrick-oberholzer)]

I just called Migrosbank and they said they are working with Kobil to solve this issue on Lucid.
No update yet

[gabriela (salvie)]

@Patrick: thanks for giving them a call. I hope they'll manage, as 10.04 is an LTS release.

Btw. does it make any difference between Ubuntu 10.04 32bit or 64bit? It's 64bit here, but I didn't try it on any 32bit machine yet.

[mamamio (mamamio)]

Hi, I have the same problem on Lucid 10.04, 32bit, 2.6.32-22-generic.

[bibber78 (marco-bibbias)]

Hi. Same problem here. Lucid 10.04, 32bit, 2.6.32-22-generic.

[Markus (mar-ayg)]

Same problem her. Lucid 10.04, 64bit

[Farliec (farliec)]

Same problem here. Lucid 10.04, 64bit, 2.6.32-22-generic.

[Master-I (master-ilic)]

Same problem here. Ubuntu 10.04 (lucid), 2.6.32-22-generic , 32bit
I have upgraded from 9.10 where I also used the workaround to manually unmount the device and mount. In 10.04 this workaround don't work.

[draft (ridershome)]

From the website http://www.migrosbank.ch/de/MBancNet/MIDentity/FAQ.htm#ubuntu

Ich habe das Betriebssystem Ubuntu und möchte die neue Ubuntu-Version 10.04 installieren. Ist diese Version mit dem M-IDentity kompatibel?
Die neue Ubuntu-Version 10.04 ist derzeit nicht mit dem M-IDentity kompatibel. Das Problem wird jedoch mit dem kommenden M-IDentity-Release, voraussichtlich bis Ende Juni dieses Jahres, behoben sein.
Wir bitten Sie deswegen mit dem Update auf Ubuntu 10.04 bis zum neuen M-IDentity-Release zu warten, über den wir Sie rechtzeitig informieren werden.

So, we have to wait until end of June for a new M-IDentity USB stick...

[André Barmasse (barmassus)]

I wonder how they want to update the software on the stick if the stick itself is not accessible under Linux! Hahahaha!! Or are they sending a brand new stick to every customer of Migrosbank??

Anyway, I just wanted to add something that has been discussed elsewhere (https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/432215?comments=all). GM_Ubuntu said that if the Kobil stick does not work, he has to switch back to Windows. I think this is the wrong way. If an enterprise proclaims "user-friendliness" and "simplyness" of its product (https://www.kobil.com/index.php?id=49&L=0) then it really has to work for everybody - especially if that enterprise produces security products for a major Swiss bank! It is not acceptable that they get aware of a problem only AFTER an Ubuntu version has been released and try to fix it somehow within the next week or so. I would at least feel appeased, if they had put some informations about this problem either on the website of the Migrosbank or Kobil - but nothing! Not even the slightest hint or some lines that they are sorry for the inconvenience and working on the problem. This behaviour has nothing to do with user-friendlyness at all! Were I work they call it lack of communication or simply: incompetence! Therefore, I give this bank the month of June to fix it or I am out of this mess!!

(Besides: the same lack of communication happened when after an update of the Kobil stick the online access to my account via the Migrosbank website was simply cut off. Asking at the information desk at the bank if I did something wrong, the simple answer was: "No, no, this just does not work anymore. Have a nice day!")

[Stefan Schmid (schms)]

Same problem here on 32bit and 64bit.

VMware:
Linux xxxxx 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux

Host:
Linux xxxx 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux

The following statement from MIGROSBANK is remarkable:

" Ubuntu Linux ab Version 7.04 (i386 Hardware-Architektur) bis 10.03 - Wichtige Informationen für Ubuntu-Version 10.04 "
(http://www.migrosbank.ch/de/MBancNet/MIDentity/Systemanforderungen.htm).

As far as I know, there has never been anything like an Ubuntu 10.03. Hopefully, this statement does not reflect the MIGROSBANK's Linux expertise.

[lugipfupf (lugi-lugipfupf)]

same here... *#@&&!##

[largem (largem)]

i had the same problems with the Kobil M-Identity stick from Valiant Bank. There has been an update and now it works fine with Ubuntu 10.4, 64bit.
I only had to change the mode in "50-udev-default.rules" into "666".
See also :(http://www.valiant.ch/nc/globaldata/holding-navigation/medien-und-aktuell/einzelansicht/medien-und-aktuell/archive/2010/05/article/update-fuer-den-ebanking-login-stick-522.html)
I hope for you that Migrosbank will release a similar update.

[Claude Paroz (paroz)]

An update for the key is announced by MIGROSBANK for July 1st. Hopefully this will resolve this issue.

[GM_Ubuntu (gilles-mulon)]

Hello folks !

Good news : I have upgraded my Kobil M-Identity stick today. It now works on Ubuntu 10.04 :o). Unfortunately a windoz machine is required for the upgrade.

Also, it is still required to change the default udev rule as described in the Faq on the Migros Bank website. However, doing this will grant r/w permissions to any device matching the default rule. I do not like this idea. Call me paranoid if you want ....

Therefore, as already explained in another post, I have created a specific udev rule that matches the Kobil M-Identity stick and set the correct permissions for this device only.

.................................................................................................................................................
BUS!="usb", ACTION!="add", SUBSYSTEM!="usb_device", GOTO="local_rules_end"
# Kobil mIDentity XL USB
ATTRS{idVendor}=="0d46", ATTRS{idProduct}=="4081", MODE="666", GROUP="plugdev"
#
LABEL="local_rules_end"
..................................................................................................................................................

If you want to use it, copy the rule located between the two dotted lines above and paste it into an editor like gedit, for example. Save the file as 01-local.rules, say, in your home directory.

Now open a terminal and type, at the command prompt :

# sudo cp ~/01-local.rules /etc/udev/rules.d/.

Restart udev by typing :

# sudo restart udev

Plug-in your Kobil M-Identity stick. Open the M-Identity folder that shows up on your desktop after a little while. Double-click on the icon Start_M-Identity_Linux. Off you go !

Please note : the above rule works well on my machine. However, I am not an expert at writing udev rules ! So feel free to report issues, improve the rule above, suggest other solutions etc ....

Enjoy Ubuntu !

Cheers.

[Claude Paroz (paroz)]

Confirmed that it works according to the udev instructions above. The update can also be done on a previous version of Ubuntu where the key is working, of course.

[gabriela (salvie)]

I can confirm this, too. Finally! That one took quite a while.

What will happen to this bug entry now? Will someone (who?) mark it as "solved"?

[Claude Paroz (paroz)]

In my opinion, the bug should be resolved when the udev trick will be unnecessary.

[Freddy Kaiser (kaiser-freddy)]

Is it possible to add a generic Rule Set for the Kobil mIDentitys?

Something linke:

/etc/udev/rules.d/51-kobil-udev.rules:

# KOBIL Systems mIDentity 4001
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="0d46",
ATTRS{idProduct}=="4001", ENV{libsane_matched}="yes", MODE="0666"

# KOBIL Systems mIDentity 4081
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="0d46",
ATTRS{idProduct}=="4081", ENV{libsane_matched}="yes", MODE="0666"

# KOBIL Systems mIDentity 4181
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="0d46",
ATTRS{idProduct}=="4181", ENV{libsane_matched}="yes", MODE="0666"

# KOBIL Systems mIDentity 4189
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="0d46",
ATTRS{idProduct}=="4189", ENV{libsane_matched}="yes", MODE="0666"

Would help for all Projects where this Hardware is used.

[Alexander List (alexlist)]

I just had the same problem all over again with Maverick (10.10) x86_64.

I've applied all the udev rules mentioned, but M-Identity isn't mounted at all.

This is getting frustrating, because upcoming Ubuntu release dates are no surprise.

Waiting for a call back from Migros Bank 2nd level support - I'll keep you posted.

[Stefan Schmid (schms)]

@Aleander List

Sadly, I have to confirm your complaint, it's turning into real show-stopper for using Ubuntu (or Linux in general).

At present, I am able to mount and use it like this ( your mileage may vary):

isc-scn@niesen:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.10
DISTRIB_CODENAME=maverick
DISTRIB_DESCRIPTION="Ubuntu 10.10"
isc-scn@niesen:~$ uname -a
Linux niesen 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux
isc-scn@niesen:~$

After connecting the usb stick, I look for a string such as sr1 (in my case) in the output of dmesg
and you use this information to mount and subsequently run ./Start_M-IDentity_Linux.

$ dmesg

(..)

[ 6203.760128] Initializing USB Mass Storage driver...
[ 6205.699687] generic-usb 0003:0D46:4081.0003: hiddev97,hidraw2: USB HID v1.00 Device [KOBIL Systems mIDentity XL] on usb-0000:00:1d.7-2/input1
[ 6205.699873] scsi6 : usb-storage 2-2:1.0
[ 6205.699978] usbcore: registered new interface driver usb-storage
[ 6205.699981] USB Mass Storage support registered.
[ 6206.710122] scsi 6:0:0:0: CD-ROM KOBIL mIDentity 0001 PQ: 0 ANSI: 0
[ 6207.051748] sr1: scsi3-mmc drive: 11x/59x writer cd/rw caddy
[ 6207.051907] sr 6:0:0:0: Attached scsi CD-ROM sr1 <--------- this line
[ 6207.051987] sr 6:0:0:0: Attached scsi generic sg2 type 5
isc-scn@niesen:~$
isc-scn@niesen:~$
isc-scn@niesen:~$ sudo mount /dev/sr1 /mnt
[sudo] password for isc-scn:
mount: block device /dev/sr1 is write-protected, mounting read-only
isc-scn@niesen:~$
isc-scn@niesen:~$
isc-scn@niesen:~$ cd /mnt
isc-scn@niesen:/mnt$ ls
autorun.inf Darwin Start_M-IDentity_Linux Start_M-IDentity_Win.exe
common Linux Start_M-IDentity_Mac.app Win32
isc-scn@niesen:/mnt$ ./Start_M-IDentity_Linux

isc-scn@niesen:/mnt$

[Hans Flipser (verhansa)]

   All bail !
   Customer

Add Bachleors, Bacehlors or Masetrs Dergees to your resume in just 4-6 weeks and open avenues to promotion and better jobs!

This is a rare chance to make a right move and receive your due benefits... if you are qualified but are lacking that piece of paper, Get one from us in a fraction of the time.

Ticket to Success. Get a Promotion. At your Own Pace!.

This is your chance to finally make the right move and receive your due benefits. If you are more than qualified with your experience, but are lacking that prestigious piece of paper known as a diploma that is often the passport to success.

------------------------------------------------------
Give us a call NOW!

+ 1 - 646 - 537 - 1732
Please leave us your:
1) Your Name
2) Your Country
3) Phone No. with countrycode if outside USA

We will get back to you ASAP
------------------------------------------------------

Do Not Reply to this Email.
We do not reply to text inquiries, and our server will reject all response traffic.
We apologize for any inconvenience this may have caused you.

[Ruedi Niederer (ruedi-niederer)]

Hello

It may be that your M-IDentity stick is mounted, but you don't see the icon on the desktop. If you click on "System" and then "Devicemanagement", you may see that the M-IDentity stick is there, but as e.g. /dev/srX where X stands for a number. If you now open a terminal, unmount the stick with "sudo umount /dev/srX" and then mount it with "sudo mount /media/M-IDentity" (you have to create the mountpoint first as describe on the internetpage of migrosbank), then the stick is mounted correctly and the icon is shown on the desktop. When finished, you have to unmount it with "sudo umount /media/M-IDentity", otherwise you get an error message.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Stefan Schmid (schms)]

Hello

After upgrading from Ubuntu 11.04 (64 bit) to Ubuntu 11.10 (64 bit),

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
~$ uname -a
Linux xxxxx 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
~$

the command ./Start_M-IDentity_Linux crashed with the following messages

(..)

root@niesen:/mnt# ./Start_M-IDentity_Linux

(Start_M-IDentity_Linux:5496): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libmurrine.so: wrong ELF class: ELFCLASS64

(Start_M-IDentity_Linux:5496): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libmurrine.so: wrong ELF class: ELFCLASS64

...

(Start_M-IDentity_Linux:5496): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(Start_M-IDentity_Linux:5496): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(Start_M-IDentity_Linux:5496): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
root@niesen:/mnt#

After installing (grudgingly) the following package, it worked again:

apt-get install ia32-libs-gtk

Remark:

Some sources propose to install the following package, however it was already installed:
sudo apt-get install gtk2-engines-pixbuf

[Thierry (tbochud)]

In 12.04, ia32 does not exist anymore. You have to call:

sudo apt-get install libgtk2.0-0:i386

I have not figure how to grant write access yet. Someone?

[Thierry (tbochud)]

Figured it out.

echo 'SUBSYSTEMS=="usb", ATTRS{idVendor}=="0d46", ATTRS{idProduct}=="4081", MODE="0666", ENV{GENERATED}="1"' | sudo tee -a /etc/udev/rules.d/70-persistent-cd.rules
sudo apt-get install libgtk2.0-0:i386 libdbus-glib-1-2:i386

the second library was tricky to find as launching /media/M-IDentity/Start_M-IDentity_Linux was just exiting without any error message.

[Stefan Schmid (schms)]

Hello

New Ubuntu release, problems are back:

# uname -a
Linux eiger 3.8.0-21-generic #32-Ubuntu SMP Tue May 14 22:16:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.04
DISTRIB_CODENAME=raring
DISTRIB_DESCRIPTION="Ubuntu 13.04"

Command ./Start_M-IDentity_Linux starts fine until it launches the firefox webrowser. Firefox window is visible for a split second then the command ./Start_M-IDentity_Linux crashes without any hints on the command line. I suppose that the firefox browser is a 32 bit programm and can not run on 64bit ubuntu 13.04 but this is only a guess.

Installed the following packages but to no avail:
- ia32-libs
- libgtk2.0-0:i386
- libdbus-glib-1-2:i386

Any idea ?

[bibber78 (marco-bibbias)]

Exactly the same problem after upgrading to Ubuntu 13.04.

[dino99 (9d9)]

http://www.freedesktop.org/wiki/Software/hal/

[rsi (rsi-q)]

Tried it on 64bit and 32bit Mint 15. Stick is mounted correctly. When starting "Start_M-Identity_Linux" I can choose the language and the update seems to work. Then it opens the Browser, but after half a second it terminates without an error.

[Edward Oakeley (internet-oakeley)]

I confirm the same as "rsi (rsi-q)". I tried on 32bit and 64bit Ubuntu 13.04 and Mint 15. I installed all the 32bit libraries and the rules. The M-Identity stick mounts correctly, starting the application gives a request for language (so far so good) then it does the quick encryption one-liner and launches the FireFox embedded on the Migros stick. It appears for a moment and then closes. No error logs on standard error if I run it from the command line. Quite annoying. I now have to dual boot my machine with Ubuntu 12.04 to use the Migros e-banking.

[Patrick Valsecchi (patrick-launchpad)]

The problem is that the device is mounted read-only. There used to be a program run by udev to switch it to read-write (I guess), but it has been removed from libccid:
  /usr/sbin/Kobil_mIDentity_switch

The udev rule to run this program is still there, but since the program has been removed, the rule is useless.

I've tried to get it back from an old package version. But it renders the device invisible once I've put back the program.

I've quit investigating after that.

[Agathon (outlandwarrior)]

I have the exact same problem. The browser opens for a second, and then closes without a error post.
I have Mint 15 with mate. Would be cool if someone has a workaround. I dont get it :O

[Claude Paroz (paroz)]

I posted step-by-step instructions in French on a Wiki some time ago: http://www.swisslinux.org/wiki/fr/documentation/midentity
Hope this helps.

[Agathon (outlandwarrior)]

Hello Claude,

I just checked your instructions. I have configured the /etc/udev/rules.d like in the FAQ of the migrosbank. Does it make a difference if I dont have a number in front of the name like you have ? kobil-midentity.rules

I did not find this text-file in my system: /lib/udev/rules.d/91-permissions.rules

I did not run the 32bit libraries, as my system is 32bit Mint 15.
I dondt think it ist something about read/write.
The programm starts, does the update check and then loads the browser. As soon as I see the browser for 1-2 seconds, it closes and the stick is unmounted.
When I start it in the terminal, there are no error posts after the crash.

Linux tehmaster-1000H 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:19:42 UTC 2013 i686 i686 i686 GNU/Linux

Maybe someone has a workaround with Ubuntu v13 ?

Cheers

[Claude Paroz (paroz)]

>I have configured the /etc/udev/rules.d like in the FAQ of the migrosbank. Does it make a difference if I dont have a number in front of the name like you have ? kobil-midentity.rules

rule files are applied in alphabetical order. It means that if you don't put any number in front of the name, the file will be applied after all number-prefixed files, which should be OK in this case.

> I did not find this text-file in my system: /lib/udev/rules.d/91-permissions.rules

Yes, this is dependent on the system (mine is Debian Wheezy).

> When I start it in the terminal, there are no error posts after the crash.

Read the final note of my instructions. Monitor the /tmp directory while you are launching the program. Try to open the created log file just before the crash (yes, it is tricky!).

[Agathon (outlandwarrior)]

Hello Claude,

I did open and safe the folder just after the crash, which is indeed tricky as it autodeletes.
Sadly I did not find any Logfile. Plenty of other stuff though. I dont get it :).

[timi (menthue)]

Hello Claude,

thanks for your hint, a
tail -f -n 30 /tmp/ksff20110607user.log
reveals the log file. There, one can see the error

**
GLib-GObject:ERROR:/build/buildd/glib2.0-2.36.0/./gobject/gobject.c:4127:g_weak_ref_set: assertion failed: (weak_locations != NULL)

The embedded Firefox Browser has certain dependencies and as of ubuntu 13.04 the default version of some of the dependent libraries has introduced incompatibilities.

Workaround - Build and install the required versions of the glib and pango libraries.

Important Note: It's highly recommend that these are NOT installed in the default location, as this could might cause general instabilities!

Get glib and pango source packages, and unpack them to a temporary directory.
http://ftp.gnome.org/pub/gnome/sources/glib/2.32/glib-2.32.3.tar.xz
http://ftp.gnome.org/pub/gnome/sources/pango/1.30/pango-1.30.0.tar.xz

Install the required build dependencies:
sudo apt-get build-dep glib2.0
sudo apt-get build-dep pango1.0

Configure, make and install glib:
cd glib-2.32.3
./autogen.sh --prefix=<INSTALL LOCATION>
make && make install

Configure, make and install pango:
cd pango-1.30.0
./configure --prefix=<INSTALL LOCATION> --enable-introspection=no
make && make install

ensure the following two environment variables are updated:
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:<INSTALL LOCATION>/lib/pkgconfig
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<INSTALL LOCATION>/lib
finally start mbancnet:
/media/user/M-IDentity/Start_M-IDentity_Linux

[Stefan Schmid (schms)]

Hi timi

Thanks a lot for the instructions. They worked just fine.
However, the firefox startet by /media/user/M-IDentity/Start_M-IDentity_Linux still crashes after a few seconds.
I checked the env variables PKG_CONFIG_PATH and LD_LIBRARY_PATH several times. They seem to be fine.
The log file in /tmp still shows

(..)
GLib-GObject:ERROR:/build/buildd/glib2.0-2.36.0/./gobject/gobject.c:4127:g_weak_ref_set: assertion failed: (weak_locations != NULL)
(..)

and a lot of errors of this type

ERROR: ld.so: object '/media/user/M-IDentity//Linux/lib/libplh.so' from LD_PRELOAD cannot be preloaded: ignored.

The latter has always been there since the problem arose (at least 13.04, I thought it started already with 12.10). I have been looking into this matter for months by now :-(

The file libplh.so exists but it is a 32-bit library and the system is 64-bit. All known 32-bit support libraries have
been installed.

stefan@xxxx:/media/user/M-IDentity/Linux/lib$ file libplh.so
libplh.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped
stefan@xxxx:/media/user/M-IDentity/Linux/lib$

At present I work with
stefan@xxxx:/$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.04
DISTRIB_CODENAME=raring
DISTRIB_DESCRIPTION="Ubuntu 13.04"
stefan@xxxx:/$
stefan@xxx:/$ uname -a
Linux xxxx 3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 20:03:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
stefan@xxxx:/$

[timi (menthue)]

Hello Stefan,

You're right, the workaround above works only on 32-bit Ubuntu.

With glib-2.32.3 and pango-1.30.0 on a 64-bit Ubuntu, I get this error when starting mbancnet:

/usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0: undefined symbol: g_object_replace_qdata

With glib-2.34.0 (https://developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.html#g-object-replace-qdata), I get

GLib-GObject:ERROR:gobject.c:4141:g_weak_ref_set: assertion failed: (weak_locations != NULL)

again :(

In your log file, it looks like mbancnet crashes on system glib (2.36), the variables must be exported in the terminal where you run Start_M-IDentity_Linux.

[timi (menthue)]

As a simple workaround on 64-bit Ubuntu Raring, you can build glib and pango on 32-bit Raring, copy <INSTALL LOCATION> folder to same location on 64-bit machine, and use a bash script to start mbancnet:

#!/usr/bin/env bash

export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:<INSTALL LOCATION>/lib/pkgconfig
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<INSTALL LOCATION>/lib
/media/user/M-IDentity/Start_M-IDentity_Linux

[Stefan Schmid (schms)]

Hello timi

This is to confirm that your proposal given in #43 worked very well ! M-IDentity is finally up and running again on

Ubuntu, 13.10
Linux xxxx 3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 20:03:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I thank you very much for your help. Just great !

[timi (menthue)]

Another solution on 64-bit raring/saucy:

Set up a 32-bit raring/saucy chroot environment on 64-bit raring/saucy. There's a german tutorial on http://wiki.ubuntuusers.de/schroot (32-Bit-Programme in einer 64-Bit-Installation verwenden). schroot rebinds /home directory on the host system by default so that it appears in the chroot system.

Enter the chroot environment, set up a sources.list file. Install pango and glib in the chroot as described above, use a folder inside your /home directory as <INSTALL LOCATION>, e.g. ~/mbancnet

Exit chroot environment.

Open terminal, plug in M-Identity stick and start mbancnet with same bash script as above.

Future updates of dependent libraries might break the dynamic linking again, in such a case enter chroot environment, and rebuild pango and glib.

[steff (stefan-neupert-gmail)]

Another solution on non-LTS 64bit

It seems Migros-Bank and Kobil relies on LTS versions.

My favourite solution is: virtualbox.

1. Make sure, dkms is installed
2. Install virtualbox (also availabe directly from the virtual-box site)
3. Make shure you're member of the 'vboxusers'-group (/etc/group)
4. Setup a new virtual-box instance and install Ubuntu 12.04 LTS
5. Install the guest-additions (available from the virtualbox-site)
6. Setup your instance and choose 'usb' to add the usb-filter
6. You might want to install the VBoxLinuxAdditions.iso (from ubuntu) for full display
7. Adjust the rules file for udev (see posts above)
8. Start the virtual-box instance und activate the usb-stick (as konfigured above)

This works perfect for me and doesn't taint the Ubuntu-installation...

[Brian (c-launchpad-net)]

VirtualBox solution worked for me.
Host machine: ThinkPad X220
Host OS: Customized (Corporate managed) Ubuntu 14, 64 bit
Guest OS: Ubuntu 14, 32 bit.

I encountered some problems trying to get it to work. The biggest issue was the screen size was 640x480 and the VirtualBox Guest Additions were not installing correctly. Things to remember:

1) Once the guest OS is installed, remember to apt-get update/apt-get upgrade immediately.

2) Be sure to add your user to vboxusers group (gpasswd -a $USER vboxusers). If you don't restart, remember to enter this group before running virtualbox (newgrp vboxusers)

3) Make the desired udev changes on both host and guest systems. Remember to restart udev (service udev restart) on both.

It seems there are multiple ways to install the virtualbox guest additions, a) via apt on the guest and b) using the virtualbox menu item "Devices > Install Guest Additions CD Image...". Only (b) worked for me due to issues with x window system version incompatibility.