Wow. Thanks for all of that effort on behalf of Carbon X1 owners. My
machine is also a Lenovo 21HMCTO1WW. Looks like the same issues. So
this is an upstream problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for all of this work. I am not sure that I should be changing
the tags based on previous experience, but here is my test report.
For testing, I updated to the linux/6.8.0-32.32 generic kernel in noble-
proposed. It seemed that I needed to reinstall the intel-ipu6-dkms
after installing
I have upgraded to the noble-proposed ipu6-drivers package. Is there a
particular kernel that needs to be installed to get the camera to work?
Or is the kernel fix not yet available?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, just trying to help by providing reports an following the rules.
I'll refrain from posting moving forward.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061747
Title:
obsolete out-of-tree
Thanks, I tried the NVidia kernel 6.8.0-1005.5+1 from noble-proposed;
still no detection. Could be that this predates that patch series? Not
sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-noble
** Tags added: verification-failed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061747
Title:
obsolete out-of-tree ivsc dkms in favor of in-tree
I did the followings steps:
- Added the noble-proposed repo
- Installed the driver(s) using: `sudo apt install
intel-ipu6-dkms/noble-proposed`
- Confirmed that the correct package was installed:
```
$ apt policy intel-ipu6-dkms
intel-ipu6-dkms:
Installed: 0~git202404110253.97c94720-0ubuntu1
*** This bug is a duplicate of bug 2038313 ***
https://bugs.launchpad.net/bugs/2038313
All of the Wayland issues for Haswell disappeared for me in fixes to the
Intel drivers in the last week. The bug #2038313 in upscayl still
remains.
--
You received this bug notification because you are a
I moved the driver file up a directory from /lib/firmware/intel/ipu to
/lib/firmware/intel and now the firmware appears to be loaded. But
something else is still wrong here:
[ 19.220279] intel-ipu6 :00:05.0: Device 0xa75d (rev: 0x0)
[ 19.220291] intel-ipu6 :00:05.0: physical base
Public bug reported:
I followed the suggestions here for handling the Intel MIPI camera
replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo
Perhaps I should have installed 22.04? Anyway, this is a new laptop so
I went with the new release.
I tried both the generic and oem kernel. Same.
*** This bug is a duplicate of bug 2038313 ***
https://bugs.launchpad.net/bugs/2038313
I'd tentatively suggest that this is not a duplicate in the following
sense:
- bug 2038313 occurs on both Wayland and Xorg sessions
- the case(s) that I reported here occur only on Wayland; everything
I also tried removing the Mesa Vulkan driver and set `export
LIBVA_DRIVER_NAME=i965`. That gets rid of the warning message but I
still get a hang with Vivaldi and nextcloud-desktop still does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks. Sounds similar. My nautilus and gnome-control center do work
strangely enough. But the more clues the better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
After 24.04
** Package changed: xorg (Ubuntu) => wayland
** Project changed: wayland => wayland (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
After 24.04 upgrade, many graphical app
Thanks for solving this. I made the change and confirm that keyboard
input now works again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056578
Title:
Tor Browser - keyboard not functioning
To
I tried the same upgrade and test on an old Sandy Bridge laptop.
Everything works as expected there. So a Haswell issue perhaps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
After
Public bug reported:
Conversely, everything works fine in Xorg.
I suspect that this must be a upstream graphics library problem with
Haswell. I also tried this on an old Sandy Bridge machine and it works
as expected.
Happy to do do additional tests and reporting but I'm not sure what to
do.
I tried the same test on an old Sandy Bridge laptop. Everything works
as expected there. So a Haswell issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
After 24.04 upgrade, many
** Summary changed:
- Many app failures under Wayland; no issues with Xorg
+ With 24.04: Many graphical app failures under Wayland; no issues with Xorg
** Summary changed:
- With 24.04: Many graphical app failures under Wayland; no issues with Xorg
+ After 24.04 upgrade, many graphical app
I should also mention: this was an upgrade from 23.10 to 24.04 and all
of the apps worked correctly in 23.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
Many app failures under
Public bug reported:
Many applications seem to fail under a Wayland session that work correctly with
an Xorg session. E.g.
- The nextcloud client app fails to contact the server and functions in the app
will not launch with Wayland while they work perfectly in Xorg
- The Vivaldi browser exits
I can confirm, and this has been irritating me for years.
I suggest using 'terminator' as a work around.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1288655
Title:
Terminal height shrinks -
Public bug reported:
The attempt to upgrade generates cycles of broken dependencies, even
though the initial 18.04 system has no broken packages, is upgraded, and
is working correctly. The upgrade logs did not give me a clue; maybe
it is something simple?
ProblemType: Bug
DistroRelease: Ubuntu
Public bug reported:
There seems to be a cycle of dependencies that breaks upgrade path.
However, the current 18.04 has no broken packages, is upgraded, and
works correctly. I was unable to spot the problem in the log.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package:
This seems to be the same problem reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
** Bug watch added: Red Hat Bugzilla #1506339
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "kern.log containing a dead hang"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+attachment/5387972/+files/kern.log.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I ran it until it happened again. I'm attaching the syslog and
kern.log from the time of the crash, which was Jun 28 at about 15:30.
Doesn't seem to be a lot to go on here . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "syslog surrounding the dead hang"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+attachment/5387971/+files/syslog.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This kernel also shows continuous rendering artifact on the native LCD
screen, such as the windows underneath the current active window appear
as flickering ghosts. No problems on the previous released kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
This issue has been a persistent but infrequent problem for many years
with the T440s. It only occurs when the laptop is docked. I have
reported this bug several times. However, with the current kernel
release, 5.4.0-37, this occurs at least once a day. The kern.log lines
I tried Wayland, too, same problem.
My workaround was to remove the Ubuntu package and compile Paraview from
scratch by cloning the git master branch. It takes some time, but it
works. Follow the instructions here:
https://www.paraview.org/Wiki/ParaView:Build_And_Install
--
You received this
Also note: this was an upgrade from 19.10, not a new install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869612
Title:
libmpi.so link is missing
To manage notifications about this bug go to:
The obvious work around is to make the link by hand, which I did, and
all is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869612
Title:
libmpi.so link is missing
To manage notifications
Public bug reported:
This file disappeared from 19.10 dev package. Without the *.la file,
libtool fails to configure libraries with GTK dependencies.
My work around was to grab the file from 18.04 and change the metadata
for the current library versions. That allowed me to successfully
compile
We can close this bug report at this point. But I do appreciate the
follow up!
It turns out that there were two problems. The first was that 18.04 had
misconfigured the cryptoswap so that was not working at all. I reported
this separately before the release of bionic and I believe that this
Sebastien: Yes, that is precisely the issue! Took me an afternoon of
sleuthing to figure it out.
Emiliano: You might want to find out if any package is providing that
file (e.g. dpkg -S 20-intel-graphics.conf) and delete that file if it
turns out to be orphaned. I do not that file, but I do
xorg.conf has been replaced by the rules in /usr/share/X11/xorg.conf.d.
You can see if there is some older cruft in there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768610
Title:
No
If you want to try that, you can grab a more recent kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ but I doubt that this
will fix your issue. I'd bet on a configuration thing, but not sure
what. You don't, by any chance, have a custom xorg.conf (in /etc/X11
or /usr/share/X11)? I
Yes, I would make a new comment to your bug report with the logs under
xorg session. I hope that one of the Ubuntu developers have a clue
about this. I'm curious myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
P.S. I also note that you are using wayland. No reason to think it will
matter, but just of of curiosity, have you tried the xorg session?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768610
I look a quick look at your posted data. It does seem odd that your
system starts out configuring the drm and then uses fb. Do you have
anything custom on your boot line, like some video parameters? E.g.
'cat /proc/cmdline'. More grabbing at straws.
--
You received this bug notification
Well, this sounds like a different problem. The problem I reported was
very clearly the result of an incomplete package upgrade/removal
resulting in a failed test for unity compatibility leading to setting
that environment variable for software gl.
You might consider opening an new bug report
Emiliano: I'm grabbing at straws, but try checking for other files in
'/etc/X11/Xsession.d/' that might be setting 'export
LIBGL_ALWAYS_SOFTWARE=1' in the environment. E.g. 'grep -H LIBGL
/etc/X11/Xsession.d/*'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm not an expert, but you might want to see if you can gain some
insight from the output of 'journalctl -b0'.
E.g. is your system using the framebuffer driver "fbcon: xxx" or "[drm]
..." during boot up?
In the 'journalctl -b0' output I posted above,you can see that it's
using the frame buffer.
Emiliano: the problem file is
'/etc/X11/Xsession.d/50_check_unity_support'. You might want to confirm
that this is gone with the purge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768610
Title:
I have figured out the problem: the installer removed nux-tools, left
over from unity, but did not purge it. This left a start up script in
/etc/X11/Xsession.d which interfered with gnome. Purged that and the
problem was gone.
So this is a dependency bug in the nux-tools package (or perhaps
** Summary changed:
- No acceleration after upgrading to 18:04 gnome-session-check-accelerated
incorrectly picks llvmpipe
+ No acceleration after upgrading to 18.04: gnome-session-check-accelerated
incorrectly picks llvmpipe
--
You received this bug notification because you are a member of
Public bug reported:
After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
animations were gone. After some digging, it seems that gnome-session
incorrectly assumes that my graphics has no acceleration, when in fact
it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated
Same problem with bandwidthTest. nvprof works with deviceQuery and
reports time spent in the various cuda query calls, but also reports "no
kernels profiled".
I did check the /dev/nvidia* permissions and they look fine to me, e.g.
crw-rw-rw. As I also mentioned, suid/guid on nvprof did not help
I tried it, and the behavior is the same.
However, the thread http://devtalk.nvidia.com/default/topic/1025155
/-resolved-profiling-error-4168-999 suggests that this issue may be an
upstream bug, although the developer did not give details.
So maybe the Ubuntu package is all good, but we'll need
Thanks. Did that, but no change in the 'nvprof' behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767205
Title:
nvprof does not complete without sudo
To manage notifications about this bug
There is no change running 'nvprof' immediately after 'sudo 'nvprof' or
vice versa. The former fails, the latter works. The same is true for
'nvvp' because of course 'nvvp' calls 'nvprof'. I ran 'nvprof' with
strace to look for some sort of write access to a /proc or /sys resource
but I didn't
Public bug reported:
Description:Ubuntu 18.04 LTS
Release:18.04
Expected behavior: profile output
Actual behavior: error messages
Reproduce as follows:
cd NVIDIA_CUDA-9.1_Samples/0_Simple/matrixMul
nvcc -I ../../common/inc matrixMul.cu -o matrixMul
# check the exe works
BTW, if i might make another comment rather than file a new bug report:
nvprof requires root privs. Even suid/guid root is not enough.
On 04/25/2018 03:46 PM, Graham Inggs wrote:
> sudo apt install openjdk8-jre
--
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039
--
You received this
Thank you very kindly for the quick reply. That worked perfectly!
It appears that openjdk-11 is installed by default.
On 04/25/2018 03:46 PM, Graham Inggs wrote:
> sudo apt install openjdk8-jre
--
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039
--
You received this bug notification
Public bug reported:
Description:Ubuntu 18.04 LTS
Release:18.04
nvvp should run without crashing. Other tools in the toolkit are
working.
Error message is:
Xlib: extension "RANDR" missing on display ":1.0".
WARNING: An illegal reflective access operation has occurred
WARNING:
Some good and bad news: I have been testing this in a running Gnome 3
environment. I decided to start testing on console. On console, all
kernels seem to fail using crypt swap. This suggests to me that failure
must depend on current memory usage, dirty ratio, or some such runtime
condition.
In response to #7, I don't think this is the same issue. The cryptswap
initiates with no difficulties, timeouts, etc. on boot. When I first
installed Bionic, ubiquity did not correctly install the swap, and I
filed #1759253 on that issue.
--
You received this bug notification because you are a
BTW, I _do_ realize that you want a starting point for bisection; I'm
sorry this is turning out so messy.
On 04/11/2018 05:51 PM, Martin Weinberg wrote:
> The first kernel on that list that exhibits the bug is the first one:
> 4.14 Final. Recall: the bug results in a full up hang. The disk
The first kernel on that list that exhibits the bug is the first one:
4.14 Final. Recall: the bug results in a full up hang. The disk stops
swapping (it's audible). I can reboot with sysctl SUB however.
I then tested 4.13.0-36 from the Ubuntu 17.10 respoitory, followed by
Yes, the problem does occur in mainline 4.16 and I have added the
requested tag.
If anything, 4.16.1 seems slower than 4.15 release kernel even for no
cryptswap. It could be that my disk is too slow for cryptswap, but it
did work in 17.10.
The obvious work around is not to use cryptswap, of
It seems that cryptswap is working correctly on 17.10 with the kernel
4.13.0-36-generic on a different machine using the same test as
described above. I tried the same kernel (4.13.0-36) on 18.04 (machine
used in original post) and it still fails. Of course, I checked that
the swap appears in
The code that I used to force failure, memtest.c, is attached to the bug
report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762468
Title:
Cryptoswap not working in Bionic
To manage
Public bug reported:
I have cryptoswap set up both with the 2 GB default swap file and an 8
GB swap partition with 8 GB of ram. However, the system does not use
this swap when it should. For example, if I run a little test code
which attempts to allocate 10 GB of memory in 1 GB chuncks, the
I continue to see this problem on a daily basis, often after a resume
from suspend, I am not running Wayland, and this crashes my
gnome-session half the time, so something there is some confusion/bug
somewhere. This morning's crash resulted in message from xorg-server so
I let apport file a bug
** Attachment added: "/var/log/installer/partman"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1759253/+attachment/5092157/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I needed to do an 'emergency' reinstall while travelling owing to a
hopeless corrupted encryptfs. I happened to have a Bionic iso from
March 11 and used that to install to my laptop.
Soon after installing, I noticed various problems with logins, hangs,
etc. which I recently
I've been studying the swap mess. It seems that the installer made a
swapfile called /swapfile and entered the line in /etc/crypttab as:
cryptswap1 /target/swapfile /dev/urandom swap,offset=1024,cipher=aes-
xts-plain64
which is the wrong, non-existent filename. So that seems to be an issue with
Thanks. Your comments led me to look at swap. There is no swap!
I installed from iso image several weeks ago (I am traveling and had a
bad ecryptfs corruption, not sure how this happened, and needed to
reinstall, and had this on my memory stick for testing).
I selected encrypted and had an
I saw that. But the disk is far from full. Don't know what's up with
the /snap loopback devices. The hard drive itself is at 35%. Here's
the df output:
Filesystem Size Used Avail Use% Mounted on
udev 3.8G 0 3.8G 0% /dev
tmpfs 767M
I'm still getting failures. This is with a fixed variety and no gnome-
shell extensions other than the default ubuntu extensions.
I don't see but reports similar to this, so I gather that others are not
generally plagued by this problem. Nonetheless, I appreciate any advice
or comment you have
Thanks. That variety script was from an old version of variety, it
seems. I removed that and checked that the current scripts in
/usr/share/variety/scripts do not have that bug (looked like an
operation on a shell variable that may not exist). I did notice a few
variety crashes, but they do
Daniel,
I took a few days, but it did again fail with the same issue. I'm
attaching the log, collected shortly after the failure by switch to
console while running the Wayland session, as you requested. Had to
reboot afterwards, to be able to log on to the desktop.
Hope this helps you spot the
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Greeter/lockscreen fails to authenicate in an endless loop
To manage notifications about this bug go
Also a problem with the Wayland session. Not a big surprise. For now,
I've turn off the screen lock.
Not sure what else to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Addendum: I was running the Xorg ("Ubuntu") session when the problems
occurred. I'm trying the Wayland session now, so the autogenerated tag
is not correct, and maybe not relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After a recent install of the 18.04 (why is a separate story), I notice
that after some number of successful screen locks, I become locked out
of the desktop with an authentication failure. During those
unsuccessful attempts to log in, syslog shows:
Mar 13 22:46:04 magpie
I refiled the bug at bugzilla.gnome.org as bug 790040.
The link is: https://bugzilla.gnome.org/show_bug.cgi?id=790040
I'm really surprised that there are not more complaints about this. To
be fair, the dock+external monitor setup has NOT worked perfectly in any
release Ubuntu release,
Just to make sure, I again repeated the sequence of events outlined
above on the stock 17.10 kernel:
Linux magpie 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
The behavior is identical to that reported above.
One minor elaboration: when I open the
Public bug reported:
In the default configuration, resuming my T440s on the Lenovo ultradock
results in not detecting the external monitor followed by a suspend.
If I open the lid while on the dock, gnome detects the external monitor
and blanks the laptop display. Then, closing the lid results
Public bug reported:
I have a Lenovo T440s (haswell) and an ultradock with external monitor.
If I resume on the dock, wayland seems to recognize the lid as closed
and suspends. The work around is to (1) open the lid, bring up the
display control tab and switch to single monitor, choose the
Yes, no problem with GNOME on Xorg. Thanks for the heads up.
I found another problem with Wayland handling the dock + laptop lid that
works correctly with Xorg. Just trying to help. Not sure what package
to file a bug on, do you? Would that be xwayland?
--
You received this bug notification
Yes, GNOME on Wayland. I will try GNOME on X.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725698
Title:
Size decreases when cycling between full-screen mode using F11
To manage notifications
Public bug reported:
Launch an gnome-terminal and cycle between full screen and normal by
pressing F11 twice. The original size of the terminal is not restored.
Doing this multiple times, the window continues to shrink.
This did not occur on 17.04 or earlier. I use this regularly as part of
my
I am happy to report that linux-image-4.4.0-63-generic from xenial-
proposed _is_ working correctly with the T440s on and off the dock. So
the bug is gone from the -proposed kernel package.
Thanks for that!
If we could only get the DP audio to work on the dock, sigh. It hasn't
worked since
Another thought: I'm using the modesetting driver, not the intel driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662381
Title:
linux-image-4.4.0-62-generic breaks Lenovo T440s on Ultradock
Also, and not sure if this is related, Plymouth does not correctly
render the splashscreen on boot up. Part way through, the screen blanks
and only the "dot icons" are visible. Again, this does not occur for
earlier kernels.
--
You received this bug notification because you are a member of
Public bug reported:
When using with dock, attached monitor is not detected, laptop monitor
remains blank. Requires a reboot
4.4.0-59 works fine. I'm guessing this is due to the i915 patches for
DP.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-62-generic 4.4.0-62.83
The symptoms and behavior are nearly the same, so the issue seems
closely related, if not the same. However, the report is for different
hardware and dock (UltraDock rather than OneLink dock although both
Haswell). But, without doing the back port of Dave Airlie's patches to
4.9.x, 4.10.x or
Thanks Luke.
I tried it but, sorry to report, the results are the same: pavucontrol
claims that the HDMI is unplugged.
I also checked with "aplay -D" commands and none of the HDMI devices
detected will play. The internal audio and a USB device are detected
and work fine.
--
You received this
Thank you for that extra info, Henry!
So, with a minor bit of sleuthing, I figured out that you are using the
opensuse repository rather than 'universe' for your owncloud-client. I
was hoping to stick to the Ubuntu-maintained repository for consistency.
However, I can confirm that the
I saw a few changes for glib-networking pushed today. However,
owncloud-client doesn't depend on these. But just to confirm one way or
the other, I upgraded and rebooted. I can report the same broken
behavior as in the original post.
Henry: can you be more specific? What packages did you
I also tried 14.04.2, which is kernel 3.16.0-30, and that also detected
the HDMI/DP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582414
Title:
No HDMI audio on Lenovo pro dock with T440s
To
Thanks.
Booted with the latest daily, which is kernel 4.4.0, and it does not
detect HDMI/DisplayPort on the ThinkPad ultra dock.
Also, from the old-releases repo, I downloaded the 14.04.1 iso running
kernel 3.13.0-32, and that one DOES detect the HDMI/DisplayPort.
--
You received this bug
Since this is a QT bug in the Ubuntu distribution, what is the correct
procedure for requesting (begging?) the QT maintainers to backport the
patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does this issue have to do with MST support in kernel 4.4? The 3.13 in
14.04 did not have MST support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582414
Title:
No HDMI audio on Lenovo pro dock
Public bug reported:
pavucontrol shows Display Port/HDMI output as "(unplugged)" and cannot
be chosen as a sink. This is only a problem with the dock; audio works
when plugging HDMI through the laptop's DP input.
The audio did work with the dock in Ubuntu 14.04. Did something in jack
detection
*** This bug is a duplicate of bug 1572321 ***
https://bugs.launchpad.net/bugs/1572321
** This bug has been marked a duplicate of bug 1572321
owncloud network access is disabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see that this appears to be the same as bug #1572321.
Sorry about that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580632
Title:
server connection state is confused and/or lost after suspend
Public bug reported:
After resuming from a suspend, the previous behavior was to reconnect to
the owncloud server. Or, instruct the app to reconnect.
With 16.04, the app claims that there is no connection to the owncloud
url. Trying to log out of the server seems to force confuse the app (it
1 - 100 of 122 matches
Mail list logo
