SRU proposal for precise
** Patch added: "precise_firefox_44.0+build3-0ubuntu1.12.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1538724/+attachment/4561091/+files/precise_firefox_44.0+build3-0ubuntu1.12.04.1.debdiff
--
You received this bug notification because you are
Hello Max,
My guess (supported by a test I made in a test environment) is the cause of the
problem are those lines under iface bond0:
pre-ip ifup eth2
pre-up ifup eth3
Those are most probably causing a deadlock, since the new release aims to fix
the race condition causing the or
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage notifications about this bug go to:
https://bugs.launchpad.net/
I have backported the fix to trusty in my ppa.
Unfortunately I was not able to reproduce this issue (although my tests
are ongoing). With that being said I would really appreciate anyone that
is affected by this issue to give it a try and let me know whether the
backport fixed that for them.
The
Since I've added the fix to bug 1532722 and after several days of
testing I did not observe any other issues on Trusty and Wily I'm
tagging this as verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ub
** Attachment added: "Full Xorg.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1554004/+attachment/4591440/+files/Xorg.1.log
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Su
Public bug reported:
There is a segfault in Xorg.log visible when starting X on Trusty 14.04
with the following hardware:
00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. VX900 Graphics
[Chrome9 HD] [1106:7122] (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology
I have verified both Trusty and Wily. The verification was automated
cyclic rebooting of a VM containing 3 NICs - 2 of them were used in
bonding in active-backup. Before the fix has been implemented this test
failed with some interfaces uninitialized or the bonding mode being
wrong (the default rou
SRU proposal for Wily (extended with fix to bug #1532722)
** Patch added: "wily_ifupdown_0.7.54ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548423/+files/wily_ifupdown_0.7.54ubuntu3.debdiff
--
You received this bug notification because you are
SRU proposal for Trusty (extended with fix to bug #1532722)
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548422/+files/trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff
--
You received this bug notification b
** Patch removed: "wily_ifupdown_0.7.54ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548423/+files/wily_ifupdown_0.7.54ubuntu3.debdiff
** Patch removed: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifu
Updated SRU proposal for Trusty (fix to bug #1532722)
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548430/+files/trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff
--
You received this bug notification because
New SRU proposal for Wily (with fix to bug #1532722)
** Patch added: "wily_ifupdown_0.7.54ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548431/+files/wily_ifupdown_0.7.54ubuntu1.2.debdiff
--
You received this bug notification because you are
Public bug reported:
The fix for bug #11395 / CVE-2015-5252
https://git.samba.org/?p=samba.git;a=commitdiff;h=7606c0db257b3f9d84da5b2bf5fbb4034cc8d77d
locked down the path checks in check_reduced_name[_with_privilege]() to prevent
unintended access via wide links.
The new checks do not correctl
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545750
Title:
Access denied if the share path is "/"
To manage notifications about this bug go to:
https://bugs.launchpad.net/samba
SRU proposal for Precise.
** Patch added: "precise_samba_3.6.3-2ubuntu2.14.debdiff"
https://bugs.launchpad.net/samba/+bug/1545750/+attachment/4572183/+files/precise_samba_3.6.3-2ubuntu2.14.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
SRU proposal for Trusty.
** Patch added: "trusty_samba_4.1.6+dfsg-1ubuntu3.14.04.11.debdiff"
https://bugs.launchpad.net/samba/+bug/1545750/+attachment/4572182/+files/trusty_samba_4.1.6+dfsg-1ubuntu3.14.04.11.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bug
SRU proposal for Wily.
** Patch added: "wily_samba_4.1.17+dfsg-4ubuntu3.2.debdiff"
https://bugs.launchpad.net/samba/+bug/1545750/+attachment/4572181/+files/wily_samba_4.1.17+dfsg-4ubuntu3.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Debdiff for Xenial.
** Description changed:
- The fix for bug #11395 / CVE-2015-5252
+ [Impact]
+
+ * User is denied access when trying to access a share "/"
+
+ [Test Case]
+
+ * Setup a Samba server
+
+ * Add a share with path "/"
+
+ * Try to access the share
+
+ [Regression Potenti
Hello Paul,
The locking mechanism was implemented to avoid race conditions in ifupdown
(such as the one reported as bug #1337873). Unsetting the variable may lead to
unexpected consequences. I belive a proper solution would be to modify wpa-roam
implementation to play along with ifupdown.
Could
Paul, I think that the real cause here is that (by looking into
debian/ifupdown/functions.sh) wpasupplicant depends on the previous single-file
ifstate.
Currently, for the sake of the locking mechanism, it has been split into an
individual ifstate.$IFACE per interface, while wpasupplicant still
** Changed in: ifenslave-2.6 (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015199
Title:
ifup does not work as documented w
** Changed in: ifenslave-2.6 (Ubuntu)
Assignee: Dariusz Gadomski (dgadomski) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015199
Title:
ifup does not work as documented w
SRU proposal for Wily
** Patch added: "wily_gtimelog_0.9.2-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtimelog/+bug/1309428/+attachment/4573641/+files/wily_gtimelog_0.9.2-1ubuntu1.debdiff
** Description changed:
+ [Impact]
+
+ * The icon of gtimelog is replaced with the de
SRU proposal for Trusty
** Patch added: "trusty_gtimelog_0.9.1-2ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtimelog/+bug/1309428/+attachment/4573640/+files/trusty_gtimelog_0.9.1-2ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Patch added: "wily_gtimelog_0.9.2-1build2_fixed.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtimelog/+bug/1309428/+attachment/4573662/+files/wily_gtimelog_0.9.2-1build2_fixed.debdiff
** Patch removed: "trusty_gtimelog_0.9.1-2ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+sou
** Patch added: "trusty_gtimelog_0.9.1-2ubuntu1_fixed.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtimelog/+bug/1309428/+attachment/4573661/+files/trusty_gtimelog_0.9.1-2ubuntu1_fixed.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Paul, I have finally managed to reproduce this on Trusty. The ifstate
looks to be a false trail.
However, please note that with 0.8.10ubuntu1 on Xenial this problem does
not occur.
I am investigating which change needs to be backported. I will keep you
updated.
--
You received this bug notifica
Hello Paul,
I have identified the cause of the problem and prepared a fix.
My tests show that it solves the issue for Trusty and Wily (while Xenial does
not require a fix since it's ifupdown has been synced with Debian to a version
containing a fix already).
Could you please revert your wpasuppl
Paul, the patch looks good.
It's better than making those scripts compatible with new style of
ifstate. Fixing ifstate-based implementation would not cover replacing
one logical iface with another, while your implementation does it.
Good luck with pushing this to Debian.
--
You received this bu
Adding SRU proposal for Wily.
** Attachment added: "wily_ifupdown_0.7.54ubuntu1.3.dsc"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+attachment/4574280/+files/wily_ifupdown_0.7.54ubuntu1.3.dsc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Adding SRU proposal for Trusty.
** Description changed:
+ [Impact]
+
+ * In some configurations recurrent ifup/down calls are broken due to a
+ false-positive recursion detection.
+
+ * In certain situations it leaves interfaces unconfigured (in this
+ case: WLAN interface connected to WiFi n
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for ifupdown #1337873
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538724
Title:
GraphicsCriticalError: |[0][GFX1]: Unknown cairo format 3
To manage notifications about this bug go to:
https://bugs.
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538724
Title:
GraphicsCriticalError: |[0][GFX1]: Unkn
Fix for Xenial.
** Description changed:
+ [Impact]
+
+ * In some configurations (like VM connected via vnc) prevents from
+ using Firefox at all (crash on launch).
+
+ [Test Case]
+
+ * Setup an Ubuntu VM with a VNC server
+ * Connect to it with a vnc client
+ * Launch the default Firefox
SRU proposal for Trusty
** Attachment added: "trusty_firefox_44.0+build3-0ubuntu1.14.04.1.dsc"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1538724/+attachment/4558380/+files/trusty_firefox_44.0+build3-0ubuntu1.14.04.1.dsc
--
You received this bug notification because you are a mem
SRU proposal for Wily
** Patch added: "wily_firefox_44.0+build3-0ubuntu1.15.10.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1538724/+attachment/4558379/+files/wily_firefox_44.0+build3-0ubuntu1.15.10.1.debdiff
--
You received this bug notification because you are a member
SRU proposal for Trusty
** Patch added: "trusty_firefox_44.0+build3-0ubuntu1.14.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1538724/+attachment/4558381/+files/trusty_firefox_44.0+build3-0ubuntu1.14.04.1.debdiff
--
You received this bug notification because you are a
Ashish: I have prepared a build in my ppa. To use it please follow these steps:
sudo add-apt-repository ppa:dgadomski/lp1538724
sudo apt-get update
sudo apt-get install firefox
This should upgrade the firefox for you to the fixed version (until such
a fixed version is released officially).
Good l
TWC Service verified trusty. Adding correct tag.
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect udev-fallback-graphics.conf
To manag
While I was working on a packport of this feature I have discovered a
bug in the gtk printing backends (affects series 2 and 3) that may cause
random crashes due to buffer overflow.
I have reported the issue upstream and am working on backports to utopic
and trusty (gtk2 and gtk3).
https://bugzil
SRU proposal for trusty.
Contains feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: "trusty_gtk+3.0_3.10.8-0ubuntu1.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4222406/+files/trusty_gtk%2B3.0_3.10.
SRU proposal for trusty.
Contains feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: "trusty_gtk+2.0_2.24.23-0ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4222405/+files/trusty_gtk%2B2.0_2.24
SRU proposal for utopic
Contains the feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: "utopic_gtk+2.0_2.24.24-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4222404/+files/utopic_gtk%2B2.0_2.2
SRU proposal for Utopic
(https://bugzilla.gnome.org/show_bug.cgi?id=73)
** Patch added: "utopic_gtk+3.0_3.12.2-0ubuntu11.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4222403/+files/utopic_gtk%2B3.0_3.12.2-0ubuntu11.debdiff
--
You received this bug no
The fix has been pulled in by the upstream:
https://git.gnome.org/browse/gtk+/commit/?id=15dbadf38992aa09364f0dd06a71a51b99b6e800
And the upstream bug (https://bugzilla.gnome.org/show_bug.cgi?id=73)
has been marked as resolved fixed.
--
You received this bug notification because you are a me
omski/linux-mst.
I will appreciate any feedback.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Description changed:
[Impact]
- - When you attempt to locate/search for a particular user most projects
+ - When you attempt to locate/search for a particular user most projects
will only provide a simple list of users with no filtering tools, this
can quickly become unsustainable if
Vincent, what you could do is to take a look at this instruction:
https://01.org/linuxgraphics/node/358
Based on this you could:
sudo add-apt-repository ppa:dgadomski/linux-mst
sudo add-apt-repository ppa:xorg-edgers/ppa
sudo apt-get update
sudo apt-get install linux-image-3.16.0-19-generic # th
Hi guys, there is an updated kernel version in my ppa (should become available
any minute):
* trusty: 3.16.0-23.31~14.04.2hf73386v20141028b1
* utopic: 3.16.0-23.31hf73386v20141028b1
I would really appreciate giving any of those a try. The procedure
should be as previously:
1. install the kernel,
Thanks Mike. If your docking station is the same as Elvis mentioned
above then this feature should (eventually) make it working.
Can you please double-check:
$ apt-cache policy linux-image-3.16.0-23-generic
whether the installed version you use is:
Installed: 3.16.0-23.31~14.04.2hf73386v20141028b1
/plymouth/commit/?id=e982dc255c0f471e67eb7bd0858c170d103d39ce)
but according to the plymouth debug log (attached) radeon fails to open.
** Affects: plymouth
Importance: Unknown
Status: Unknown
** Affects: plymouth (Ubuntu)
Importance: Undecided
Assignee: Dariusz
Thanks Matthew.
All the changes from David's backport for 3.16 branch has been cherry
picked to the kernel in my ppa, so I would appreciate any feedback from
using a build from his sources.
If it works with his version then something in Ubuntu kernel may be
blocking this feature.
If anyone is ab
Elvis, thank you for checking this. I assume that the multi-display
configuration did not work for you as well as the network?
Have you tried running utopic kernel backport on trusty before? Maybe just this
backport does not work.
Does anybody (with the hardware) have utopic (14.10) installation
Matthew, can you please confirm that you don't have 'mirroring'
parameter anywhere on the kernel commandline?
# grep mirror /proc/cmdline
Can you please also post output of:
# find /sys/kernel/debug -name i915_dp_mst_info -exec cat {} \;
Thanks!
--
You received this bug notification because yo
aexl, as long as the docking station uses your intel card via a
displayport 1.2 then this may be the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.2 MST support is
Thanks Matthew!
I will review the changes to trusty and try to backport this feature to
3.13 (to avoid network problems).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.
Wouter, I would appreciate anyone with a suitable hardware to stay with
trusty for a couple of days more until we have a working solution.
But if you need the MST feature please move to utopic and give a try the
same build Matthew found working.
There is a new 3.13 build for trusty ongoing in my
That's a good point Matthew. I should have been more clear about it.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.2 MST support is missing in the Intel drive
Hello everyone,
The last build was successful so there is a trusty kernel
(3.13.0-39.66hf73386v20141030b1) to be tested in my ppa.
I will appreciate your feedback.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Matthew, did you make any investigation why it was not working for you
on your first laptop?
Please share any observation that may help other people here.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Thank you Elvis.
Can you please post your output of:
# find /sys/kernel/debug -name i915_dp_mst_info -exec cat {} \;
Have you tried installing the linux-image-extra package for the kernel
you previously tested (3.0.16 - the one that left you without a
network)? If not, I would appreciate checking
What I was referring above was the output of:
# find /sys/kernel/debug -name i915_dp_mst_info -exec cat {} \;
on my system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1
Thank you for the information Matthew.
I didn't notice that because for me without the necessary hardware those
files are empty all the time.
Elvis, did you get any results after installing linux-image-extra?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs
Hello Elvis,
Was it any different for you with the 3.13 kernel?
Thanks,
Dariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.2 MST support is missing in the Intel dri
** Description changed:
+ SRU Justification:
+
+ Impact: Many users expect the possibility to use the DP1.2 MST feature which
+ enables them to use a number of different display setups: daisy-chaining
+ DP1.2 displays, some 4K displays appearing as 2 separate displays, 3D
displays.
+ This howeve
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386170
Title:
Libreoffice startup center shorcut broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
SRU proposal for precise
** Description changed:
+ [Impact]
+
+ * This bug is likely to cause a crash with a SEGV in multithreading
+ applications doing many memory deallocations with ATOMIC_FASTBINS
+ feature enabled.
+
+ [Test Case]
+
+ * Since this is a race condition issue there is no si
** Description changed:
[Impact]
- * This bug is likely to cause a crash with a SEGV in multithreading
+ * This bug is likely to cause a crash with a SEGV in multithreading
applications doing many memory deallocations with ATOMIC_FASTBINS
feature enabled.
[Test Case]
- * Since
Hi Vincent,
There is a 3.13.0-39.66hf73386v20141030b1 version available for trusty. You
should be able to install it with:
sudo add-apt-repository ppa:dgadomski/linux-mst
sudo apt-get update
sudo apt-get install linux-image-3.13.0-39-generic
linux-image-extra-3.13.0-39-generic
And
apt-cache pol
David, unfortunately I don't see any updates in this area in upstream
erlang.
At this point I can suggest you using either:
1) the version from my ppa [1] or
2) the workaround from comment #6
I will update this bug as soon as the fix will be merged to the upstream
erlang.
[1] ppa:dgadomski/erlan
Mathieu: I forgot to mention it in the descripiton. To observe this
problem you first need to apply Colin's patch for bug #1386113
(https://launchpadlibrarian.net/188412508/fix-keyfile-error.patch).
Thanks for looking at this!
--
You received this bug notification because you are a member of Ubu
Krzysztof, you don't have to downgrade the kernel. This is only
necessary with the open-source Intel drivers.
I'm not sure if AMD drivers support Displayport 1.2 MST feature, but I
know that NVIDIA drivers do support it and it does not require anything
special about the kernel.
Please browse your
Ben, are you able to compare this behaviour with the 3.17 kernel (e.g.
from debs available at [1])?
If the behavior is consistent between the two kernel version - it's another
issue.
If 3.17 behaves better than the 3.16 you were using - this is the right place
to handle the problem.
[1] http://
@Ben: if you were using an official Utopic 3.16.0-28-generic kernel,
please note that it does NOT contain support for multiple displays using
MST, so it will not be possible to have non-mirroring displays.
If it is not from the official Utopic repository, please share the
origin of this kernel.
@
I have found an interesting merge request for erlang [1].
Looks like during the implementation it's author has fixed the
assumption that if epmd is built with IPv6 support it losses the
possibility to bind with IPv4 address.
I have cherry-picked that change and applied it to Ubuntu's erlang-base.
Ben, I have updated the kernel version in my ppa. Could you please test
version 3.16.0-28.37hf73386v20141212b2 and compare the supsend/resume
behavior with what you observer using 3.17?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- Inconsistent behaviour between automated uniquity launch and manual launch
with presseed
+ Ubiquity ignoring preseed file contents
** Summary changed:
- Ubiquity ignoring preseed file contents
+ Desktop installer ignoring preseed file passed by kernel command line
** Desc
*** This bug is a security vulnerability ***
Public security bug reported:
In Precise after new HWE kernel was released the following message was
displayed to the user:
"New hardware support is available [Install]".
This is perfectly correct, but I have received some complaints from
sysadmins t
"New important security and hardware support update" sounds good to me.
Putting there a "More info" link there sounds like a perfect idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1402706
Title:
Colin, thanks for the hint.
I have made sure that the disk is clear (all partitions erased, no VGs
or LVs present) before running scenario 2.
Unfortunately the workaround did not change the outcome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
There is a line in the syslog:
> Dec 17 18:00:28 ubuntu log-output: No volume groups found
and then a couple of seconds later:
> Dec 17 18:00:39 ubuntu partman-lvm: Physical volume
> "/dev/mapper/sda5_crypt" successfully created
> Dec 17 18:00:39 ubuntu partman-lvm: Volume group "crypt" succe
/var/log/installer/debug from the 2nd attempt (with workaround).
** Attachment added: "debug"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1386153/+attachment/4283017/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
syslog from the 2nd attempt (with workaround).
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1386153/+attachment/4283016/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
syslog with set -x added to partman-
base/choose_partition/partition_tree/do_option
** Attachment added: "syslog.set-x"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1386153/+attachment/4283430/+files/syslog.set-x
--
You received this bug notification because you are a member of Ub
Thanks Marcin.
I got some feedback from the feature author on the erlang-bugs mailing
list. He will make a new pull request against the latest erlang.
Hopefully it will get merged and we will be able to cherry-pick it and
deliver as SRU to Ubuntu.
--
You received this bug notification because yo
Updated debdiff against eglibc_2.15-0ubuntu10.9.
** Patch added: "precise_eglibc_2.15-0ubuntu10.10.debdiff"
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1020210/+attachment/4299972/+files/precise_eglibc_2.15-0ubuntu10.10.debdiff
** Patch removed: "precise_eglibc_2.15-0ubuntu10.8.debd
The upstream gtk is considering backporting this change to gtk2: [1]
What I find most important in the description is:
With regards to the importance of having this only fixed in GTK 3. To be
honest, as long as firefox still uses GTK 2 in most distributions this fix is
more important for our users
I believe this is the commit in question:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0b0a84154eff56913e91df29de5c3a03a0029e38
Looks like a good canditate for considering a cherry-pick.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Carl, I have backported the fixes to trusty kernel. Could you please
give them a try in your environment?
The build is available in my PPA (ppa:dgadomski/kernel-nfs).
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Krzysztof, looks like you installed the kernel correctly, you are simply
booting into a newer kernel without the feature.
Please make sure you boot using 3.13.0-39.
To do so please choose kernel 3.13.0-39 from the GRUB menu during the
boot of your computer.
You can find more information how do d
Krzysztof, you should be using 3.13.0-39 patched by me (the newer
version is the vanilla Ubuntu kernel which does not support MST).
Regarding your question about cables: you should not worry about that.
According to [1]:
> Despite what you may read, there is no such thing as a
> DisplayPort 1.1
Sorry Krzysztof, this bug is dedicated only to supporting Intel VGAs, so
none of the packages here would solve your problem.
Since you use the proprietary AMD drivers you should examine the
features their driver support and follow their instructions.
Sorry, I have missed the AMD VGA part in the l
Hi Ben,
I have uploaded new kernel build (version:
3.16.0-26.34hf73386v20141126b1). Could you please give it a try?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort
Ben, according to your logs:
> [ 11.322] Current Operating System: Linux dib 3.16.0-25-generic
> #33hf73386v20141106b1-Ubuntu SMP Thu Nov 6 14:20:03 UTC 2014 x86_64
you have used the previous kernel again. Maybe you made your attempt
right before the packages were published in my ppa.
Looks like
I'm glad it works for you Ben.
To everyone: if we want to get this to the Ubuntu kernel we need more
feedback from people testing this.
Please give the Utopic kernel (3.16.0-26.34hf73386v20141126b1) a try and
leave a comment here. This is a big feature and it would help us to have
it tested.
Tha
Elvis, no, sorry, not yet. I was focusing on Utopic as it is the first
step to get it accepted to Ubuntu.
What worries me is that the current build for trusty 3.13 worked for
Wouter (comment #78) and does not work for you. That makes me wonder if
your configuration is even supported by this featur
Elvis, the only thing I was able to do for you right now is to build you
an Utopic kernel for Trusty (the same that was working for Ben).
Please find it in my ppa. The version number is
3.16.0-26.34~14.04.1hf73386v20141127b1.
Please remember to use also the extras package.
--
You received this
@Björn: my tests show that it fixes the issue, however I still did not
get any feedback from the reporter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386170
Title:
Libreoffice startup center sho
501 - 600 of 821 matches
Mail list logo
