from:"Florian W."

I cloned git://git.launchpad.net/~ubuntu-kernel-
test/ubuntu/+source/linux/+git/mainline-crack and checked out tag
v4.16.5, applied the 6 patches listed at the top of
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.5/ and the one debug
patch at https://lkml.org/lkml/2018/4/3/136.

journalctl before/during/after suspend&resume (see below for journalctl
after removing and modprobing the r8169 module):

Apr 29 00:17:38 flo-desktop systemd[1]: Reached target Sleep.
Apr 29 00:17:38 flo-desktop systemd[1]: Starting Suspend...
Apr 29 00:17:38 flo-desktop systemd-sleep[1950]: Suspending system...
Apr 29 00:17:38 flo-desktop kernel: PM: suspend entry (deep)
Apr 29 00:17:38 flo-desktop kernel: PM: Syncing filesystems ... done.
Apr 29 00:17:55 flo-desktop kernel: Freezing user space processes ... (elapsed 
0.004 seconds) done.
Apr 29 00:17:55 flo-desktop kernel: OOM killer disabled.
Apr 29 00:17:55 flo-desktop kernel: Freezing remaining freezable tasks ... 
(elapsed 0.003 seconds) done.
Apr 29 00:17:55 flo-desktop kernel: Suspending console(s) (use 
no_console_suspend to debug)
Apr 29 00:17:55 flo-desktop kernel: serial 00:04: disabled
Apr 29 00:17:55 flo-desktop kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Apr 29 00:17:55 flo-desktop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Apr 29 00:17:55 flo-desktop kernel: sd 0:0:0:0: [sda] Stopping disk
Apr 29 00:17:55 flo-desktop kernel: sd 1:0:0:0: [sdb] Stopping disk
Apr 29 00:17:55 flo-desktop kernel: ACPI: Preparing to enter system sleep state 
S3
Apr 29 00:17:55 flo-desktop kernel: PM: Saving platform NVS memory
Apr 29 00:17:55 flo-desktop kernel: Disabling non-boot CPUs ...
Apr 29 00:17:55 flo-desktop kernel: IRQ9: New affinity: 0-3 effective: 2
Apr 29 00:17:55 flo-desktop kernel: IRQ25: New affinity: 0,2-3 effective: 0
Apr 29 00:17:55 flo-desktop kernel: IRQ 25: no longer affine to CPU1
Apr 29 00:17:55 flo-desktop kernel: smpboot: CPU 1 is now offline
Apr 29 00:17:55 flo-desktop kernel: IRQ9: New affinity: 0-3 effective: 0
Apr 29 00:17:55 flo-desktop kernel: IRQ12: New affinity: 0-3 effective: 3
Apr 29 00:17:55 flo-desktop kernel: IRQ17: New affinity: 0-3 effective: 0
Apr 29 00:17:55 flo-desktop kernel: IRQ22: New affinity: 0,3 effective: 3
Apr 29 00:17:55 flo-desktop kernel: IRQ 22: no longer affine to CPU2
Apr 29 00:17:55 flo-desktop kernel: smpboot: CPU 2 is now offline
Apr 29 00:17:55 flo-desktop kernel: IRQ1: New affinity: 0-3 effective: 0
Apr 29 00:17:55 flo-desktop kernel: IRQ12: New affinity: 0-3 effective: 0
Apr 29 00:17:55 flo-desktop kernel: IRQ14: New affinity: 0-3 effective: 0
Apr 29 00:17:55 flo-desktop kernel: IRQ16: New affinity: 0 effective: 0
Apr 29 00:17:55 flo-desktop kernel: IRQ 16: no longer affine to CPU3
Apr 29 00:17:55 flo-desktop kernel: IRQ19: New affinity: 0-3 effective: 0
Apr 29 00:17:55 flo-desktop kernel: IRQ22: New affinity: 0,3 effective: 0
Apr 29 00:17:55 flo-desktop kernel: smpboot: CPU 3 is now offline
Apr 29 00:17:55 flo-desktop kernel: ACPI: Low-level resume complete
Apr 29 00:17:55 flo-desktop kernel: PM: Restoring platform NVS memory
Apr 29 00:17:55 flo-desktop kernel: PCI-DMA: Resuming GART IOMMU
Apr 29 00:17:55 flo-desktop kernel: PCI-DMA: Restoring GART aperture settings
Apr 29 00:17:55 flo-desktop kernel: LVT offset 1 assigned for vector 0x400
Apr 29 00:17:55 flo-desktop kernel: IBS: LVT offset 1 assigned
Apr 29 00:17:55 flo-desktop kernel: microcode: CPU0: new patch_level=0x01db
Apr 29 00:17:55 flo-desktop kernel: Enabling non-boot CPUs ...
Apr 29 00:17:55 flo-desktop kernel: x86: Booting SMP configuration:
Apr 29 00:17:55 flo-desktop kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Apr 29 00:17:55 flo-desktop kernel: process: Switch to broadcast mode on CPU1
Apr 29 00:17:55 flo-desktop kernel:  cache: parent cpu1 should not be sleeping
Apr 29 00:17:55 flo-desktop kernel: microcode: CPU1: patch_level=0x01db
Apr 29 00:17:55 flo-desktop kernel: CPU1 is up
Apr 29 00:17:55 flo-desktop kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Apr 29 00:17:55 flo-desktop kernel: Clockevents: could not switch to one-shot 
mode:
Apr 29 00:17:55 flo-desktop kernel: process: Switch to broadcast mode on CPU2
Apr 29 00:17:55 flo-desktop kernel:  lapic is not functional.
Apr 29 00:17:55 flo-desktop kernel: Could not switch to high resolution mode on 
CPU 1
Apr 29 00:17:55 flo-desktop kernel:  cache: parent cpu2 should not be sleeping
Apr 29 00:17:55 flo-desktop kernel: microcode: CPU2: patch_level=0x01db
Apr 29 00:17:55 flo-desktop kernel: CPU2 is up
Apr 29 00:17:55 flo-desktop kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Apr 29 00:17:55 flo-desktop kernel: Clockevents: could not switch to one-shot 
mode:
Apr 29 00:17:55 flo-desktop kernel: process: Switch to broadcast mode on CPU3
Apr 29 00:17:55 flo-desktop kernel:  lapic is not functional.
Apr 29 00:17:55 flo-desktop kernel: Could not switch to high resolution mode on 
CPU 2
Apr 29 00:17:55 flo-desktop kernel:  cache: parent cpu3 should not be slee

[Bug 1760073] Re: No network from suspend resume

Related/Duplicate(?):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772

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

Title:
  No network from suspend resume

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

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

[Bug 1760073] Re: No network from suspend resume

I have added a link to the upstream kernel.org bugzilla, I believe it's
the same bug.

** Bug watch added: Linux Kernel Bug Tracker #198973
   https://bugzilla.kernel.org/show_bug.cgi?id=198973

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=198973
   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/1760073

Title:
  No network from suspend resume

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

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

[Bug 1760073] Re: No network from suspend resume

Since updating to bionic, I notice the same symptoms (network not
working after suspend).

I'm adding this comment to note that this makes my network come up again, I'll 
try to add this as a post-suspend script as described above:
$ sudo modprobe -r r8169
$ sudo modprobe r8169
(Suggested in https://ubuntuforums.org/showthread.php?t=2386503 )

My journalctl looks a very little bit different, but I guess it's simply
because we don't use exactly the same mainboards, so the IRQs differ:

Apr 28 11:00:17 flo-desktop NetworkManager[733]:   [1524906017.6262] 
manager: sleep: wake requested (sleeping: yes  enabled: yes)
Apr 28 11:00:17 flo-desktop NetworkManager[733]:   [1524906017.6263] 
device (eth0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'managed')
Apr 28 11:00:17 flo-desktop kernel: r8169 :02:00.0 eth0: link down
Apr 28 11:00:17 flo-desktop kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is 
not ready
Apr 28 11:00:17 flo-desktop NetworkManager[733]:   [1524906017.6566] 
manager: NetworkManager state is now DISCONNECTED
Apr 28 11:00:20 flo-desktop ModemManager[693]:   Couldn't check support 
for device at '/sys/devices/pci:00/:00:0a.0/:02:00.0': not 
supported by any plugin
Apr 28 11:00:20 flo-desktop kernel: do_IRQ: 3.36 No irq handler for vector

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

Title:
  No network from suspend resume

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

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

[Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

2017-12-26 Thread Florian W.

Using artful, I updated these packages (everything that used to have version 
"17.2.2-0ubuntu1" on my system) to version "17.2.4-0ubuntu1~17.10.1" from 
-proposed:
libegl1-mesa:amd64 libgbm1:amd64 libgl1-mesa-dev:amd64 libgl1-mesa-dri:amd64 
libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-glx:i386 
libglapi-mesa:amd64 libglapi-mesa:i386 libgles2-mesa:amd64 
libwayland-egl1-mesa:amd64 libxatracker2:amd64 mesa-common-dev:amd64 
mesa-vdpau-drivers:amd64 mesa-vulkan-drivers:amd64

After a reboot, I can confirm Lawrence's observation that vulkan-
smoketest segfaulted on the old version, but seems to work fine using
the version from -proposed.

Since Lawrence forgot to remove the verification-needed-artful tag, I'm
going to remove it now.

** Tags removed: verification-needed-artful

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

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

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

[Bug 1573624] Re: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-04-16 Thread Florian W.

Ubuntu 16.10 -> 17.04 upgrade fails because of this, presumably if
"systemctl disable mysql" was used earlier. Is that an unsupported
configuration? I enabled/started mysql when the first modal error
message dialog was displayed and it eventually re-tried the mysql
upgrade (which succeeded with a message like "Mysql data format already
up-to-date"). However, the Ubuntu upgrader GUI just quit after the main
upgrade process was finished instead of cleaning up and restarting the
system. I did some manual clean-up and everything appears to be fine.

** Changed in: mysql-5.7 (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1573624/+subscriptions

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

[Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-12-16 Thread Florian W.

Flash not working is less of a show stopper than half of the internet
not working because of trust issues. (Who needs flash anyway? I use it
maybe once a month, but now I can't do my christmas shopping in Chromium
because amazon doesn't work no matter what.) So if you can't get flash
to work, I'd recommend just pushing the new chromium anyway. :-)

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions

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

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-24 Thread Florian W.

Thanks Joseph!

I now believe I'm seeing two different issues in 4.8 that are not in 4.4 and 
slow down my boot, which is very confusing.
- #1: High number of kworkers (fixed in 4.8 using the two patches and bisected 
by Doug Smythies already)
- #2: Unknown other issue. I've noticed that when compiling a simple 
cmake/ninja project using 6 compiler processes on my rather old 4-core CPU, 
some kernels show odd behaviour that might also slow down the boot process.

When compiling that cmake project on 4.4, 4.6-7afd16f or 4.7-rc1, issue
#2 does not exist. While compilation takes place on 4.8 (no matter if
kworker patches are applied or not), my mouse cursor becomes sluggish
and it takes a long time to just switch to another window in Unity 7.
Compilation speed is unaffected though, so maybe just some kind of task
switching problem, not a CPU utilization issue.

So that makes it quite difficult to tell if any given kernel is good or
bad by just looking at the boot time. As far as I can tell, this is the
current list of kernels and the issues they have, where #2 was detected
using the cmake compilation behaviour and #1 by the number of kworker
processes after boot (should be ~35):

4.8 + patches: #2
4.8: #1, #2
4.7-rc1: #1
4.6-7afd16f: none
4.4: none

4.8 has about the same wall clock boot time as 4.7-rc1 in my case, while
4.8+patches is ~5 seconds faster, but that's hard to tell, since boot
times vary by 2-3 seconds anyway. So #1 apparently dominates the slow
down. I've only been able to get a "perfect" <10sec boot time from GRUB
to lightdm with 4.4 and 4.6-7afd16f. So the order of boot speed is like
this right now for me:

4.4|4.6-7afd16f < 4.8+patches < 4.8|4.7-rc1

Sorry for the long-winded comment, I just feel uncomfortable calling
this kernel "good" or "bad" without explaining why 4.7-rc1 might
actually be "good" on my system concerning issue #2. 4.6-7afd16f appears
to be as "good" as 4.4 in any case.

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

Title:
  [4.8 regression] boot has become very slow

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

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

[Bug 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG

2016-10-24 Thread Florian W.

Concerning the "bootspeed" tag, the NM issue would be less noticable if
"rc-local.service" was removed from "After=" in plymouth-quit.service.
That way, my boot-to-graphical-login is a few seconds faster because
plymouth is only visible for a very very short time instead of waiting
up to 8 seconds for the network to come up. I did that using systemd
override, and now my boot on kernel 4.4 is almost as fast as it was in
16.04.

Of course, technically the full boot including nmbd etc. still takes the
same time because NM is still slow, but I don't really care if nmbd is
up when I type my password into lightdm. The only thing that matters to
me is that I can type my password and then fire up Chromium, by which
time the network generally is ready to use in my case.

But maybe there's a good reason for some people to have rc.local
executed (and therefor network ready to use) before starting lightdm.

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

Title:
  NetworkManager takes very long to start, or times out, blocked on RNG

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1622893/+subscriptions

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

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-24 Thread Florian W.

My boot time comparison: (Wall clock time from GRUB to lightdm ready for login)
4.4: 12.28s
4.8.0-26 + Patches (Joseph's kernel): 21.78s
4.8.0-22 (Yakkety): 25.06s

This is with NetworkManager-wait-online.service enabled, which seems to
take ~8s in my case.

The attached file has systemd-analyze (blame|critical-chain) output for
each boot. Seems like slowdowns are all over the place, with some
exceptions like nmbd. nmbd takes 5.1s no matter which kernel I use.

And apparmor.service behaves opposite to boot time in this case: When
boot is slower, apparmor.service loads faster.

Loading times after typing my password into lightdm appear to correlate
with boot times, but I haven't measured them. Noticably slower with 4.8
compared to 4.4.

I don't have enough time to learn how to compile Ubuntu kernel packages
and start a bisection right now, but maybe I can start an attempt next
week. My CPU is old / slow though, so that will probably take some time.

** Attachment added: "boot times.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+attachment/4766355/+files/boot%20times.txt

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

Title:
[4.8 regression] boot has become very slow

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

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

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-23 Thread Florian W.

Thanks Joseph! I'm seeing the same effect described by Martin.
Boot+lightdm+loading Unity 7 is not as fast as it used to be in 16.04.

I need to compare timings (4.8 patched vs 4.8 vs 4.4) tomorrow to make
sure, but I also feel like it's a little faster now with the patches
applied.

The number of kworker processes after boot has reduced drastically using
the patched kernel, it's a sane number now (~30), not 1004 like when
using the unpatched 4.8 kernel.

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

Title:
  [4.8 regression] boot has become very slow

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

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

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-20 Thread Florian W.

My problem is probably the same that Doug Smythies described in bug
1626564 . I used the "echo workqueue:workqueue_queue_work >
/sys/kernel/debug/tracing/set_event" method and had about 1000 work
items enqueued by "memcg_kmem_cache_create_func" all at pretty much the
same time, which correlates nicely with the 1000 kworker processes I see
after boot.

If Martin has the same issue with lots of kworkers (I'm still not quite
sure?), this might be the same issue.

So I suspect the bad commit might be:
81ae6d03952c1bfb96e1a716809bd65e7cd14360
"mm/slub.c: replace kick_all_cpus_sync() with synchronize_sched() in 
kmem_cache_shrink()"
according to https://bugzilla.kernel.org/show_bug.cgi?id=172991

This commit was released in Linux 4.7.

This patch might fix the issue, but I haven't tested it:
https://patchwork.kernel.org/patch/9359271/

** Bug watch added: Linux Kernel Bug Tracker #172991
   http://bugzilla.kernel.org/show_bug.cgi?id=172991

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

Title:
  [4.8 regression] boot has become very slow

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

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

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-20 Thread Florian W.

Well, I guess the other patch is required as well for SLUB (not only SLAB as I 
assumed at first):
https://patchwork.kernel.org/patch/9361853/

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

Title:
  [4.8 regression] boot has become very slow

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

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

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-19 Thread Florian W.

This is what I get right after boot and login into Unity 7 (executed in Gnome 
Terminal):
$ ps aux | grep kworker | wc -l
1004

Kernel is 4.8.0-22-generic. After a few minutes, only 21 kworkers remain. Load 
after 4 minutes is not excessive (1244 sleeping processes), forgot to check 
load right after boot:
up 4 min,  1 user,  load average: 1,01, 1,79, 0,94

I'm not sure if it is of any help, but I've attached the output of "ps
aux | grep kworker".

** Attachment added: "ps aux | grep kworker"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+attachment/4763631/+files/kworkers

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

Title:
  [4.8 regression] boot has become very slow

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

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

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-14 Thread Florian W.

Same here, downgrading to 4.4 from Xenial improved the situation (boot
still feels a little slower than Xenial though, maybe because of the
NetworkManager bug). I use a 7 years old desktop computer based on a
Gigabyte motherboard and AMD Phenom II X4 955 CPU, So it's not Thinkpad-
related.

(From GRUB to lightdm used to be 7 seconds in 16.04, but using Kernel
4.8 and the new network manager it feels more like 20 secs. Also, the
Unity 7+Chromium launch used to take just very few seconds, now it's a
noticable delay with only the wallpaper showing, no matter which kernel
I use, so that's unrelated. Anyway, booting my computer has just become
a lot less fun even though I removed Apache 2 and Tomcat. :( )

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

Title:
  [4.8 regression] boot has become very slow

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

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

[Bug 1621278] [NEW] package printer-driver-gutenprint 5.2.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4

2016-09-07 Thread Florian W.

Public bug reported:

Error displayed during GUI-based upgrade from 14.04 to 16.04.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: printer-driver-gutenprint 5.2.11-1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Sep  8 01:53:22 2016
DuplicateSignature:
 package:printer-driver-gutenprint:5.2.11-1
 Setting up printer-driver-gutenprint (5.2.11-1) ...
 sed: Kann /var/cache/cups/ppd-updates nicht bearbeiten: Das ist keine normale 
Datei
 dpkg: error processing package printer-driver-gutenprint (--configure):
  subprocess installed post-installation script returned error exit status 4
ErrorMessage: subprocess installed post-installation script returned error exit 
status 4
InstallationDate: Installed on 2013-03-10 (1277 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: gutenprint
Title: package printer-driver-gutenprint 5.2.11-1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 4
UpgradeStatus: Upgraded to xenial on 2016-09-07 (0 days ago)

** Affects: gutenprint (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package printer-driver-gutenprint 5.2.11-1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 4

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

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

[Bug 1477720] Re: Unity8 won't install properly

2016-03-19 Thread Florian W.

I also get this when running sudo unity8-lxc-setup --rebuild:
> Starting the container
> Not able to connect to the network.

When trying to log into the unity8 lxc session afterwards, I get this in 
unity-system-compositor.log (probably expected?):
0
130
lxc_container: cgmanager.c: lxc_cgmanager_enter: 694 call to 
cgmanager_move_pid_abs_sync failed: invalid request
lxc_container: cgmanager.c: cgm_attach: 1324 Failed to enter group 
/lxc/unity8-lxc/init.scope
lxc_container: attach.c: lxc_attach: 831 error communicating with child process
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill 
-l [sigspec]

This is the output you requested:

$ sudo lxc-start -n unity8-lxc --logfile=/tmp/start_unity8-lxc.out 
--logpriority=DEBUG
lxc-start: lxc_start.c: main: 279 Container is already running.
$ sudo lxc-stop -n unity8-lxc # this takes quite long, maybe a minute
$ sudo lxc-start -n unity8-lxc --logfile=/tmp/start_unity8-lxc.out 
--logpriority=DEBUG
$

The file start_unity8-lxc.out is attached to this comment.

** Attachment added: "start_unity8-lxc.out"
   
https://bugs.launchpad.net/unity8-preview-lxc/+bug/1477720/+attachment/4603119/+files/start_unity8-lxc.out

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

Title:
  Unity8 won't install properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-preview-lxc/+bug/1477720/+subscriptions

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

[Bug 1477720] Re: Unity8 won't install properly

2016-03-19 Thread Florian W.

I should probably add that I'm still on Trusty, kernel 4.2, and an older
mesa/Xorg stack.

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

Title:
  Unity8 won't install properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-preview-lxc/+bug/1477720/+subscriptions

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

[Bug 1463598] Re: Chromium 43 fails to use hardware acceleration

2015-09-06 Thread Florian W.

Hi,

I'm just wondering if WebGL is still disabled in 14.04, even though we
are on chromium 44 now? I wanted to enable WebGL just to see if I could
watch 360° Youtube vids then, and now noticed that it no longer works at
all, apparently due to this Ubuntu change.

I realize that lots of crashes are GPU-related, but IMHO ripping that
feature out of chromium completely is bad, as most chromium GPU features
are blacklisted (by Google) on my AMD system anyway because they tend to
cause problems. If it's too much of an issue, maybe GPU stuff could be
blacklisted for all drivers, and those who would like to use WebGL etc.
could manually override the blacklist in about:flags? That's what I have
done repeatedly in the past, although I'm well aware that any strange
behaviour could be related to disabling the blacklist.

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

Title:
  Chromium 43 fails to use hardware acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1463598/+subscriptions

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

[Bug 1454699] Re: Vivid update to 3.19.7 stable release

2015-05-21 Thread Florian W.

This kernel (3.19.7), as well as the SRU-proposed 3.19.8, is also
affected by the ext+raid0+trim "chunksize not a power of 2
patch"-regression that causes severe data loss. So I certainly don't
want this patch to land on my trusty system with -lts-vivid kernel. :)

https://lkml.org/lkml/2015/5/21/167

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

Title:
  Vivid update to 3.19.7 stable release

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

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

[Bug 1454202] Re: Utopic update to 3.16.7-ckt11 stable release

2015-05-21 Thread Florian W.

Since 3.16.7-ckt11 appears to be affected by the ext4+raid0+trim
corruption bug [1], it might be better not to update to -ckt11.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=98501

** Bug watch added: Linux Kernel Bug Tracker #98501
   http://bugzilla.kernel.org/show_bug.cgi?id=98501

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

Title:
  Utopic update to 3.16.7-ckt11 stable release

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

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

[Bug 1456627] Re: Almost unusuable while non-Ubuntu device connected through adb

2015-05-20 Thread Florian W.

Ah, if the log steadily grows and is never truncated, that might have
caused the increasing CPU usage for rendering the log, and increasing
memory usage as well. I still wonder why the spawning of new processes
fails after some time though.

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

Title:
  Almost unusuable while non-Ubuntu device connected through adb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1456627/+subscriptions

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

[Bug 1456627] Re: Almost unusuable while non-Ubuntu device connected through adb

2015-05-20 Thread Florian W.

> Can you check the device log output on the devices page and paste the
contents?

Here's the log after a minute or so (protocol fault at the bottom => I 
disconnected the device to copy the log):
http://paste.ubuntu.com/11242404/

I didn't think of checking the log earlier. Probably the first thing I
should have checked!

> We push out a quick update to fix this bug.

Thanks a lot :-)

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

Title:
  Almost unusuable while non-Ubuntu device connected through adb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1456627/+subscriptions

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

[Bug 1456627] Re: Almost unusuable while non-Ubuntu device connected through adb

Well, sorry for the long post. %) I think I found the bug.

Anyway, is it possible that…
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/qtcreator-plugin-ubuntu/wily/view/head:/src/ubuntu/ubuntudevice.cpp

In line 209 or 216, the condition is true because my device is not an
Ubuntu device. So m_errorCount is incremented and detect() is called.
detect() is an alias for detectDeviceVersion().

So detectDeviceVersion() calls startProcess() again, i.e. the script is
instantly invoked again after a failure.

processFinished() then has the check for "maximum of 3 attempts" (line
165), but if the exit code of the process is 0, the m_errorCount is
reset to 0. (BTW, there's also a Q_UNUSED macro in processFinished()
that can probably be removed?) And…

$ /usr/share/qtcreator/ubuntu/scripts/device_version 007692f760d6239b
/system/bin/sh: chroot: not found
/system/bin/sh: chroot: not found
/system/bin/sh: chroot: not found
/system/bin/sh: chroot: not found
$ echo $?
0

So in my case, the m_errorCount is probably set to 0 after each
device_version execution. And that probably explains the "infinite
loop"-style behaviour I observed.

It's interesting to see that my system hardly manages to execute the script 
more than once per second. I added
echo $(date) >> /tmp/log
to see how often it's called. I guess that spawning a new shell process (bash 
in my case) is rather slow. :-)

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

Title:
  Almost unusuable while non-Ubuntu device connected through adb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1456627/+subscriptions

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

[Bug 1456627] Re: Almost unusuable while non-Ubuntu device connected through adb

Thanks for your important questions, Zoltan!

> What CPU and how much memory do you have on that device?

It's an old AMD Phenom II X4 955 BE. Still, qt creator usually needs
much less than one full core when just editing code files and generally
works quite well. I have 8GB of memory.

> Were you monitoring during that "hanging" period what else was going
on in your system?

I looked at "top" and found that qtcreator uses 99% (out of 400%
theoretically possible with my 4 core CPU).

No monitoring other than that, but I reproduced the issue again. There
are two different /usr/share/qtcreator/ubuntu/scripts/device_version
processes running right now, and in total I counted more than 3 of them
since I started ubuntu-sdk. At least that's what I assume, I've
repeatedly called ps aux | grep script and each time, there are a few of
them active and they have new PIDs each time.

> Anyhow, QtCreator is a big and heavy application, it is not free from
bugs. If we find a resource leak, we will follow it up with the upstream
developer.

It's working quite nicely when I don't have my Android phone attached
via USB, so I don't think it's an upstream bug. Also worked fine when I
attached my phone with Ubuntu booted on it.

> [The device_version script] does not use much CPU or any system
resources. In your case it got confused because your android device had
the same ID as the earlier registered Ubuntu device (due to the dual
boot). Anyhow the SDK tries three times to discover the attached device
and then it gives up.

Yeah, the script itself seems to be relatively lightweight. However it's
executed in what appears to be an infinite loop on my system. So the
"three attempts" limit might not work correctly?

> Sorry my ignorance, but I am not a kernel guru. How does that script
proves that the qtcreator is forking 30 times a second?

Sorry, my post was not even close to clear enough about that. AFAIK the
shell command shows that there were ~300 new processes spawned within
the 10 seconds sleep period, because the PID of each grep call was
incremented by ~300 compared to the last grep. AFAIK, PIDs are chosen
incrementally, so each new process gets a PID of $lastPID+1, unless that
PID is already in use. So a "grep, wait 10 seconds, grep" sequence
should show that both grep PIDs are pretty similar on my relatively calm
desktop system. A difference of 300 between both PIDs tells me that my
system spawned 300 processes in 10 seconds. Since top shows nothing
unusual other than 99% qtcreator CPU usage, I assumed that most of the
300 processes were spawned by qtcreator (I suspect: by the qtcreator
ubuntu plugin).

I have now disconnected my phone from USB. top shows that qtcreator is
now down to 0.0%, but takes up 30% of my memory (ps shows RSS 2468524 –
2.4G, this might indicate a leak? Can't remember what qtcreator memory
usage is normal after 30 mins of idling in the background.).

Now let me repeat that command:
$ while true; do ps aux | grep OnlyFindGrepItself; sleep 10; done
x   6171  0.0  0.0  18980  2136 pts/0S+   21:23   0:00 grep 
--color=auto OnlyFindGrepItself
x   6174  0.0  0.0  18980  2192 pts/0S+   21:23   0:00 grep 
--color=auto OnlyFindGrepItself
x   6178  0.0  0.0  18980  2200 pts/0S+   21:23   0:00 grep 
--color=auto OnlyFindGrepItself
So down to to a PID increase of 4 between grep calls, or ~0.4 forks per second 
(most of which are probably caused by the shell command itself).

I think that makes it relatively clear that connecting my phone causes
the issues, and since part of the issue is that qtcreator uses 99% CPU
according to top, I'd guess that the issue is in the qtcreator process.
Also, since I definitely have more than 3 invocations of the
device_version script, it is probably related to the script or the
invocation of the script, so it's probably a bug in the qtcreator ubuntu
plugin.

I hope this explains my thoughts a little better, though I do have some
doubts about it. So feel free to ask again if this was not clear enough.
:-)

To reproduce the issue, this time it was enough to plug in my phone,
then start the SDK. At first, it's not at 99% CPU – more like 40%. It
steadily needs more CPU time until it hits 99%. This goes on for some
time, then suddenly CPU usage drops and at that time, I have to restart
the SDK because I can no longer start the build or deploy the app to my
phone. Apparently the SDK is unable to spawn a new shell process. If the
CPU usage is caused by excessively calling the device_version script,
this explains the sudden CPU usage drop: the script can't be spawned
because qtcreator is unable to spawn new processes.

Thanks!

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

Title:
  Almost unusuable while non-Ubuntu device connected through adb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu

[Bug 1456627] Re: Almost unusuable while non-Ubuntu device connected through adb

While this happened all the time in the last few days, I now did
something that apparently made it stop (temporarily?).

Maybe deleting the device from the Devices view in Ubuntu SDK? It re-
appeared quickly, but maybe that stopped it. Maybe it's important that
the same device (Nexus 4) has been used with the Ubuntu OS instead of
Android before, using the Dual-Boot mechanism.

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

Title:
  Almost unusuable while non-Ubuntu device connected through adb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1456627/+subscriptions

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

[Bug 1456627] [NEW] Almost unusuable while non-Ubuntu device connected through adb

Public bug reported:

I'm using qtcreator-plugin-ubuntu
3.1.1+15.10.20150508-0ubuntu1i~0trusty1 from the Trusty PPA.

I'm currently porting my Ubuntu App to Android, so I have my android
phone connected to my computer using USB.

A few days ago I noticed that qtcreator started using a complete CPU
core soon after startup, which makes working with qtcreator quite
unpleasant (sluggish interface, and CPU fan noise). After some time (30
minutes?), it is then no longer possible to start a build process in
qtcreator for what appears to be a strange reason. I no longer have the
error message. I guess this is because of some kind of ressource leak.

Now I noticed these popping up in ps aux quite frequently while it happens:
> x  10209  8.0  0.0  19696  2972 ?S14:57   0:00 /bin/bash 
> /usr/share/qtcreator/ubuntu/scripts/device_version 007692f760d6239b
> x  10233  0.0  0.0  19696   304 ?S14:57   0:00 /bin/bash 
> /usr/share/qtcreator/ubuntu/scripts/device_version 007692f760d6239b
> x  10234  0.0  0.0  19696  1888 ?S14:57   0:00 /bin/bash 
> /usr/share/qtcreator/ubuntu/scripts/device_version 007692f760d6239b

And this test shows that something, probably qtcreator, is forking almost 30 
times per second:
$ while true; do ps aux | grep OnlyFindGrepItself; sleep 10; done
> x  10841  0.0  0.0  18980  2152 pts/0S+   14:58   0:00 grep 
> --color=auto OnlyFindGrepItself
> x  11132  0.0  0.0  18980  2152 pts/0S+   14:58   0:00 grep 
> --color=auto OnlyFindGrepItself
> x  11406  0.0  0.0  18980  2152 pts/0R+   14:58   0:00 grep 
> --color=auto OnlyFindGrepItself

As soon as I disconnect my android device from the USB port, the CPU fan
goes silent and there's no significant CPU usage any more.


So I guess that something in the qt creator Ubuntu plugin tries to detect my 
android phone as an Ubuntu device, fails, and then instantly tries again.

This is from qtcreator strace and repeats quite often as well: read(36, 
"/system/bin/sh: chroot: not found\r\n", 35) = 35
Looks like something is trying to use chroot on my phone, and my Android 
lollipop can't do that. So the device_version script might not be the only 
thing that keeps my system busy.

** Affects: qtcreator-plugin-ubuntu (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Almost unusuable while non-Ubuntu device connected through adb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1456627/+subscriptions

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

[Bug 1179160] Re: Segfault in libc-2.15.so

2015-05-10 Thread Florian W.

A full stacktrace could help with finding the error, the message posted
does not tell me what's wrong.

The crash could be related to a "broken" media file that kills minidlna,
you can test that by setting the media directory to some empty location
on your hard drive. Minidlna code quality has improved since 12.04, so
this bug might even be fixed when using 15.04 or some other more recent
Ubuntu release.

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

Title:
  Segfault in libc-2.15.so

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

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

[Bug 1448521] Re: sudo unity8-lxc-setup fails on 15.04

2015-04-28 Thread Florian W.

This bug appears to be fixed now in the PPA, thanks!

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

Title:
  sudo unity8-lxc-setup fails on 15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-preview-lxc/+bug/1448521/+subscriptions

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

[Bug 1326296] Re: minidlnad hangs on one specific file

It might be interesting to know if this happens when minidlna is linked
against ffmpeg instead of libav. Some people say that libav has more
bugs (some even say it's "broken"), so maybe this is one of those bugs.
It should be possible to remove libav and install ffmpeg on newer Ubuntu
releases, then compile minidlna manually.

libav seems like it's used in Ubuntu/Debian mostly for political
reasons.

Alternatively, another distribution like Arch Linux can be used to test
if the file works there with minidlna+ffmpeg. I don't have a buggy mkv
file, so I can't do that. I do have an Arch Linux setup available
though.

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

Title:
  minidlnad hangs on one specific file

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

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

[Bug 1231886] Re: MiniDLNA does not support RegisterDevice SOAP action

According to http://sourceforge.net/p/minidlna/bugs/212/ , this should
work since minidlna 1.1.2. So any trusty, utopic or vivid users should
be fine.

Can anyone confirm so we can close this as "fix released"?

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

Title:
  MiniDLNA does not support RegisterDevice SOAP action

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

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

[Bug 1389241] Re: package minidlna 1.1.2+dfsg-1.1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Is this still an issue? I'm not very experienced with upstart. The error
message almost sounds like the minidlnad binary is missing. Can you
check if /usr/bin/minidlnad exists? Maybe your file system was full /
corrupted when minidlna was upgraded the last time? Have you tried

sudo apt-get install --reinstall minidlna

to reinstall minidlna and see if this fixes your issue?

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

Title:
  package minidlna 1.1.2+dfsg-1.1build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

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

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

[Bug 878734] Re: package minidlna 1.0.21 dfsg-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2

It seems like the attached logs don't tell us why the post-install
script returned an error.

This error might occur if you manually remove the "minidlna" user or
"minidlna" group while having minidlna installed on your system.

There could be other problems that cause an exit status 2.

Since this bug is more than 3 years old, you probably can't reproduce
this to figure out what's wrong. I'm marking this as "Incomplete". If
anyone still has the same issue, I think you can run this to get more
info about the error and post that as a comment:

sh -x /var/lib/dpkg/info/minidlna.postinst configure

** Changed in: minidlna (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package minidlna 1.0.21 dfsg-1 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 2

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

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

[Bug 994234] Re: package minidlna 1.0.21+dfsg-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2

It seems like the attached logs don't tell us why the post-install
script returned an error.

This error might occur if you manually remove the "minidlna" user or
"minidlna" group while having minidlna installed on your system.

There could be other problems that cause an exit status 2.

Since this bug is almost 3 years old, you probably can't reproduce this
to figure out what's wrong. I'm marking this as "Incomplete".  If anyone
still has the same issue, I think you can run this to get more info
about the error and post that as a comment:

sh -x /var/lib/dpkg/info/minidlna.postinst configure

** Changed in: minidlna (Ubuntu)
   Status: New => Incomplete

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

Title:
  package minidlna 1.0.21+dfsg-1ubuntu1 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 2

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

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

[Bug 979505] Re: minidlna crashed with SIGABRT in __libc_message()

I think this was fixed in minidlna 1.0.22 by this commit:
http://sourceforge.net/p/minidlna/git/ci/c599ed3a9fe79f69c2a229d5f6f1d30534a65bfb/

So let me close this as "Fix Released". If anyone has this crash in
Trusty or newer Ubuntu releases, please reopen. :) Ubuntu 12.04
(precise) has an old, buggy minidlna version.

** Changed in: minidlna (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  minidlna crashed with SIGABRT in __libc_message()

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

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

[Bug 1077371] Re: Regression: Comma delimited list of network interfaces no longer works

The report says that this works in Precise (12.04). Which versions are
affected by this bug? Is this still an issue in Vivid? In Trusty, the
comma delimiter seems to work. At least minidlna doesn't crash. (I don't
get any logs and the -d flag crashes, so I can't check for the error
message.)

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

Title:
  Regression: Comma delimited list of network interfaces no longer works

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

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

[Bug 1053173] Re: minidlna crashes on boot when no active network connection

As I stated above, this should be fixed in recent minidlna releases, so
I close this bug now. If this still happens on Ubuntu 14.04 (Trusty) or
newer releases, please reopen the bug report.

** Changed in: minidlna (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  minidlna crashes on boot when no active network connection

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

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

[Bug 1363069] Re: Segfault running "minidlnad -d" in 14.04 docker container

minidlna-1.1.4+dfsg-1 that was imported from Debian to Ubuntu Vivid is
supposed to have a fix for this.

** Changed in: minidlna (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Segfault running "minidlnad -d" in 14.04 docker container

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

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

[Bug 1448521] Re: sudo unity8-lxc-setup fails on 15.04

I think this should fix itself when /usr/share/distro-info/ubuntu.csv is
updated to contain the "w" series. The error occurs in lots of ubuntu-
related tools when there is no known development release. See LP Bug
#1068390 for example.

Nevertheless, unity8-lxc-setup should be fixed to handle that error, I
guess.

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

Title:
  sudo unity8-lxc-setup fails on 15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8-lxc/+bug/1448521/+subscriptions

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

[Bug 1439158] Re: unity8-lxc update from PPA fails to install on Trusty

2015-04-01 Thread Florian W.

I (probably) fixed this by removing the extra space in front of "with"
in line 293. sudo apt-get -f install then worked without a flaw.

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

Title:
  unity8-lxc update from PPA fails to install on Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8-lxc/+bug/1439158/+subscriptions

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

[Bug 1439158] [NEW] unity8-lxc update from PPA fails to install on Trusty

2015-04-01 Thread Florian W.

Public bug reported:

This error started to appear yesterday whenever I do apt-get things.

$ LANG=C sudo apt-get install unity8-lxc
Reading package lists... Done
Building dependency tree   
Reading state information... Done
unity8-lxc is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up unity8-lxc (1.0.4-0~61~ubuntu14.04.1) ...
  File "/usr/bin/unity8-lxc-setup", line 293
with open(os.path.join(rootfs_path, "etc", "X11", 
"default-display-manager"), "w+") as fd:

 ^
IndentationError: unindent does not match any outer indentation level
dpkg: error processing package unity8-lxc (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 unity8-lxc
E: Sub-process /usr/bin/dpkg returned an error code (1)


$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04

(HWE stack with kernel and Xorg/mesa from Utopic installed manually)

** Affects: unity8-lxc (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  unity8-lxc update from PPA fails to install on Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8-lxc/+bug/1439158/+subscriptions

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

[Bug 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog

2015-02-21 Thread Florian W.

Sorry, the unity-control-center package was not taken from the PPA, but
from the bzr branch linked in this bug report. Not sure if these
packages use the same code.

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

Title:
  Mouse settings missing from Mouse & Touchpad dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions

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

[Bug 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog

2015-02-21 Thread Florian W.

I've built (on trusty) and installed the unity-control-center package
from the PPA, and unity-settings-daemon from utopic, and now I have a
mouse pointer speed option in the settings. That setting was missing
when I used the original trusty packages.

Now another problem is that the mouse cursor is pretty fast, even when
using the slowest setting. My mouse has a hardware DPI change button
though, so I can fix that. :-)

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

Title:
  Mouse settings missing from Mouse & Touchpad dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions

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

[Bug 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog

2015-02-21 Thread Florian W.

Lorenzo, have you tried the PPA referenced by Iain Lane (#35)? I'd love
to test that, but I'm still on trusty and the debs don't work. Let me
try to build the package locally.

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

Title:
  Mouse settings missing from Mouse & Touchpad dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions

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

[Bug 1241185] Re: Should provide policy based lifecycle exceptions

2015-02-18 Thread Florian W.

Since you want to mark this bug as "Won't fix", can you point me to some
docs for music-hub? I can only find some info about
QtMultimedia.MediaPlayer related to music-hub, but that QML API is
apparently missing the functionality described in this bug report.

I'm already using QtMultimedia.MediaPlayer, and while that allows me to
keep playing the current song when the display turns off or I switch to
another app, which is already a huge improvement over the state from
~1.5 years ago when I tried this the last time, it's still not even
close to "good enough".

When the current song ends, the MediaPlayer.onStatusChanged signal is
not executed immediately, but only after I switch back to my app or
unlock the phone. As far as I can tell, that signal is the only place
where I could start playback of the next song. So it's just silent after
the current song ends, clearly a very bad user experience.

You should either allow apps to run the slot connected to that signal
whenever it is fired (which might be pretty difficult to solve and opens
up a lifecycle policy exploit), or add a queue API to QtMultimedia /
some other QML namespace. (On a related note, a signal like
"playbackAboutToFinish" could allow implementing gapless playback in the
future.)

If you do the queue thing, make sure to support programatically deleting
from the queue before the media is played: I want to implement "play
next song from my app's queue, or if the user has not enqueued any
songs, play next song from album". If I am supposed to use the music-app
queue, I have to enqueue all the remaining songs on the current album
when playback starts. If a user then adds something to the app queue, I
must be able to remove everything from the music-hub queue, add the
user-provided song, then add every song following the newly enqueued
song on its album.

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

Title:
  Should provide policy based lifecycle exceptions

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

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

[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64

2015-02-18 Thread Florian W.

This is still an issue, and very confusing. I assume that most
developers who need external dependenices for the click package run into
this and wonder why the linker complains about not finding the library.

I guess most developers find it more convenient to add build rules that
copy prebuilt libraries from the chroot into the click package instead
of adding the library source code to their project. This ensures easy
click package updates whenever Ubuntu updates the library (without API
breaking changes of course). For this use case, running apt-get install
libwhatever-dev in the chroot is the first required step, and the user
expects to have a somewhat sane environment when clicking the "Maintain"
button.

I worked around this by installing libupnp6:armhf and libupnp6-dev:armhf
instead of libupnp-dev.

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

Title:
  new armhf click build chroot is DEB_BUILD_ARCH=amd64

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

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

[Bug 1422989] [NEW] emulator: mtp-server fails to start, respawns immediately -> high CPU load / log spam

2015-02-17 Thread Florian W.

Public bug reported:

I think the bug title and the logs attached by ubuntu-bug explain my
issue:

mtp-server fails to start on emulator image 105 (devel-proposed i386)
because there is no /dev/mtp_usb device. After the process quits, it is
instantly respawned, just to fail again. The emulator is now 0% idle
because it uses all the processing ressources to spawn apport, mtp-
server and (juding by PID delta between mtp-server processes) 8 other
processes over and over again.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: mtp-server 0.0.4+15.04.20150126-0ubuntu1
Uname: Linux 3.4.0-4-goldfish i686
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
Date: Tue Feb 17 22:59:27 2015
SourcePackage: mtp
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mtp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 vivid

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

Title:
  emulator: mtp-server fails to start, respawns immediately -> high CPU
  load / log spam

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

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

[Bug 1324333] Re: The Ubuntu touch emulator doesn't produce audio

2015-02-17 Thread Florian W.

I guess this is no surprise to anyone involved in ubuntu emulator
development, but for completeness sake: This is printed in the
"Application Output" tab in ubuntu-sdk when launching an app that
targets the 14.10 click target in the current devel-proposed emulator
image. It is supposed to use the QtMultimedia.MediaPlayer for playing
audio.

> Initializing AalServicePlugin
> virtual QMediaService* AalServicePlugin::create(const QString&) 
> "org.qt-project.qt.mediaplayer"
> [1424210133.140476] Loader: Loading modules from: 
> /usr/lib/i386-linux-gnu/mir/client-platform/
> [1424210133.140691] Loader: Loading module: 
> /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
> [1424210133.251984] Loader: Loading module: 
> /usr/lib/i386-linux-gnu/mir/client-platform/android.so
> [1424210133.379905] Loader: Loading module: 
> /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
> Creating a new static Service instance
> Failed to start a new media-hub player session:  
> org.freedesktop.DBus.Error.ServiceUnknown: The name core.ubuntu.media.Service 
> was not provided by any .service files
> Failed to create a new media player backend. Video playback will not function.

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

Title:
  The Ubuntu touch emulator doesn't produce audio

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

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

[Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2

2015-02-15 Thread Florian W.

I tried this again now, and after installing libgl1-mesa-dev-lts-utopic
I was able to re-install qt5-default and qtbase5-dev, and then ubuntu-
sdk.

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

Title:
  Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
  14.04.2

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

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

[Bug 1420366] Re: kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)

2015-02-12 Thread Florian W.

I have now verified that building the goldfish kernel from git with the
upstream commit cherry-picked, and then booting that kernel in the
emulator, solves my issue with libupnp.

** Summary changed:

- kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)
+ [fixed-upstream] kernel null pointer dereference after 
setsockopt(…IP_ADD_MEMBERSHIP…)

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

Title:
  [fixed-upstream] kernel null pointer dereference after
  setsockopt(…IP_ADD_MEMBERSHIP…)

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

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

[Bug 1420366] Re: kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)

There's actually a fix upstream, :
https://android.googlesource.com/kernel/goldfish/+/0836a0c191f580ed69254e0b287cdce58481e978

I hope there are plans to rebase to a recent goldfish kernel some time.
:)

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

Title:
  kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)

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

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

[Bug 1420366] Re: goldfish kernel panic after setsockopt(…IP_ADD_MEMBERSHIP…)

I have some more details about the kernel panic.

In net/ipv4/igmp.c, line 320, ip_route_output_ports() is called with socket 
(aka "sk") = NULL.
In include/net/route.h, line 150, that NULL socket pointer is passed on to 
sock_i_uid(), so sock_i_uid(NULL) is called.

That sock_i_uid() call is not in mainline Linux (neither 3.4 nor 3.18),
but it is in the Google android goldfish kernel.

I'd say that code is faulty, because the ip_route_output_ports()
function takes a NULL socket into account, only the recently added
sock_i_uid() call is missing a NULL check.

In net/core/sock.c, line 1477, the sock_i_uid() function then
dereferences the NULL pointer, which probably explains my kernel panic
issue.

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

Title:
  kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)

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

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

[Bug 1420366] Re: goldfish kernel panic after setsockopt(…IP_ADD_MEMBERSHIP…)

I think the goldfish kernel is not maintained in the android source
package, but in this separate linux-goldfish package, so it's time to
move this bug again.

** Package changed: android (Ubuntu) => linux-goldfish (Ubuntu)

** Summary changed:

- goldfish kernel panic after setsockopt(…IP_ADD_MEMBERSHIP…)
+ kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)

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

Title:
  kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)

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

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

[Bug 1420366] Re: emulator freeze on setsockopt(…IP_ADD_MEMBERSHIP…)

Okay, so it's not actually the emulator. The "guest system" (goldfish?)
simply kernel panics, see the attachment.

I guess the android source package is still correct though.

** Attachment added: "goldfish-kernel-panic.log"
   
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1420366/+attachment/4317217/+files/goldfish-kernel-panic.log

** Summary changed:

- emulator freeze on setsockopt(…IP_ADD_MEMBERSHIP…)
+ goldfish kernel panic after setsockopt(…IP_ADD_MEMBERSHIP…)

** Description changed:

+ Update: The "freeze" I explain in this bug is not an emulator freeze
+ (which I thought at first), but a goldfish kernel panic.
+ 
+ 
+ 
  This might be a bug in one of the products the ubuntu emulator is based
  on, or maybe it's a configuration issue. I don't know so I report this
  here.
  
  I'm trying to use libupnp in the Ubuntu emulator (My app was compiled
  using a 15.04 framework / i386 "kit" chroot created through ubuntu-sdk
  on Ubuntu 14.04, the emulator runs the "devel" i386 system image, I
  think r1, and libupnp is statically linked against my c++ backend
  module).
  
  My system is 14.04 and I use the SDK PPA, so…
  ubuntu-emulator is version 0.10-0ubuntu1
  ubuntu-emulator-runtime is version 20140922-1903-0ubuntu3
  
  There is a problem because InitUpnp() freezes the emulator instead of
  initializing the library correctly.
  
  By single-stepping through that library function and the functions called by 
that function, I figured out that it probably freezes in a setsockopt() call: 
(*)
  > ret = setsockopt(*ssdpSock, IPPROTO_IP, IP_ADD_MEMBERSHIP,
  >  (char *)&ssdpMcastAddr, sizeof(struct ip_mreq));
  
  Line 846:
  > 
http://sourceforge.net/p/pupnp/code/ci/master/tree/upnp/src/ssdp/ssdp_server.c#l846
  
  * (That guess is based on the fact that after entering
  create_ssdp_sock_v4(), there's a sequence of socket(), setsockopt(),
  bind(), inet_addr(), inet_addr(), setsockopt() and then it freezes when
  typing "fin" in gdb to return from the last setsockopt call – I don't
  have enough debug information in the binary to know exactly, and I'm
  looking at libupnp git master but linking against a precompiled
  libupnp.a supplied by Ubuntu.)
  
- 
- That system call apparently changes the socket to receive multicast packets. 
+ That system call apparently changes the socket to receive multicast
+ packets.
  
  Related: http://sourceforge.net/p/pupnp/mailman/message/18352779/ states
  that the same line of code caused issues for another qemu-based
  emulator, but that was in 2008 and AIUI qemu is supposed to support
  IP_ADD_MEMBERSHIP since 2009.

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

Title:
  goldfish kernel panic after setsockopt(…IP_ADD_MEMBERSHIP…)

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

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

[Bug 1420366] Re: emulator freeze on setsockopt(…IP_ADD_MEMBERSHIP…)

2015-02-10 Thread Florian W.

Turns out that goget-ubuntu-touch is not the correct source package for
this bug, since the emulator runtime is in the "android" package.

** Package changed: goget-ubuntu-touch (Ubuntu) => android (Ubuntu)

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

Title:
  emulator freeze on setsockopt(…IP_ADD_MEMBERSHIP…)

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

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

[Bug 1420366] [NEW] emulator freeze on setsockopt(…IP_ADD_MEMBERSHIP…)

2015-02-10 Thread Florian W.

Public bug reported:

This might be a bug in one of the products the ubuntu emulator is based
on, or maybe it's a configuration issue. I don't know so I report this
here.

I'm trying to use libupnp in the Ubuntu emulator (My app was compiled
using a 15.04 framework / i386 "kit" chroot created through ubuntu-sdk
on Ubuntu 14.04, the emulator runs the "devel" i386 system image, I
think r1, and libupnp is statically linked against my c++ backend
module).

My system is 14.04 and I use the SDK PPA, so…
ubuntu-emulator is version 0.10-0ubuntu1
ubuntu-emulator-runtime is version 20140922-1903-0ubuntu3

There is a problem because InitUpnp() freezes the emulator instead of
initializing the library correctly.

By single-stepping through that library function and the functions called by 
that function, I figured out that it probably freezes in a setsockopt() call: 
(*)
> ret = setsockopt(*ssdpSock, IPPROTO_IP, IP_ADD_MEMBERSHIP,
>(char *)&ssdpMcastAddr, sizeof(struct ip_mreq));

Line 846:
> http://sourceforge.net/p/pupnp/code/ci/master/tree/upnp/src/ssdp/ssdp_server.c#l846

* (That guess is based on the fact that after entering
create_ssdp_sock_v4(), there's a sequence of socket(), setsockopt(),
bind(), inet_addr(), inet_addr(), setsockopt() and then it freezes when
typing "fin" in gdb to return from the last setsockopt call – I don't
have enough debug information in the binary to know exactly, and I'm
looking at libupnp git master but linking against a precompiled
libupnp.a supplied by Ubuntu.)


That system call apparently changes the socket to receive multicast packets. 

Related: http://sourceforge.net/p/pupnp/mailman/message/18352779/ states
that the same line of code caused issues for another qemu-based
emulator, but that was in 2008 and AIUI qemu is supposed to support
IP_ADD_MEMBERSHIP since 2009.

** Affects: goget-ubuntu-touch (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  emulator freeze on setsockopt(…IP_ADD_MEMBERSHIP…)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1420366/+subscriptions

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

[Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2

2015-02-09 Thread Florian W.

Thanks, Maarten. I just noticed my comment was missing the apt command
that I used.

I now use

> LANG=C sudo apt install --install-recommends libgles2-mesa-lts-utopic
libglapi-mesa-lts-utopic linux-generic-lts-utopic xserver-xorg-lts-
utopic libgl1-mesa-dri-lts-utopic libegl1-mesa-drivers-lts-utopic libgl1
-mesa-glx-lts-utopic:i386

and now wine is preserved. However, I still lose qt5-default,
qtbase5-dev and some other qt5 libs, and also libsdl2-2.0-0 and related
sdl libs, and some random other libs where I'm not sure I really need
them (I guess not). Adding qt5-default and qtbase5-dev to the command
leads to http://paste.ubuntu.com/10141032/ (I already have the utopic
kernel, so that note there by apt is correct).

I'm not sure if this is a bug in one of the backported packages, or
another package, or even my system setup or apt skills. Since #16 and
#13 apparently had the same issue, it might be related. Let me know if
this is not the right place to post this. :-)

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

Title:
  Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
  14.04.2

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

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

[Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2

2015-02-09 Thread Florian W.

Is there any way to preserve wine, libsdl-*-dev and qt5 when installing
the hardware enablement bits on 14.04 (with -proposed disabled)?

I tried the suggested apt command lines, but none of them seemed to
install the new mesa/xorg stack and preserve wine/qt5/libsdl at the same
time. See the attached apt output.

** Attachment added: "apt-hwe.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1400626/+attachment/4315207/+files/apt-hwe.txt

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

Title:
  Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
  14.04.2

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

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

[Bug 1359265] Re: Characters mixing up in address bar

2015-01-27 Thread Florian W.

I was still able to reproduce this using Version
39.0.2171.65-0ubuntu0.14.04.1.1064 (hope we can get an update soon btw
:D), but it appears to be much more difficult now. It no longer happens
when I type at my normal typing speed. Maybe that's because the omnibar
suggestions apparently load pretty fast now, it used to be much slower.
Only characters typed while the suggestions load (i.e. chromium appears
to be frozen during that time) are mixed up.

The only way I can reproduce this now is:
- Open a new tab
- Concentrate and try to type "asdf" as fast as possible using the left hand
- Usually comes up as "adsf" in omnibar, like in 90% of attempts

I verified that my "asdf" typing skills are okay by opening gedit and
typing "asdf" as fast as possible 20 times. That worked correctly.

I'm not sure which input method I'm using. It's a USB keyboard. I tried
to find out how to identify my system's input method, but Google just
tells me how to type Japanese characters.

** Changed in: chromium-browser (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/1359265

Title:
  Characters mixing up in address bar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359265/+subscriptions

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

[Bug 1396224] Re: unity-system-compositor fails to launch / terminates with signal 15

2014-11-26 Thread Florian W.

This is fixed now, as far as I can tell. Thanks. :-)

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

Title:
  unity-system-compositor fails to launch / terminates with signal 15

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-preview-lxc/+bug/1396224/+subscriptions

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

[Bug 1391348] Re: [Errno 101] download chrome via china gfw

2014-11-19 Thread Florian W.

This is probably either a network connectivity issue or related to
censorship / nation-wide firewall in china, as you mention.

So you'd need to fix your internet connection or ask your government to
allow access to the google chrome download (not sure if there's a place
where you can ask for great firewall exceptions or if that'd be
dangerous / illegal). There's nothing that can be fixed in the package,
as far as I can tell.

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

Title:
  [Errno 101]  download chrome  via china gfw

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1391348/+subscriptions

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

[Bug 1386455] Re: Chromium 37 has 159 known security issues

2014-11-11 Thread Florian W.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Chromium 37 has 159 known security issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1386455/+subscriptions

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

[Bug 1312219] Re: Plugin needs to update automatically

2014-11-05 Thread Florian W.

Debian status is inaccurate, it is actually something like "Invalid" /
"Wontfix", not "Fix Released".

I do think this is a valid bug. The "proper" solution probably is:
Release an updated pepperflashplugin-nonfree package every time Google
updates the flash plugin. The package should contain a checksum of the
current .so file and download&extract&check&install the library on
installation. (This will only work if old chrome download files are
available even after a new version is released… otherwise, the package
installation will fail as soon as a new chrome version is released. In
that case, the checksum verification should be skipped, but still: a new
debian package should released every time flash gets updated.)

The Debian wiki says that this is not suitable for Debian because it's
apparently difficult to get security updates into stable if they are not
100% security related. So I wonder why there's no special exception for
closed-source software in Debian where patching ONLY security issues is
simply not possible… It really sounds stupid.

> But that would reopen the debate on how to get the updated Debian package
> in stable in a user friendly way and sufficiently fast. Note that the Debian
> package would pull in a combination of feature updates and security fixes in a
> new upstream release of closed-source software, which is somewhat difficult
> for Debian procedures to install quickly in stable. 

So Debian apparently prefers having really dangerous outdated versions
of flash installed on their users' systems (because ~~nobody knows about
update-pepperflashplugin-nonfree) instead of pushing one isolated
closed-source software package (that might do a little more than fixing
security issues) into stable.

The debian process is not very well suited for closed-source software. I
wonder if Ubuntu would be willing to improve this. It probably depends
on the number of Chromium users, most of which probably use pepperflash-
plugin-nonfree without knowing about the risk for their system when
installing & forgetting about that package.

So … please: Either drop the pepperflash package and recommend upstream
chrome for users that need flash, or fix the package.

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

Title:
  Plugin needs to update automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/pepperflashplugin-nonfree/+bug/1312219/+subscriptions

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

[Bug 1386455] [NEW] Chromium 37 has 159 known security issues

2014-10-27 Thread Florian W.

*** This bug is a security vulnerability ***

Public security bug reported:

Chromium 38 (released 3 weeks ago) fixes at least $52k worth of security issues:
http://googlechromereleases.blogspot.de/2014/10/stable-channel-update.html

So 159 chromium security fixes (with 113 "relatively minor") are waiting
for a MOTU to be packaged in Ubuntu.

Thanks to anyone taking care of that, and special thanks to Chad Miller
for having done so repeatedly.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 37.0.2062.120-0ubuntu0.14.04.1~pkg1049
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 28 00:09:44 2014
InstallationDate: Installed on 2013-03-10 (596 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to trusty on 2014-04-22 (188 days ago)
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-04-23T00:11:40.712095

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Information type changed from Private Security to Public Security

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3188

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3189

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3190

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3191

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3192

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3193

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3194

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3195

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3196

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3197

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3198

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3199

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3200

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

Title:
  Chromium 37 has 159 known security issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1386455/+subscriptions

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

[Bug 1359265] Re: Characters mixing up in address bar

2014-10-27 Thread Florian W.

Someone recently confirmed this, but I haven't experienced the bug in
recent weeks. Possibly since updating to 37?

Does this still affect anyone? If not, I'll close the bug in a few days.

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

Title:
  Characters mixing up in address bar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359265/+subscriptions

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

[Bug 1314076] Re: pbuilder-dist: Local archives othermirror overridden by later othermirror

2014-09-11 Thread Florian W.

I was about to go insane re-creating and updating chroots and using all kinds 
of pbuilderrc options. Nothing seemed to help. Then I found this bug report and 
applied this patch to my local pbuilder-dist copy:
http://bazaar.launchpad.net/~p8n/ubuntu-dev-tools/othermirror_fixes/revision/1421

Sanity restored. Thanks, Per Carlson! Maybe we can get at least the bug
fix commit into ubuntu-dev-tools?

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

Title:
  pbuilder-dist: Local archives othermirror overridden by later
  othermirror

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1314076/+subscriptions

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

[Bug 1360026] Re: Libav11 for Utopic

2014-09-03 Thread Florian W.

To clarify:
- So in Debian, all the packages in testing are now built against libav11 
AFAICT.

I actually meant:
The packages that are both in sid and in testing were successfully rebuilt 
against libav11. However, they are still in sid and waiting to migrate. :-)

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

Title:
  Libav11 for Utopic

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

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

[Bug 1360026] Re: Libav11 for Utopic

2014-09-03 Thread Florian W.

So in Debian, all the packages in testing are now built against libav11 AFAICT.
I (as a user) hope we can still get libav11 for Utopic.

In case this helps with your decision, these are the packages in sid
which are not built against libav11 (yet?):

- bino (unrelated to libav, some gettext related version mismatch)
- gnash (probably unrelated, FTBFS on armel because armel has std::future 
issues, and FTBFS on mips for whatever reason)
- gstreamer0.10-ffmpeg (FTBFS since libav9)
- jitsi (unrelated, complains about invalid -d command line option for apt … ?!)
- mrpt (there was no attempt to build against libav11 for any main arch yet, 
since there seem to be unrelated build issues on some arches. Building on alpha 
architecture at ports.debian.org against libav11 succeeded recently.)
- taoframework (language bindings that need updating for libav9+. Upstream 
probably cared about ffmpeg only and is dead now anyway.)
- visp (probably unrelated, test suite failure on powerpc)
- zoneminder (FTBFS since libav10 at least, still using CODEC_ID_*)

I'm not sure if Ubuntu carries any additional packages that would fail
to build against libav11. Also not sure about the current Ubuntu state
of the packages I mentioned. Maybe some of them need to be dropped from
the archive.

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

Title:
  Libav11 for Utopic

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

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

[Bug 1360505] Re: Security fixes from 36.0.1985.143 and 37.0.2062.94

2014-09-03 Thread Florian W.

This is fixed, right? I just got updated to 37 through update-manager. Thanks a 
lot, Chad :-)
I'm not closing it because it's not my bug, but I guess it can be closed.

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

Title:
  Security fixes from 36.0.1985.143 and 37.0.2062.94

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1360505/+subscriptions

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

[Bug 1363069] Re: Segfault running "minidlnad -d" in 14.04 docker container

2014-08-29 Thread Florian W.

Yes, that's the commit and Katsuhiko TAKAHASHI's comment.

I haven't contacted Benoît regarding this issue, as I haven't received a
response to my mail from last year about updating the package from
1.0.24 to 1.1.x. He is either Missing In Action, or he's too busy to
reply to minidlna mails (or gmail ate my/his mail).

Obviously, there was one package upload by Benoît since then (which
happened right after some DD threatened to highjack the package because
it was outdated and Benoît appeared to be MIA), so there's some hope he
can continue to do the maintainer job once he finds some time for it.
Otherwise, I guess the MIA team is going to orphan the package sooner or
later (or force a co-maintainer) and some other DD will hopefully fix
the few low-hanging bug reports. Anyway, I still consider him MIA and
won't try to contact him, so feel free to give it a try. :-)

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

Title:
  Segfault running "minidlnad -d" in 14.04 docker container

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

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

[Bug 1363069] Re: Segfault running minidlna in 14.04 docker container

2014-08-29 Thread Florian W.

This is unrelated to docker, it's a bug in a minidlna patch that was
added for Debian to possibly allow using logrotate for minidlna.
However, according to a Debian bug report, the log-reopen on signal does
not actually work due to a mistake in the patch, since the log-reopen
function is not called on receiving the logrotate signal (SIGUSR1 or
maybe SIGHUP, don't remember).

Since the patch can't handle logfilename=NULL (i.e. log to stdout),
Debian and Ubuntu minidlna versions crash when using the -d option.

I reported this to Debian some time ago: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=749265

** Bug watch added: Debian Bug tracker #749265
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749265

** Also affects: minidlna (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749265
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Segfault running minidlna in 14.04 docker container
+ Segfault running "minidlnad -d" in 14.04 docker container

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

Title:
  Segfault running "minidlnad -d" in 14.04 docker container

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

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

[Bug 1359615] Re: [precise] critical: flash stopped working after last update

2014-08-29 Thread Florian W.

Chromium is not in "main", i.e. it's officially unsupported by
Canonical. Formally, only approved Ubuntu community members (MOTUs)
support  chromium in Ubuntu, while Canonical does  not guarantee any
support at all.

That's the formal aspect at least. In practice, it seems like a
Canonical employee, Chad Miller, thankfully does most (all?) of the
Chromium work. It's a pretty important package after all, but as you can
tell from the not quite optimal security support (still 50+ open
security vulnerabilities right now and generally lagging a few weeks or
months behind with security fixes), it's on a "best-effort" basis. Maybe
Chad does the work in his free time, or it's just a low priority work
task for him. So don't expect an official statement from an Ubuntu
representative because formally, Chromium is not a part of Ubuntu that
Canonical cares about. Use Firefox which is in "main" and the default
browser if you want Canonical support (or maybe if you can pay some
signficant amount of money, Canonical would offer to support Chromium
for you).

It is important to note that shipping Chromium in a distro is very
difficult. Google seems to care about their own packaging, and that's
it. It's not an easy upstream to work with. It has bundled source copies
of libraries, until some time ago not even official release tarballs,
it's a very fast moving target and there is no backwards compatibility
for anything.

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

Title:
  [precise] critical: flash stopped working after last update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359615/+subscriptions

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

[Bug 1359615] Re: [precise] critical: flash stopped working after last update

2014-08-27 Thread Florian W.

Well, I didn't push the update. I'm just a user. But if Ubuntu didn't
push newer chromium releases to stable, there'd be a ton of security
flaws by the time even the next STS Ubuntu release is published 6 months
later.

And that would basically mean that any user who cares at least a little
bit for the security of his operating system would be unlikely to use
the Ubuntu chromium. I'd actually switch to Arch Linux completely in
that case, since I don't want the Chrome compiled by Google and trying
to find up to date PPAs or compiling myself appears to be more work than
just fixing the occasional Arch breakage.

The only sane thing any responsible distribution can do about chromium
is to either NOT package it at all (this is what Fedora does), or ship
the latest stable chromium at all times. If they just ship whatever was
the latest chromium at the time of distro release, their users would be
at risk and most users wouldn't even realize how dangerous it is to use
the distro packaged browser.

So yeah, this is a very difficult situation and I agree it's unfortunate
that plugins have stopped working. However, this is not an "experiment",
it's a required security update. Just shipping chrome 34 without the
fixes would be irresponsible and unprofessional, it's almost like still
using Windows XP today.

If you really want 34 back, I'd recommend you to start backporting all
the security fixes from 35, 36 and 37 to version 34. Maybe Ubuntu would
be willing to ship your 34 + backported fixes. Better ask them first. If
you can't do that, you could pay someone to do it, but that will be
pretty expensive I guess seeing how there are ~50-100 issues in chromium
34 to be fixed. :)

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

Title:
  [precise] critical: flash stopped working after last update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359615/+subscriptions

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

[Bug 1353185] Re: Chromium 36 upgrade will not execute

2014-08-27 Thread Florian W.

Michael Gilbert of Debian apparently carries some patches for chromium
that supposedly get rid of SSE2 instructions in the Debian chromium
package (at least in experimental?).  User opera posted a link to the
corresponding bug report in Debian. I'm not sure what the status of this
is or if Ubuntu would be willing to use the same patches, as they seem
pretty untested and impact/maintenance burden for future chromium
releases is not clear.

I wouldn't recommend using Chromium 34, as each of 35, 36 and 37 has a
lot of security fixes that are not in 34. So that would be somewhat
dangerous. I also don't know about an easy way to revert to 34, as most
PPAs or other repositories are probably updated by now. Maybe you can
find the old deb files somewhere.

Consider using a different browser :/

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

Title:
  Chromium 36 upgrade will not execute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1353185/+subscriptions

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

[Bug 1360505] Re: Security fixes from 36.0.1985.143 and 37.0.2062.94

** Summary changed:

- Security fixes from 36.0.1985.143
+ Security fixes from 36.0.1985.143 and 37.0.2062.94

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

Title:
  Security fixes from 36.0.1985.143 and 37.0.2062.94

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1360505/+subscriptions

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

[Bug 1359615] Re: [precise] critical: flash stopped working after last update

I'm sorry, you don't have option 3). Only after upgrading to Trusty.
Pepperflash is not available in Precise.

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

Title:
  [precise] critical: flash stopped working after last update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359615/+subscriptions

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

[Bug 1359615] Re: [precise] critical: flash stopped working after last update

There is no way (or at least no way that does not involve forking
chromium and quite a lot of coding work) to get chromium to work with
Adobe Flash and have no security issues at the same time. Ubuntu decided
to prefer breaking flash over having precise users exposed to a growing
number of threats. This is simply because chromium no longer supports
NPAPI on Linux as you have mentioned, but old chromium versions are a
security hell.

You have four options:
1) Use e.g. firefox + NPAPI Adobe Flash for your flash viewing pleasure.
2) Install Google Chrome (instead of chromium) that comes with bundled 
pepperflash.
3) Install pepperflash separatly (sudo apt-get install 
pepperflashplugin-nonfree) and use it with chromium. Please note that 
pepperflash DOES NOT AUTO UPDATE, even though it has critical security updates 
regularly. Use "sudo update-pepperflashplugin-nonfree --status" to see if there 
is an update available, and "sudo update-pepperflashplugin-nonfree --install" 
to install the update.
4) Don't use flash. Obviously that's not always an option, but some sites like 
youtube have HTML5 alternatives ready to be enabled.

This is not a bug, it's the intended deprecation of an old plugin API.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Invalid

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

Title:
  [precise] critical: flash stopped working after last update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359615/+subscriptions

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

[Bug 1360505] Re: Security fixes from 36.0.1985.143

37.0.2062.94 has 50 more security fixes:

http://googlechromereleases.blogspot.de/2014/08/stable-channel-
update_26.html

CVE-2014-3176, CVE-2014-3177 (critical, sandbox breakage)
CVE-2014-3168
CVE-2014-3169
CVE-2014-3170
CVE-2014-3171
CVE-2014-3172
CVE-2014-3173
CVE-2014-3174
CVE-2014-3175 ("various fixes")

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3168

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3169

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3170

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3171

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3172

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3173

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3174

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3175

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3176

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3177

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

Title:
  Security fixes from 36.0.1985.143

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1360505/+subscriptions

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

[Bug 1353185] Re: Chromium 36 upgrade will not execute

Frederick, there was no chromium 35 in Ubuntu if I remember correctly,
so you are probably talking about Chromium 34 (that was the current
version in Ubuntu until a few weeks ago when it was upgraded to 36).
Chromium 35 has stopped supporting non-SSE2 Linux systems because,
according to Google, there are exactly 0 Linux users without SSE2. I'm
sorry, you don't exist.

See the chrome bugtracker link above:
> The good news is that for Linux (as opposed to for Windows), there are zero 
> pre-SSE2 users
> out there, so bumping the minimum requirement from P3 to P4 [..]

Also, AMD processors apparently do not exist in the Google universe, so
now we have Pentium 4 as the minimum CPU requirement. :-)

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

Title:
  Chromium 36 upgrade will not execute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1353185/+subscriptions

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

[Bug 1343081] Re: chromium: missing "http://" in URL bar on non-ssl http URLs