Public bug reported:
After playing around for some time (usually from a couple of minutes to
about 45 minutes) my Android phone becomes unusable through adb running
on Ubuntu.
All calls to adb (e.g. adb devices, adb kill-server) just hang and they don't
respond to Ctrl+C etc. The adb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946562
Title:
Multiple 'task blocked for more than 120 seconds' messages in dmesg
To manage notifications about this bug go to:
Shanekpiper - Yes, I've originally installed 11.04, but later I've
upgraded to 11.10 and eventually to 12.04. It was working correctly all
the time up to upgrade to 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've upgraded to kernel 3.2.0-18-generic today and after about 40
minutes the problem appeared again. Changing back to Confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I observe a somewhat buggy behavior in comparison to 11.10. I have a
desktop PC with audio out on the back (I use it for speakers) and audio
out in the front (used for headphones). I have both: speakers and
headphones connected all the time. In 11.10 it used to provide output
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927704
Title:
No sound through speakers on 12.04
To manage notifications about this bug go to:
I have an update on the above scenario:
5. Suspend-to-ram, unplug speakers and wake computer.
Without unplugging speakers I still get no sound after waking the computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
During the last check I've noticed that the problem concerns more than
just an Android phone through adb. After observing those messages Task
blocked... I cannot use any USB mass storage devices at all. I've tried
to plug in 2 USB memory sticks just to observe that those are not
automatically
Unfortunately I was not able to test the mainline kernel. I could not
get X.org to work with it. My graphics card (Nvidia GF GT240) crashes
with the nouveau driver and the official NVIDIA driver was refusing to
install.
Adding kernel-unable-to-test-upstream tag.
** Tags removed:
Thanks Shanekpiper.
Unfortunately adding
options snd-hda-intel model=asus
to file
/etc/modprobe.d/alsa-base.conf
and rebooting afterwards did not help.
After the reboot with headphones plugged in I can't get any output from
speakers no matter whether I plug in or out the headphones jack.
--
I'm sorry, I was not able to boot with mainline kernels 3.2.7-3.2.9.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946562
Title:
Multiple 'task blocked for more than 120 seconds' messages in dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951440
Title:
vim-gnome ignores colorscheme setting from vimrc
To manage notifications about this bug go to:
Public bug reported:
For some time (about 2-3 weeks) I observe a regression in vim-gnome
package.
For some reason it ignores the colorscheme setting on startup.
I have tested it with a simple one-line ~/.vimrc file:
colorscheme desert
Each time I start vim it has theme 'default' set, after I
Public bug reported:
Whenever I try to configure Ubuntu One with an existing account (I press
the Sign me with an existing account button in the Ubuntu One Control
Panel) I stuck on the ubuntu-sso-login-qt (that's the window title)
screen. I provide my e-mail and password but the Sign In button
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951584
Title:
Cannot sign in to Ubuntu One - Sign in button disabled
To manage notifications about this bug go to:
This bug does not affect the console vim application. Running
'colorscheme' command in vim returns the requested 'desert' scheme. The
issue concerns only vim-gnome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem persist on the newest kernel. Changing back to Confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946562
Title:
Today I have upgraded the kernel to linux-image-2.6.38-10-generic. It
seems the issue is fixed. To boot takes around 30s as before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760114
Title:
Public bug reported:
Binary package hint: linux-image
After upgrading from Ubuntu 10.10 to 11.04 Beta boot time increased
significantly - from about 20-30 seconds to over 2 minutes.
There is a strange gap in the dmesg log (please see the attachments)
between around 0.9 and 80 seconds.
** Attachment added: uname-a.log
https://bugs.launchpad.net/bugs/760114/+attachment/2031786/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760114
Title:
Increased boot time
--
Added lspci output.
** Attachment added: lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/760114/+attachment/2031819/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Added version.log.
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/760114/+attachment/2031820/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have tried the mainline kernel (linux-
image-2.6.39-020639rc3-generic_2.6.39-020639rc3.201104120912_amd64.deb)
and the behavior is exactly the same. However when using the previous
10.10 kernel (2.6.35-28-generic) under 11.04 the boot time is under 30
seconds.
--
You received this bug
Public bug reported:
Almost each time I login to Unity using LightDM after some time (from 5
min to about 2-3 hours) my session crashes and I am taken to the login
lightdm screen again. It does not matter what applications are running -
sometimes I get it when I have only the browser running,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031376
Title:
Unity/LightDM session crashes - login screen appears
To manage notifications about this bug go to:
After it happened again I was able to observe that the process which
exited was /usr/bin/X.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031376
Title:
Unity/LightDM session crashes - login screen
I consider this invalid now. I think it was the fault of my BIOS settings. I
have changed the Onboard Devices / Front Panel Select setting from 'AC97' to
'HD Audio' and the jack detection behaves as expected:
1. I boot with my headphones plugged in to the front panel - I have no sound
through
@madbiologist: I experience exactly the same behavior on 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/763052
Title:
Ubuntu can't boot on nvidia GeForce GT240 with nouveau drivers
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946562
Title:
Multiple 'task blocked for more than 120 seconds' messages in dmesg
Public bug reported:
The update manager segfaults when trying to upgrade from 13.04 to 13.10.
Steps to reproduce:
1. $ sudo update-manager -c -d
2. Press the 'Upgrade...' button.
Expected result:
Another window appears asking to confirm the upgrade.
Actual result:
After message on checking the
Hello Robert,
Thank you for working on this issue. I want you to know that we have a
customer waiting for a fix to this bug.
Please let me know if I could provide you help in development and/or
testing.
Regards,
Dariusz
--
You received this bug notification because you are a member of Ubuntu
Hello William,
Regarding your comment #20: did the contents of /proc/key-users when you
observe to issue somehow differ from the ones you posted in comment#19?
What I am trying to determine is whether for some reasons the quota is
hit on your machine when you observe the issue or is it caused by
William,
I'm sorry, but I cannot reproduce this issue with the kernels you
mentioned.
Are you able to provide me sosreport from the affected system?
You could also try adding -vvv option to your
/etc/request-key.d/id_resolver.conf to make it look like this:
create id_resolver * *
I have verified this on my machines, although I still wait for a
verification from a user.
I will update this issue after getting the confirmation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
SRU proposal for utopic (gtk+3.0)
** Patch added: gtk+3.0_3.12.2-0ubuntu8.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4214816/+files/gtk%2B3.0_3.12.2-0ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
SRU proposal for utopic (gtk+2.0)
** Description changed:
- i am printing from my ubuntu karmic to a windows box. everytime i print
- i get asked to input username and password to windows box, then the
- document gets printed. there is a remember password checkbox, but it
- keeps asking me when
SRU proposal for Utopic.
** Patch removed: precise_eiciel_0.9.8.1-3ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1361217/+attachment/4186845/+files/precise_eiciel_0.9.8.1-3ubuntu1.debdiff
** Patch removed: trusty_eiciel_0.9.8.1-3ubuntu1.debdiff
SRU proposal for precise.
** Patch added: eiciel_0.9.8.1-3ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1361217/+attachment/4215738/+files/eiciel_0.9.8.1-3ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
SRU proposal for trusty.
** Patch added: eiciel_0.9.8.1-3ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1361217/+attachment/4215737/+files/eiciel_0.9.8.1-3ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Robie, please find the corrected patches.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361217
Title:
GUI for managing ACL
To manage notifications about this bug go to:
** Changed in: xserver-xorg-video-intel (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/1104230
Title:
DisplayPort 1.2 MST support
@TWC Service Thank you for checking this.
** Tags removed: verification-needed
** Tags added: verification-done
--
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
@Marco
I am thinking about a fix for this:
* Add a setting to change the current behavior (e.g. Remember viewport focus)
* Before changing viewport save the currently focused window
* When coming back to a viewport instead of focusing the default window do:
i) if the new setting is enabled try to
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
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).
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
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
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
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
Public bug reported:
I have observed a strange behavior of pbuilder-dist while interacting
with remote files mounted with sshfs.
Reproducability: Always
Steps to reproduce:
1. Mount a remote directory containing your sources and *.dsc files locally via
sshfs:
$ sshfs username@ip-address
** Changed in: eiciel (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/1361217
Title:
GUI for managing ACL
To manage notifications
Adding SRU proposal for Precise.
** Patch added: precise_eiciel_0.9.8.1-3ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1361217/+attachment/4186845/+files/precise_eiciel_0.9.8.1-3ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Adding SRU proposal for Trusty.
** Patch added: trusty_eiciel_0.9.8.1-3ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1361217/+attachment/4186846/+files/trusty_eiciel_0.9.8.1-3ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Adding SRU proposal for Utopic.
** Patch added: utopic_eiciel_0.9.8.3-1ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1361217/+attachment/4186847/+files/utopic_eiciel_0.9.8.3-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
I think using 0.9.9 for utopic would be valuable since beside including
this feature it also contains some UI tweaks making the app more
compliant with Gnome HIG.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Iain, I have just finished testing the debian package on Utopic. Works
flawlessly. I think we can proceed with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361217
Title:
[FFe] GUI for
Hi Vincent,
If I understand correctly your docking station performs the role of a dp
mst hub (can you please confirm this with the documentation of your
docking station or provide its model to verify this online?), so it
should be a good setup to test.
Ideally to make this working you would need
Hi Elvis,
Looks like you have the perfect setup to test this case.
Please make sure you have ppa-purge installed so you can revert the
package updates if anything goes wrong.
Please follow these steps:
1. sudo add-apt-repository -y ppa:dgadomski/linux-mst
2. sudo add-apt-repository -y
VIncent, according to [1] this hardware is displayport 1.2 compatible.
Plus, the Display Port 1.2 adds the ability to daisy chain displays (4
displays via 1 connector).
However, I have not been able to determine whether this works in such a
way that it takes MST output from your laptop's
Hi Elvis, unfortunately I do not know that. Please consult your user's
manual. I haven't got access to those monitors. 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:
Thank you guys for testing this. Unfortunately I do not know the cause
with the wireless network problems. I was doing sanity tests of those
kernels on my trusty desktop (with a USB WiFi dongle) and my utopic
laptop (with built-in wifi). In both cases I was able to use my network.
This kernel is
Thanks Vincent. This confirm that probably what I have backported is not
enough to have full MST support. I will try to prepare an updated build
after reviewing David Airlie tree.
I will work on providing an update next week.
Thank you all for testing.
--
You received this bug notification
Public bug reported:
1. Affected release: precise (12.04)
2. Affected version: clvm 2.02.66-4ubuntu7.4
3. Steps to reproduce:
a Setup:
* SAN server serving 3 drives
* Cluster consisting of 2 nodes
b. Connect drives to the cluster (open-iscsi)
c. Configure clvm.
d. Create PV on all 3 drives.
I have investigated the possibility to backport the fix for this issue
from trusty (14.04). There has been a major refactoring of the locking
all over lvm between versions shipped with precise (2.02.66 patched to
2.02.72) and trusty (2.02.98).
The scope of backporting makes this operation risky
Assuming that:
* vg0 is the volume group in question
* lv0 is the logical volume
* sdc is the physical volume that needs to be freed
there is a workaround possible:
1. lvconvert --mirrorlog core -m 1 /dev/vg0/lv0
2. lvconvert --mirrorlog core -m 0 vg0/lv0 /dev/sdc
3. vgreduce vg0 /dev/sdc
--
Hello Elvis,
I have came across something that may interest you, here [1]. The Dell
support person there states that you should have the DSP 1.2 enabled
only on the primary monitor, on the secondary it should be disabled.
[1] http://en.community.dell.com/support-
** Tags removed: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315098
Title:
GUI for managing ACL
To manage notifications about this bug go to:
Public bug reported:
The udev-fallback-graphics.conf script tries to load vesafb module if
PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier.
The problem is that from kernel version 3.13.0-16.36 vesafb is compiled
in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the
fallback mode
** Changed in: udev (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/1367241
Title:
Incorrect udev-fallback-graphics.conf
To manage
Adding SRU proposal for Utopic.
** Patch added: systemd_208-8ubuntu3.debdiff
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201487/+files/systemd_208-8ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Adding SRU proposal for 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 manage notifications about this bug go to:
Adding SRU proposal for Trusty.
** Patch added: systemd_204-5ubuntu20.7.debdiff
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201485/+files/systemd_204-5ubuntu20.7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Adding SRU proposal for Precise.
** Description changed:
+ [Impact]
+
+ * When setting up primary display driver fails an attempt to load vesafb
+module is undertaken. This fails since from 3.13.0-16.36 version
+vesafb is compiled in the kernel (so no actual modprobing is needed).
+
** Also affects: systemd (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/1367241
Title:
Incorrect udev-fallback-graphics.conf
To manage
** 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.net/bugs/1104230
Title:
DisplayPort 1.2 MST support
** Changed in: systemd (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/1367241
Title:
Incorrect udev-fallback-graphics.conf
Thanks Martin for taking a look.
In my precise (12.04.5) install the default kernel is 3.13.0-32-generic, which
is affected by the issue:
$ grep FB_VESA /boot/config-3.13.0-32-generic
CONFIG_FB_VESA=y
In fact initially this has been reported by a CTS customer for precise.
--
You received this
Building vesafb as a module should still be possible.
Trusty had vesafb build in the kernel from the very first release, so I
believe the assumption is safe here.
Regarding precise:
Instead of removing the script I could leave it but alter it to check the
feature (e.g. kernel version number or
** Changed in: nfs-utils (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/1124250
Title:
Partially incorrect uid mapping with nfs4
Actually I think the second approach would be better, since the error
comes not from the message (which is redirected to upstart logs anyway),
but from the return code of the script.
Unfortunately, according to my knowledge, the upstart scripts are
executed with the -e switch making it stop with
Adding new SRU proposal for Precise.
** Patch removed: systemd_204-5ubuntu20.7.debdiff
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201485/+files/systemd_204-5ubuntu20.7.debdiff
** Patch removed: udev_175-0ubuntu9.7.debdiff
I have uploaded new patches updated as agreed.
--
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 manage notifications about this bug go to:
Adding new SRU proposal for Trusty.
** Patch added: systemd_204-5ubuntu20.7.debdiff
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4202154/+files/systemd_204-5ubuntu20.7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@blkperl
William, could you please confirm that you are using kernel at least
3.13.0-35.62 (this is a solution to #1344405 which may also cause
similar effects).
Could you also please provide the output of:
$ sudo cat /proc/key-users
You may also try to increase values (beside their root_*
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
/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.net/bugs
** 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
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 #
Thanks Vincent.
Would you mind giving the patched kernel from ppa:dgadomski/linux-mst a
try? That would allow us to confirm whether the cherry-pick works for
the trusty backport of utopic kernel.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for giving that a try Vincent. I believe that the intel driver
needs to be reinstalled for this to work.
Regarding the source code:
Please not that if you uncomment the following line in your
/etc/apt/sources.list.d/dgadomski-linux-mst-trusty.list file
# deb-src
** 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/1315098
Title:
GUI for managing ACL
To manage notifications about this bug go to:
** 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/445333
Title:
remember password on printing to windows printers does not work
To manage notifications about this bug go to:
** 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/1104230
Title:
DisplayPort 1.2 MST support is missing in the Intel driver
To manage notifications about this bug go to:
** 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/1367241
Title:
Incorrect udev-fallback-graphics.conf
To manage notifications about this bug go to:
** 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/1361217
Title:
[FFe] GUI for managing ACL
To manage notifications about this bug go to:
Vincent, I missed the setup you use in one of your comments. The kernels
that I have prepared add only one feature: the Multi Stream Transport
(MST) feature of the displayport 1.2, nothing else.
So basically for this to work you need a displayport 1.2 capable device
and a displayport 1.2 monitors
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.
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
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
1 - 100 of 792 matches
Mail list logo
