Aug 31 2017
Aug 10 2017
Nov 8 2016
Ah, debian packages worked. I had to reboot though.
Oct 11 2016
Fixed in Tanglu 4.0 (Dasyatis kuhlii)
Oct 9 2016
Oct 6 2016
Oct 1 2016
I can not reproduce this issue anymore. The libautodie-perl library has been backported to regular chromodoris updates for a while, and the issue doesn't seem to happen with the perl-base version.
So, I think this problem is resolved.
If you can test it though, that would be awesome, to get another independent conformation.
If the bug still persists, feel free to reopen!
Thank you very much for investigating this! :-)
Aug 23 2016
Ah ha! It's most likely a bug in google chrome. I reported it to google, but I guess we can close this bug.
I opened a dbus bug report here, https://bugs.freedesktop.org/show_bug.cgi?id=97439
Aug 22 2016
Similar bug report here, https://bugs.kde.org/show_bug.cgi?id=261180
Jul 31 2016
Jul 30 2016
Jul 23 2016
Oh, I see why this is high priority. I tried installing on another computer and declined usrmerge and everything broke. Various scripts now look for /usr/bin/mount instead of /bin/mount. So usrmerge really isn't optional.
Jul 22 2016
I don't understand why this is high priority. Just remove it from the install process. Nobody will care. You can try again in tanglu5.
Jul 20 2016
In case it isn't obvious, this bug is my number one complaint with dasyatis. Argh!
Jul 19 2016
This bug is very annoying. Is there some other implementation of dbus that we can swap in to better localize the bug? systemd-dbus maybe?
Possibly related to this, if I use gnome-www-browser (link to google-chrome) on the command line to open a new web page then it just takes a moment prior to the "Too many open files" thing but takes like 1-2 minutes to open the page after the "Too many..." is observed. I suspect they are related. Maybe there is a dbus call with a timeout involved in opening the link?
I'm not sure if this is helpful, but I recorded dbus-monitor output from the beginning of a login session up to when it started reporting that "too many open files" problem. See attached.
Here's a similar report, but without any solution:
Redshift doesn't work either. I guess nouveau is not mature enough yet.
Jul 18 2016
Hm, I need to try redshift which offers multiple adjustment methods.
I upgraded to dasyatis today. I am happy to report that USB tethering works great again.
Oh, and I had 2 copies of libpng that required manual intervention.
I also had to fix a few more symlinks to libraries in /usr/lib such as libresolv and libz
Jul 16 2016
This is intentional, because adding a new arch means some overhead we don't want to add when people don't use i386, which will be the majority by now.
If you are using a 32bit app, adding i386 is a really easy task. And the new Skype client for Linux also supports amd64.
Jul 15 2016
This took ages, but I think we're done here :-)
Debian also found a solution for secure boot, which we will likely adopt for Tanglu 5.
Patch works here, please test for any issues! :-)
Jul 14 2016
This should be fixed now.
If you can, please test if this issue still exists for you!
Patch for this is on its way to out daily image builds.
Jul 1 2016
Actually, this is part of a bigger issue... The chain is:
I found one point at the xda-developers forum. One member mentioned that AT&T use a tethering lock
Jun 30 2016
So calibre is effectively blocking on the i386 build of python3.5?
This was already done, but calibre still needs to migrate.
See http://qa.tanglu.org/migrations/britney_excuses.html#calibre on what is missing to make this happen :)
Jun 29 2016
Jun 27 2016
Version 5.0.22-dfsg-1 is in staging, which should solve this issue.
It might need some time to migrate, apparently there are issues with that atm.
Jun 26 2016
The enx026472600378 interface is the phone. > It might be also [[ https://code.google.com/p/android/issues/detail?id=82545 | this one ]] That issue has a bunch of complaints with no clear resolution.
Jun 24 2016
Do you use some kind of security...firewall..protective software on your phone? It might block network traffic over usb and/or bluetooth
Jun 23 2016
Too bad. I thought this is the issue. Could you try the following: connect your phone by cable with your computer tethering switched on. What does "lsusb" and "ip link" tell you. Should be something like usb... or en..
Another idea, but i am not very convinced. Do you use some kind of security...firewall..protective software on your phone? It might block network traffic over usb and/or bluetooth
Forgot to mention. It might be also this one
Jun 20 2016
Disabling ipv6 makes it fail much faster. Here is the log:
Jun 19 2016
I just tested this, the problem is gone in the latest Tanglu 4.0 (Dasyatis kuhlii) snapshot.
Looks like it worked very well! Thanks!
Ok, I completely missed that debdiff, but I got it fixed anyway. I think I also found out why libjson-c doesn't work with that..
For the record, here is a debdiff with the changes applied in Tanglu to make dpkg work correctly in the last non-broken upload (1.18.4tanglu2).
Jun 18 2016
On the laptop. I guess you use networkmanager. There you are able set up your connection parameters and your should be able to deselect ipv6
Jun 16 2016
This should be fixed with today's nightly builds - d-i wasn't copied over to Tanglu 4.0 (Dasyatis kuhlii) corectly, so there was a kernel version mismatch.
Thanks for reporting the issue!
Due to T221 - Gtk3 themes broken due to latest Gtk3 update the included Gtk themes have to be reworked that all GUIs looks similar again.
Bwt I saw your bug report concerning tethering with Android. I tend to say that Android could be the cause. I saw that ipv4 connection worked and ipv6 failed. Somewhere I read that dhcpv6 in Android still is not working. Maybe you could set the parameters for the network connection via bluetooth and usb to ipv4 only and give it again a try.
Jun 10 2016
I saw a gorgeous new GTK+3 Breeze theme in action at a KDE sprint this week :-)
So at least for Plasma we might have a solution (that should go into Tanglu 4.0 (Dasyatis kuhlii) soo though, when there is a release of the theme or reasonably bug-free Git snapshot can be taken).
Perhaps I find a patch which fixes or disarm this issue: https://bugs.freedesktop.org/show_bug.cgi?id=94887
I will give it a shot to see what's happen ...
Nope ... this patch (https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-20&id=6144b2276c7298040c080f85ffa83afbe1257c54) was dropped in gtk+3.0 (3.20.2-1) because it was in this release already :(
Jun 9 2016
Jun 5 2016
Since today Fvwm-Nightshade beta package is accepted in dasyatis.
Jun 4 2016
May 26 2016
I am happy with the command line script so this is not an urgent issue for me.
Here's what usually happened with bluetooth:
Here are the logs from the 1 time that I got bluetooth to work. Let me know what else you need to diagnose the issue.