[Bug 513529] Re: karmic to lucid upgrade: virtualbox modules fail to built and cause upgrade to fail

2010-05-03 Thread Jan Gutter
Wow, and I had such high hopes for my first upgrade (Karmic->Lucid)!

It seems the Ubuntu developers are not really interested in fixing this
problem, or the many other open bugs. The workaround obviously appears
to uninstall virtualbox before upgrading, yet nobody seemed to mention
it on the Lucid upgrade site...

Ah well.

-- 
karmic to lucid upgrade: virtualbox modules fail to built and cause upgrade to 
fail
https://bugs.launchpad.net/bugs/513529
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 228850] Re: firefox wpad.dat report incorrect myIpAddress()

2010-05-06 Thread Jan Gutter
This bug still affects Lucid Lynx.

I presume the Ubuntu developers are not even interested in passing the
bug (or buck) upstream?

-- 
firefox wpad.dat report incorrect myIpAddress()
https://bugs.launchpad.net/bugs/228850
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 444612] Re: WACf008 (and maybe other) tablets supports higher baud rate

2009-10-06 Thread Jan Gutter
Here's the .diff between the original .fdi and my .fdi file.

** Attachment added: "The differences between the old .fdi and new .fdi file."
   
http://launchpadlibrarian.net/33126113/xserver-xorg-input-wacom-highspeed.patch

-- 
WACf008 (and maybe other) tablets supports higher baud rate
https://bugs.launchpad.net/bugs/444612
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 444612] [NEW] WACf008 (and maybe other) tablets supports higher baud rate

2009-10-06 Thread Jan Gutter
Public bug reported:

Binary package hint: wacom-tools

I'm running Karmic Beta (64-bit) on a Lenovo Thinkpad X200 Tablet.
Currently the tablet autodetects the baudrate at 9600. This causes
perceptible input lag. I've found that if I increase the baud rate to
38400, it improves the experience a lot!

This value is set in: 
/usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi
which is part of the: 
xserver-xorg-input-wacom_1%3a0.8.4.1-0ubuntu1_amd64.deb 
binary package.

I've created an updated version that sets the WACf008 tablet to this
speed, and I'll be attaching the diff shortly.

Offtopic: I'm incredibly impressed with the polish and usability of
Karmic thus far, keep up the good work!

** Affects: wacom-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
WACf008 (and maybe other) tablets supports higher baud rate
https://bugs.launchpad.net/bugs/444612
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 444612] Re: WACf008 (and maybe other) tablets supports higher baud rate

2009-10-06 Thread Jan Gutter

** Attachment added: "The modified .fdi file to make WACf008 default to 38400"
   http://launchpadlibrarian.net/33126053/10-linuxwacom.fdi

-- 
WACf008 (and maybe other) tablets supports higher baud rate
https://bugs.launchpad.net/bugs/444612
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 451304] [NEW] Partition type 0x12 could be hidden

2009-10-14 Thread Jan Gutter
Public bug reported:

Binary package hint: devicekit-disks

/lib/udev/rules.d/95-devkit-disks.rules contains rules to hide system
recovery partitions and such: here's an excerpt:

# special MBR partition types (EFI, hidden, etc.)
# see http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
ENV{DKD_PARTITION_SCHEME}=="mbr", \
  
ENV{DKD_PARTITION_TYPE}=="0x00|0x11|0x14|0x16|0x17|0x1b|0x1c|0x1e|0x27|0x3d|0x84|0x8d|0x90|0x91|0x92|0x93|0x97|0x98|0x9a|0x9b|0xbb|0xc2|0xc3|0xdd|0xef",
 \
  ENV{DKD_PRESENTATION_HIDE}="1"

According to the web site listed, partition type 0x12 (Compaq
diagnostics) is also used by Thinkpads for the recovery partition. I can
confirm this, at least on my Lenovo X200 Tablet. Adding 0x12 to the
hidden partition types would hide the recovery partition by default,
which I consider to be a bonus: a technically minded user can always
unhide the partition if they need access to it. As I've already hidden
mine with a custom rule, I don't mind either way.

The main reason why my recovery partition wasn't hidden using other
rules, was because it does not have a label.

Thanks for the hard work guys, it really shows!

** Affects: devicekit-disks (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Partition type 0x12 could be hidden
https://bugs.launchpad.net/bugs/451304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1768526] Re: Include nfp driver in linux-modules

2018-05-02 Thread Jan Gutter
The code impact is likely adding the line:

drivers/net/ethernet/netronome/*

to

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/debian.master/control.d/generic
.inclusion-list

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768526

Title:
  Include nfp driver in linux-modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768526/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768526] Re: Include nfp driver in linux-modules

2018-05-03 Thread Jan Gutter
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768526

Title:
  Include nfp driver in linux-modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768526/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768526] Re: Include nfp driver in linux-modules

2018-05-26 Thread Jan Gutter
Thanks! I've created a custom cloud-image using the following method,
and verified that the proposed package has indeed moved the module out
of -extras into the main package.


curl 
'http://cloud-images.ubuntu.com/daily/server/bionic/current/bionic-server-cloudimg-amd64.img'
 -O

cat >bionic-proposed 

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-09-29 Thread Jan Gutter
A simple one-line patch seems to solve the issue for me:

Index: iproute2-4.3.0/lib/libnetlink.c
===
--- iproute2-4.3.0.orig/lib/libnetlink.c
+++ iproute2-4.3.0/lib/libnetlink.c
@@ -202,7 +202,7 @@ int rtnl_dump_filter_l(struct rtnl_handl
.msg_iov = &iov,
.msg_iovlen = 1,
};
-   char buf[16384];
+   char buf[65536];
int dump_intr = 0;

iov.iov_base = buf;

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-10 Thread Jan Gutter
I'm unfamiliar with where to submit the fix for this bug. Am I
submitting the fix to the wrong forum?

** Patch added: "[PATCH] Fix "Message truncated" issue with many VF's"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4966551/+files/iproute2-fix-netlink-overflow.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-10 Thread Jan Gutter
This fix has been pulled into CentOS 7.3 and later

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-10 Thread Jan Gutter
This bug has already been fixed upstream in the following commit:

https://anonscm.debian.org/git/collab-maint/pkg-
iproute.git/commit/?id=72b365e8e0fd5efe1d5c05d04c25950736635cfb


This commit happened between: tags debian/4.3.0-1 and debian/4.6.0-1

** Bug watch added: Red Hat Bugzilla #1380803
   https://bugzilla.redhat.com/show_bug.cgi?id=1380803

** Also affects: iproute2 (CentOS) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1380803
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-11-01 Thread Jan Gutter
@arges

Hi, would you need any more testing from us?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-26 Thread Jan Gutter
I tested on Trusty: iproute2_3.12.0-2ubuntu1.1_amd64.deb fixed the bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-26 Thread Jan Gutter
** Tags removed: verification-needed
** Tags added: verification-done

** Tags removed: verification-needed-trusty verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-26 Thread Jan Gutter
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-12 Thread Jan Gutter
Yes, I've confirmed it's fixed there.

I build it from the .dsc, and didn't see "Message truncated".

Then, just to make sure, I reverted the patch (changing the buf size to
16384) and the bug was back.

So at least there's been some use in real world of the patch, I hope...

What's the path of least resistance here? Backporting to iproute2's
stable branch, or applying the patch downstream at Ubuntu?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-17 Thread Jan Gutter
@nacc I built from source to verify that the one-liner is directly
responsible for fixing and breaking the issue (inherent paranoia). I did
test with the binaries and they worked.

Apologies, I'm unfamiliar with the Ubuntu SRU process as you can
probably see. What exactly is an "MP" and how would one go about to
propose one?

I'm aware of the need of testing bugfixes like these, I'm not familiar
with your release pipeline, however.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-19 Thread Jan Gutter
@nacc

Thanks so much for the explanation. I also found
https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Merge_Proposals_and_Reviewing
that details a bit more of the internal processes. As relative outsiders
to the Ubuntu process, I'd appreciate it very much if you could handle
that part for Monique's patches. I can be on hand to answer technical
questions if required.

Regarding the buffer size choice, it's very arbitrary as Phil said. I'm
pretty sure we came to the same conclusion independently (libvirt and
libnl had very similar issues) and the workaround is obvious. 32k seems
to work for 64 VF's (our test case), but breaks with 128 VF's. Not a lot
of machines can handle 128 concurrent VF's. I typed 64k "just because".
libvirt+libnl allow message peeking. However, iproute2 uses netlink
directly. So, implementing a similar idea would require an entirely new
receive codepath with all the fun of finding out where new exception
paths occur: something to be done on tip and not suitable for backport
without thorough vetting.

I'm sure it'll save a lot of time once the kinks have been worked out of
the automation, backports are quite the double-edged sword.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-20 Thread Jan Gutter
I concur with option 2), unnecessary deviation will just cause
confusion.

Regarding the other buffer sizes, the last time I looked they were
mostly OK. The issue reared its head in this particular case because the
netlink message that previously had a pretty constant per-netdev
response size suddenly had the ability to balloon with "no warning". A
number of workarounds exist (i.e. you have to explicitly ask for the VF
info), but, in this case we actually want the VF info and iproute2 was
just unprepared for the size of it.

I guess the core issue is that it's entirely possible for the kernel to
add extra netlink attributes to any query response, iproute2 makes the
assumption that the queries it's making is not necessarily going to
explode with gigabytes of new annotations and 16k will easily fit any
current real-world system. A pragmatic approach would probably be to
handle the "Message Truncated" path with a dynamically sized buffer as
an exceptional case.

Any fix in iproute2 that "properly" addresses this issue has to be
carefully vetted. Who knows how many inherent races will get exposed if
the ip command doubles in execution time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-20 Thread Jan Gutter
I had a look at the two proposals and could not spot any obvious
mistakes:

- the correct upstream git commit has been cherry-picked
- I don't have any objections to attribution or log messages

Thanks again for shepherding this one through!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails

2012-05-09 Thread Jan Gutter
Asking again: is anyone from Ubuntu looking at this issue at all?

Unfortunately there's rather a complex interplay of subsystems here: It
seems the top end is Nautilus, and the bottom end might be libmtp. In
the middle GVFS, GIO, FUSE and all sorts of stuff might lurk.

If only some expert that knew how bits and pieces of a Linux
distribution were monitoring this thread!

Anyway, on the libmtp site, there's this nice email exchange:
http://sourceforge.net/mailarchive/forum.php?thread_name=CAKnu2Mrp4s6hTXr%3DNp1VYN9sFmWbb6NV2GeTawSm2rsSu002GA%40mail.gmail.com&forum_name=libmtp-discuss

It seems that the original MTP spec transferred everything in one go.
The uncached extension apparently allows devices to transfer portions of
the tree, if I'm reading the exchange correctly. There's also a link in
there to a different project called go-mtpfs (https://github.com/hanwen
/go-mtpfs). I haven't tried it yet, but it might hold promise.

Reading the last portion of the README is really enlightening.
http://libmtp.git.sourceforge.net/git/gitweb.cgi?p=libmtp/libmtp;a=blob;f=README;hb=HEAD
MTP was really not designed to work like a file system. I presume the
confusion sets in because the UI conflates the object handling metaphor
with the file handling metaphor under Windows.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972311

Title:
  Accessing a MTP device like the Galaxy Nexus fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/972311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails

2012-05-09 Thread Jan Gutter
mtpfs, go-mtpfs, gmtp, mtp-detect and nautilus (gvfs, or gio, or
whatever) all use the same libmtp library. It seems that the common way
to query MTP devices used to be "pull a list of all objects", "push and
pull individual objects". A lot of old, legacy devices actually seem to
*expect* that kind of behaviour.

When Google decided upon MTP, they obviously just tested with Windows.
(The OSX people also tend to mumble and growl about the transfer speed).
I have no idea how the Windows MTP stack works: on Windows XP you have
to install Windows Media Player, but later versions seem to have it
built-in. The rationale being that you don't want people to install
third-party stuff, so you stick with whatever crap protocol Microsoft
designed. MTP is NOT made for generic file transfer, it's made for
"media" transfer (i.e. videos, music and pictures).

It's entirely plausible that Microsoft's MTP stack does a per-device
check (or uses massive USB id databases) to see whether the devices are
"old" or "new" style, and works accordingly. Also Microsoft's MTP stack
runs a single service that connects and speaks to the MTP devices, so
the way libmtp speaks to the devices is by nature completely different.

So, it looks like the two styles (incremental fetching of objects, and
full listing) seems to be slightly incompatible. libmtp supports both,
but the application using it (go-mtpfs and mtpfs) use entirely different
parts of the API, it seems.

So, either we need to find out where the code that uses libmtp in
Nautilus is built, use *shudder* go (I feel like installing .NET!) or
fix mtpfs to use a different style of access. I guess, waiting 10
minutes using gmtp is also an option.

Seems like the Ubuntu people are still MIA?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972311

Title:
  Accessing a MTP device like the Galaxy Nexus fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/972311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails

2012-05-09 Thread Jan Gutter
Sorry, I meant Canonical people. I forgot that Ubuntu is supposedly a
"community distribution", except when it's not :-p

Where's "upstream"? Is there a bug tracker for the gvfs people anywhere?
Please understand, the reason this is a confusing issue is that it's not
immediately apparent from any system feedback where the issue lies:
Nautilus pops up on connecting your device, giving a cryptic error from
DBUS with very little help.

Like any non-trivial system where only a small fraction is visible, we
must rely on experts to point us in the right direction. I understand
it's a low priority for Canonical to fix this: maybe changing the error
message to "Device not supported" might be more helpful?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972311

Title:
  Accessing a MTP device like the Galaxy Nexus fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/972311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails

2012-05-03 Thread Jan Gutter
Which update was that? I'm up to date and it's still broken. The only
updates I got that might be relevant was for glib (and libtasn1), and
neither fixed the issue.

I've tried using Cinnamon, GNOME fallback and Unity, and now it seems
like hit-or-miss that MTP even gets recognized. If that happens, I only
get the silly button at the top that says I could use Rythmbox to manage
my music device and the timeout message after a lng while.

Way to go bringing enterprise-class polish to the user interface, guys!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972311

Title:
  Accessing a MTP device like the Galaxy Nexus fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/972311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails

2012-05-03 Thread Jan Gutter
I've tried something different:

http://ohheyitslou.blogspot.com/2011/12/galaxy-nexus-enable-mtp-file-
transfer.html

Precise is up-to-date with the latest stable libmtp. BUT, it seems that
mtpfs pulls down the entire tree from the phone before allowing access
to the FS. If this is because libmtp operates that way, it might explain
why there's a timeout in the GUI version: for anything but a basically
empty phone, it's going to time out.

A quick way of accessing at least *some* part of the phone's FS is to
run the mount command like 'mtpfs -o allow_other /mnt/tmp/', wait a
while, switch the phone to PTP, then back to MTP. You should be able to
see the portion of the tree that downloaded.

I checked how long it takes for the full tree to transfer, and it seems
to be about 6.5 minutes.

Is anybody from Ubuntu dealing with this, or should try our luck with
the libmtp guys?

And yeah, it does seem that the frustration is affecting me in
mysterious ways :-p

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972311

Title:
  Accessing a MTP device like the Galaxy Nexus fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/972311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 630748] Re: iwlagn degrades quickly during normal wifi session

2012-05-05 Thread Jan Gutter
Gotta love the enterprise polish Ubuntu brings to Linux!

At http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2214 it seems
that the bug has been fixed lately (for some people at least) by the
guys at Intel. As with the severe power usage regression, Ubuntu seems
to be unable or unwilling to do anything except package other people's
software when the problem is anything except a marketing issue...

Since the bug has been marked as fixed (by the equivalent of disabling
the high-end features of the device), I doubt we'll see any real
resolution. Oh well...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/630748

Title:
  iwlagn degrades quickly during normal wifi session

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/630748/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 927828] Re: sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed.

2012-05-05 Thread Jan Gutter
If you don't want to enable the "proposed" repository, here's a quick
way to install the fixed sudo:

sudo -i  # < this helps work around the bug in the current version of sudo
wget -c -t 0 
'https://launchpad.net/ubuntu/+source/sudo/1.8.3p1-1ubuntu3.1/+build/3453511/+files/sudo_1.8.3p1-1ubuntu3.1_amd64.deb'
dpkg -i sudo_1.8.3p1-1ubuntu3.1_amd64.deb

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828

Title:
  sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
  *)0)' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/927828/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails

2012-05-01 Thread Jan Gutter
*sigh* It's what I've come to expect from Ubuntu: remember, Shuttleworth
says it's better to have users than a stable product!

As a workaround, you can set the Galaxy Nexus to use PTP. (Drag down on
the notifications bar, and click the "Connected as media device/Touch
for other USB options" notification.) On previous versions of Ubuntu, it
gave access to many more directories than it does now, but at least if
you install a file manager, you should be able to copy files to the
directories you can see. Keep in mind that it's slow, buggy as heck, and
the protocol is really crap. Basically only use it to upload or download
files: do NOT do file management!

Don't expect this to be fixed for 12.04 though. I seriously doubt that
there are any actual developers on Canonical's staff: most are marketing
drones.

Also, Google really should have reached out to major distros that MTP is
the future much, MUCH earlier. (They had planned this from early 2011 at
least.) Maybe then a decent distro could have picked up the support and
Canonical would have got the code that way.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972311

Title:
  Accessing a MTP device like the Galaxy Nexus fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/972311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 903422] Re: Mount / Provide access to Android 4 (Ice Cream Sandwich, ICS) MTP devices

2012-08-17 Thread Jan Gutter
Hi,

Have you tried using jmtpfs?

http://research.jacquette.com/jmtpfs-exchanging-files-between-android-
devices-and-linux/

It's working for me on my Galaxy Nexus (JB and ICS), and I've also had
luck with it with a Galaxy S3 (ICS). (I'm using 12.04 with the latest
libmtp)

Unfortunately mtp is still really slow: keep in mind it was never really
designed to scale, and mapping it on to a filesystem will always be
imperfect.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903422

Title:
  Mount / Provide access to Android 4 (Ice Cream Sandwich, ICS) MTP
  devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/903422/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 986722] Re: Can't browse MTP device (Galaxy Nexus)

2012-08-19 Thread Jan Gutter
Hi, I recently posted this in bug 903422:

Have you tried using jmtpfs?

http://research.jacquette.com/jmtpfs-exchanging-files-between-android-
devices-and-linux/

It's working for me on my Galaxy Nexus (JB and ICS), and I've also had
luck with it with a Galaxy S3 (ICS). (I'm using 12.04 with the latest
libmtp)

Unfortunately mtp is still really slow: keep in mind it was never really
designed to scale, and mapping it on to a filesystem will always be
imperfect.

The long and the short of it, it seems the bug is NOT in libmtp (since
jmtpfs also uses libmtp). gmtp and gvfsd uses a much older method to
access mtp devices which involves downloading the entire directory
structure beforehand. Turns out that this can take a long time (mtp
is *SLOW*) which causes timeouts and very unhelpful error messages in
the rest of the system.

Google put everyone slightly between a rock and a hard place here. The options 
are:
1) Support old-style (Microsoft) devices and fail horribly on new-style 
(Android). (Do nothing)
2) Break backward compatibility (HEAVEN FORBID!)
3) Emulate what Windows does. Since they seemed to design it for Windows in the 
first place...

I have a private bet with myself what the eventual solution is going to
be. I hope I'm wrong.

Jan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986722

Title:
  Can't browse MTP device (Galaxy Nexus)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/986722/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs