Samsung Xcover 271 B2710 mass storage does not mount automatically
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| usb-modeswitch (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1. In the interface of the Samsung Xcover 271 B2710, set it to connect as mass storage.
2. Connect it to the computer via USB cabel.
Notice that it does not mount automatically. Also it does mount automatically when instead of step 1 it is set to connect to Samsung Kies or to sync with a media player.
Below I provide output from dmesg and lsusb -vv.
Output from dmesg as it is connected (step 2):
[101332.680133] usb 2-6: new high speed USB device using ehci_hcd and address 6
[101333.630726] Initializing USB Mass Storage driver...
[101333.630861] scsi5 : usb-storage 2-6:1.0
[101333.630956] usbcore: registered new interface driver usb-storage
[101333.630958] USB Mass Storage support registered.
Output from lsusb -vv:
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 006 Device 002: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d Logitech, Inc.
idProduct 0xc01b MX310 Optical Mouse
bcdDevice 18.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
HID Device Descriptor:
bLength 9
bcdHID 1.10
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 10
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 005 Device 003: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d Logitech, Inc.
idProduct 0xc30e UltraX Keyboard (Y-BL49)
bcdDevice 1.80
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
HID Device Descriptor:
bLength 9
bcdHID 1.10
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 10
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
HID Device Descriptor:
bLength 9
bcdHID 1.10
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 10
cannot read device status, Operation not permitted (1)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 002 Device 006: ID 04e8:f000 Samsung Electronics Co., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x04e8 Samsung Electronics Co., Ltd
idProduct 0xf000
bcdDevice 0.00
iManufacturer 3
iProduct 2
iSerial 4
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurat
iConfiguration 1
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 2
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 12
can't get hub descriptor: Operation not permitted
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 12
can't get hub descriptor: Operation not permitted
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-28-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] Filen eller katalogen finns inte
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe4804000 irq 47'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,
Controls : 11
Simple ctrls : 9
Date: Sat Apr 9 10:31:37 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Hewlett-Packard HP Compaq 6710b (GR680ET#AK8)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=
LANG=sv_SE.UTF-8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
dmi.bios.date: 08/09/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.16
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq 6710b (GR680ET#AK8)
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Sleft (sleft) wrote : | #1 |
description: | updated |
description: | updated |
description: | updated |
summary: |
- Samsung X Cover 271 B2710 mass storage does not mount automatically + Samsung Xcover 271 B2710 mass storage does not mount automatically |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Sleft (sleft) wrote : | #2 |
This is a problem with the usb-modeswitch, if you disable it in /etc/usb_
Andrew Simpson (andrew-simpson) wrote : | #4 |
Confirming the fix by Michael B also works with a Samsung S5510.
The problem is with usb_mode_switch and the associated udev rules in /lib/udev.
# Samsung U209
#ATTRS{
These lines do not represent a unique product; the Samsung Xcover 271 B2710 and Samsung S5510 (and others??) also match this line (lsusb gives 04e8:f000).
Commenting out this line fixes the problem on the Samsung 5S5510, and I would guess the Xcover 271 B2710 too.
affects: | linux (Ubuntu) → usb-modeswitch (Ubuntu) |
Josua Dietze (digidietze) wrote : | #5 |
The instant "fix" is O.K.
For a proper solution I need the "lsusb -v" output of the U209.
usb_modeswitch can check attributes of a device (USB or SCSI) to identify specific models even if the USB IDs are identical. See the notorious "05c6:1000" ID ...
I'll try to reach the original contributor of the U209 information.
Josua Dietze (digidietze) wrote : | #6 |
No reply from the original contributor, but I finally found this usb_modeswitch output via Google, after several fruitless attempts:
Received inquiry data (detailed identification)
-------
Vendor String: SAMSUNG
Product String: SCH-U209 Install
Revision String: 2.31
-------
Device description data (identification)
-------
Manufacturer: SAMSUNG Electronics Co.,Ltd.
Product: USB MMC Storage
Serial No.: 000000000002
-------
The page is here, see post #14:
http://
I consider this information correct; this enables us to identify the modem apart from the phones.
I think I can assume that the USB ID strings are not specific to the modem, so the SCSI strings need to be used.
The file "/usr/share/
"/usr/share/
Can anyone test that fix?
Thanks!
Josua Dietze (digidietze) wrote : | #7 |
Addendum:
Due to the way usb_modeswitch works, the udev rules line WILL match with all devices using the Samsung ID, but the dispatcher mechanism will NOT start the switching process except for the U209 modem. It will just exit.
So commenting out the udev rule can not be considered a general fix.
Andrew Simpson (andrew-simpson) wrote : | #8 |
Comment #6: Works for me with Samsung GT-S5510T.
The file at "/usr/share/
[ 6917.232046] usb 1-9: new high speed USB device using ehci_hcd and address 3
[ 6917.432759] cdc_acm 1-9:1.0: ttyACM0: USB ACM device
[ 6917.435607] usbcore: registered new interface driver cdc_acm
[ 6917.435615] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[ 6961.538549] usb 1-9: USB disconnect, address 3
[ 6961.904051] usb 1-9: new high speed USB device using ehci_hcd and address 4
[ 6962.091062] usbcore: registered new interface driver uas
[ 6962.122318] Initializing USB Mass Storage driver...
[ 6962.122516] scsi6 : usb-storage 1-9:1.0
[ 6962.124644] usbcore: registered new interface driver usb-storage
[ 6962.124651] USB Mass Storage support registered.
[ 6963.130812] scsi 6:0:0:0: Direct-Access Samsung GT-S5510T 2.31 PQ: 0 ANSI: 2
[ 6963.137871] sd 6:0:0:0: Attached scsi generic sg3 type 0
[ 6963.139923] sd 6:0:0:0: [sdc] 3854336 512-byte logical blocks: (1.97 GB/1.83 GiB)
[ 6963.141679] sd 6:0:0:0: [sdc] Write Protect is off
[ 6963.141688] sd 6:0:0:0: [sdc] Mode Sense: 0f 0e 00 00
[ 6963.141693] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 6963.144672] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 6963.148547] sdc: sdc1
[ 6963.151654] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 6963.151663] sd 6:0:0:0: [sdc] Attached SCSI removable disk
Changed in usb-modeswitch (Ubuntu): | |
status: | Confirmed → Fix Committed |
Didier Raboud (odyx) wrote : | #9 |
This was fixed in usb-modeswitch upstream update 20111023, available in Ubuntu Precise. It affects all previous Ubuntu releases though.
Changed in usb-modeswitch (Ubuntu): | |
status: | Fix Committed → Fix Released |
ptah (brett-h-l) wrote : | #10 |
Samsung 2710 does not connect in U-12.04. Reverted to /etc/usb_
Josua Dietze (digidietze) wrote : | #11 |
Please be a little bit more specific. Why do you conclude that usb_modeswitch is responsible for the connection problems?
Mind that the orignal bug was about the mass storage mode of the phone, not about connecting issues.
Also, the committed fix will prevent *any* mode-switching action for this phone. Disabling usb_modeswitch will change nothing.
sko (sebastianus13) wrote : | #12 |
I can confirm that the fix in ubuntu 12.04 does not fix the connection problems of
a Samsung B2710 mobile phone. The phone is recognized by the kernel but does not show
up as a usable device (the device file will not be created). (USB mass storage mode)
After setting "DisableSwitchi
as expected.
For reference:
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 003 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Bus 002 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 001 Device 009: ID 04e8:f000 Samsung Electronics Co., Ltd
# tar tzvf /usr/share/
-rw-rw-r-- root/root 166 2011-11-10 23:42 04e8:689a
-rw-rw-r-- root/root 142 2011-11-10 23:42 04e8:f000:sMo=U209
Josua Dietze (digidietze) wrote : | #13 |
Please create a usb_modeswitch log file by editing /etc/usb_
Andrew Simpson (andrew-simpson) wrote : | #14 |
Regarding comment #8. Can now confirm that usb_modeswitch is not working with Kubuntu 12.04. Changing the config file to 'DisableSwitchi
Have enabled debugging (EnableLogging=1) and collected debugging information with 'DisableSwitchi
ikletti (ikletti) wrote : | #15 |
I can confirm that this problem still exists with Kubuntu 14.04 and a Samsung B2710.
Using the fix from comment #3 works.
Josua Dietze (digidietze) wrote : | #16 |
The problem is obvious in the log from #14:
Warning: SCSI attribute "vendor" not readable.
Warning: SCSI attribute "model" not readable.
Warning: SCSI attribute "rev" not readable.
The filter "sMo=U209" which should prevent usb_modeswitch from doing anything in this case does not work - because the SCSI identification fails.
The problem is in the dispatcher part of the Ubuntu fork of usb_modeswitch.
ikletti, can you check out these SCSI attributes in the /sys tree when your phone is plugged in?
You'll find it under
/sys/bus/
Andrew Simpson (andrew-simpson) wrote : | #18 |
This is with the same phone from #14
$ cd /sys/bus/
$ cat vendor
Samsung
$ cat model
GT-S5510T
$ cat rev
2.31
I couldn't find directory 'usb-storage' in /sys/usb/drivers unless I did 'DisableSwitchi
Josua Dietze (digidietze) wrote : | #19 |
Yes, it's correct to disable mode-switching when checking out the SCSI attributes. This is what usb_modeswitch sees when a phone/modem is plugged in. Then it has to determine if any action is required.
Bottom line:
The dispatcher part of the usb_modeswitch Ubuntu fork has trouble reading the SCSI attributes, which are however present and readable.
I have not seen problems like this with the original (upstream) package which is also used on Debian.
Ubuntu Developers?
Josua Dietze (digidietze) wrote : | #20 |
Hint:
It may well be that there is a timing problem if the dispatcher tries to read the values when the storage driver has not completed the initialization of the storage interface.
udippel (udippel) wrote : | #21 |
Only as an update: As of today, it still doesn't work out of the box.
The workaround fixes it.
Allow me a bit of comment that sounds sarcastic, and yet bugs me as an oldtimer with 20 years on Linux: I always advocate FOSS. Should someone hit this snag, how can I honestly defend this shortcoming? Asking Aunt Tilly to search Google and end with her using the CL to vi a parameter in a file?
Could I blame her on going back to the monopolist?
I would defend my beloved Linux, were she the first to encounter this. Alas, it has been around for > 5 years.
And I am afraid, not only this particular mobile phone will simply not work as mass storage.
Josua Dietze (digidietze) wrote : | #22 |
udippel, instead of ranting generally you could just use Debian instead of Ubuntu. It's likely that you would not run into this bug.
This bug is still active in Natty.