Is there a workaround for this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2059872
Title:
Unable to listen on port 22 if multiple Port= present in sshd
Problem solved (At last!!).
Since I am not a Linux/Debian/Ubuntu matter, I can't give detailed
reasoning the cause-consequence relationship. But this is what I did
after hundreds of tries.
1. Update SOF firmware binaries.
Read this:
~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: joseph-vunanga 4569 F pulseaudio
Thanks all for your contributions.
In my case, the only available kernels in grub are 5.19.0-35-generic and
5.19.0-38-generic.
Booting with both options have the same result: HDMI Audio is missing.
I've restarted the computer for weeks without any change.
Is there a safe way to install a
Public bug reported:
After months using the HDMI output without problems, it has stopped working
after a system update two days ago.
HDMI output is not listed in the list of available output devices.
Same computer works with this sound output perfectly when booting with Windows
or an older
@juliank: I was affected by this bug when upgrading to 22.04.1 from
20.04 at the weekend. (originally installed as 18.04)
Unfortunately the system did *not* auto-recover.
Manually picking the previous kernel options from grub gave the same
"error: out of memory."
I was able to recover the
Public bug reported:
I am experiencing beep sound and audio from zoom, firefox, or vlc. It might
play media for some seconds then beep. This has something to do with pipewire
and sof driver and S16_LE format.( I read online).
If I switch the profile Play HiFi quality Music in pavucontrol it
I found out what the issue was. The problem is the new linux kernal
update Linux 5.8.0-50-generic.
After booting up with Linux 5.8.0-48-generic (the previous one), the
problem is resolved
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Ubuntu was perfect before updating it.
I ran the command sudo apt update. After that, my computer graphics have
become choppy. I have attached a screenshot of the problem.
Description:Ubuntu 20.04.2 LTS
Release:20.04
00:02.0 VGA compatible controller: Intel
Pop OS 20.10 same for me intel 620
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1872802
Title:
Resizing any window will randomly result in graphics corruption for a
Done some more digging into this and I have a feeling it's to do with
IPv6. The interface gets several IPv6 addresses assigned (not sure if
this is an issue). If I turn off IPv6 support, for this interface, in
the Gnome Settings window, the interface recovers and stays up.
--
You received this
Public bug reported:
I'm on 20.04, on a Dell XPS 9730. Upon boot, the wired connection comes
up fine but, after a seemingly random time, the interface fails. If I
watch the NetworkManager journal and try and switch the interface off
and then back on in Gnome Control Panel, the interface keeps
The only way to get this back is a reboot, which also hangs due to
trying to stop the NetworkManager service.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1893798
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778
Okay, well after entirely too much excitement, I made some progress.
After much googling, I found that this error message refers to a problem
with GNOME so one can get around it by going into console mode,
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778
I tried to follow the instructions in #8. My computer is now bricked
with the message after login password of "Oh No! Something has gone
wrong. A problem has occurred and the system can't recover.
Hi,
It is not connecting at Bluetooth level. Once I manage to get it connected,
all works like charm.
On Mon, May 11, 2020, 2:30 PM Sebastien Bacher
wrote:
> Thank you for your bug report. Is it not connecting to the device at the
> bluetooth level or is connecting but not routing the sound to
** Description changed:
I'm running Ubuntu 20.04 LTS on a ThinkPad P72 with a Quadro P5200. I
recently purchased the ThinkPad Workstation Dock Gen2 and have been
having issues with external displays on it.
There are a multitude of issues with this. Sometimes you can plug in
displays
Public bug reported:
I'm running Ubuntu 20.04 LTS on a ThinkPad P72 with a Quadro P5200. I
recently purchased the ThinkPad Workstation Dock Gen2 and have been
having issues with external displays on it.
There are a multitude of issues with this. Sometimes you can plug in
displays and both will
Public bug reported:
I'm running Ubuntu 20.04 LTS on a ThinkPad P72 with a Quadro P5200.
Whenever I have Discrete graphics enabled in the BIOS, or set the prime-
select profile to NVIDIA, the display will freeze and the mouse pointer
will drift for a few seconds. This makes the system nearly
I currently have the package patched in my PPA to resolve the bug. It is
a difficult to debug problem that has been sending users upstream to
kodi with bug reports and confusing stack traces. This will get more
exposure when focal is released due to the LTS status.
--
You received this bug
Is this going to make it for focal? This bug causes kodi to crash when
turning my TV screen off.
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu.
** Also affects: initramfs-tools
Importance: Undecided
Status: New
** No longer affects: initramfs-tools
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
When IPv6 ND RAs are sent from two different routers, one with Medium
and one with High preferences, systemd-networkd will ignore the fact
they have different preferences and create two multipath routes with the
same weight.
I ran a tcpdump of the RAs and confirmed that both
No one is asking you to send them a fix. Since you are experiencing the
issue on a stable release, you should let Mesa know that the issue
exists in stable releases, and ask them to provide the fix for the
stable 20.0.x branch.
--
You received this bug notification because you are a member of
Oibaf is using the development release of Mesa. It's not released yet.
Mesa 20.1 isn't scheduled for release until May.
You need them to backport the fix to the 20.0.x branch. Here is the
upstream issue: https://gitlab.freedesktop.org/mesa/mesa/issues/2523
You can ask there for a backport to
I filed this against grub2 originally. Somehow ubuntu-bug changed that
to xorg. I added grub2 back. It's not letting me remove xorg.
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you
Public bug reported:
2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels
that don't have CONFIG_EFI_STUB=y configured. This really needs to fall
back to the old mode if EFI handover is not supported by the kernel.
Also, after using a kernel with CONFIG_EFI_STUB=y it still
This is supposed to be fixed in Mesa 20.1 git by c81aa15d,
gallium/auxiliary/vl: fix bob compute shaders for deint yuv.
See:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/c81aa15d646215eac38c8e0b6dc1a10b35bc13c3
This could be backported to Mesa 20 if someone wants to try it.
--
You
** Changed in: juju
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1860432
Title:
juju agent fails to start on focal
Status
Upgrade steps:
https://github.com/juju/juju/pull/11159
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1860432
Title:
juju agent fails to start on focal
Status in juju:
I'm marking this as also affects alsa-plugins since that is shipping a
jack plugin by default, and this bug is triggered when jack isn't even
running. Programs that scan for ALSA devices pick up that jack plugin
and trigger the double close.
** Also affects: alsa-plugins (Ubuntu)
Importance:
Initial patch for support in 2.7 is here:
https://github.com/juju/juju/pull/11147
Other patches for upgrade paths will follow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Nevermind need to use the daily image stream.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1860432
Title:
juju agent fails to start on focal
Status in juju:
In
Can we get some reproduction detail?
I can't specify focal as bootstrap-series on LXD (no image found) or
MAAS (doesn't start an instance, though I did add 20.04 to the image
list.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: juju
Status: Triaged => In Progress
** Changed in: juju
Assignee: (unassigned) => Joseph Phillips (manadart)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Can this package get updated to 1.9.13, or at least patched in time for
20.04? The security exploitability of this bug may be low, but the impact
on affected users is high. It causes hard to debug, random crashes of other
programs (e g. Kodi) that are scanning ALSA devices when the jack daemon
Public bug reported:
Screen occasionally shows strange distortions and corruptions during almost any
activity. Static or bars of colour appear in unusual places along the screen.
Corruptions are often (though not always) removed in some sections of the
screen by the appearance of other display
jackd2 released version 1.9.13 which includes this fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479
Title:
libjack-jackd2-0 double close on a failure to connect
I just requested one and received: CVE-2019-13351
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-13351
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
** Description changed:
After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes
in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-
- plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is
+ plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA
** Patch added:
"Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch"
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+attachment/5271631/+files/Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch
** Information type changed from
I'm marking this a security bug, since all double close bugs can
potentially be security bugs in multithreaded programs depending on the
close interleaving.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
See kodi issue with stack traces:
https://github.com/xbmc/xbmc/issues/16258
** Also affects: jackd2 (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
*** This bug is a security vulnerability ***
Public security bug reported:
After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes
in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-
plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is
enabled by
My network works fine. I am on a wired network connection. However,
whenever I try to connect using VPN I get the "Activation of network
connection failed" error message.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I still haven't been able to reproduce this. If you can reproduce this
easily, maybe I can provide some kernels to be tested?
I'll keep trying to reproduce here. I compared my VM settings to why is
in the bug description, and I have the same config, except the region.
I wouldn't think that
Public bug reported:
After upgrading from 18.10 to 19.04 the desktop context menu no longer
contains the choices:
Keep aligned
Organize desktop by name
These were very useful to me. I would like them to be restored.
Ubuntu 19.04, 64bit
Gnome 3.32.1
** Affects: tracker (Ubuntu)
Public bug reported:
The default state of display is upside-down. I'm observing this issue in
latest kernels(>4.19).
Command "xrandr -o normal" make things normal, but rotating display
welcomes unexpected behavior.
Please Check, Any help is highly appreciated. Thanks
ProblemType: Bug
I modified your script to perform 5000 reboots. I'm up to 3508 reboots
now without hitting the bug. I'll let it run for a while longer. I'll
also compare our environments to see if there is a difference.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Yeah, it's only `Snap user application autostart helper` and `SSH Key
Agent`.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1821904
Title:
Sound is muted by default
Hi Daniel,
I've done that and, although it doesn't fix the issue completely, I
think it's uncovered more clues. I've noticed that a volume setting
gets applied a few seconds after Gnome loads. So, after removing the
directory, I reboot and the volume comes up as it was in the previous
session.
Just to confirm, I also did this upgrade path (18.04 -> 18.10 -> 19.04)
on my desktop and I get the same issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1821904
Um, good question. The volume in Gnome shell top right panel, as well
in Gnome settings, appears muted (and it is muted when I try to play
things). All I need to do is unmute / press volume up or down to fix
this, it's just a small niggle.
The only extension that I have is extended-gestures.
I think this might still be a bug as I want the notifications in GNOME
notifications, just not also via Evolution (which I don't use anyway).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
** Attachment added: "allpackages.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+attachment/5250172/+files/allpackages.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1821904/+attachment/5250168/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1821904/+attachment/5250169/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1821904/+attachment/5250170/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1821904/+attachment/5250167/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1821904/+attachment/5250171/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Thanks Dan, hopefully they're all here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1821904
Title:
Gnome Shell always started muted on Disco
Status in pulseaudio
apport information
** Tags added: apport-collected wayland-session
** Description changed:
On Disco, Gnome Shell always starts muted.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu23
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+
** Attachment added: "English localised mkvinfo of the played video file"
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1821301/+attachment/5248401/+files/mkvinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
I try to read a video with totem, I heard some digital noise (less than
one second) and only see a black screen. Nothing append after that,
totem UI work but the video file don't play.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libgstreamer1.0-0 1.15.2-1
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
Public bug reported:
Each time I boot my laptop (and time to time after), the log show this
crash :
[ 47.202056] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us *
3000 tries - dce110_stream_encoder_dp_blank line:927
[ 47.202109] WARNING: CPU: 5 PID: 868 at
Has I say in my report : "Graphically, applications react normally, we
can see their connections with pulse audio in the applications tab of
the sound settings. But no sound comes out of the speakers."
At UI level, everything seem to work, application volume is not mutted.
The stranger thing is
Public bug reported:
A bug exists in ifupdown which incorrectly identifies Infiniband-capable
interfaces running in Ethernet mode as Infiniband interfaces. This
causes the creation of VLANs to fail with an error such as:
/bin/sh: 1: cannot create /sys/class/net/eth0/create_child: Permission
Further info: successive restarts of systemd-networkd or netplan apply
(which I've since learned simply generates files and restarts networkd)
applies the rule, following by the next immediate invocation removing
the rule, and so on.
--
You received this bug notification because you are a member
I can duplicate this. Posted my issue to askubuntu before coming across
this report. See https://askubuntu.com/questions/1094591/18-04-1-lts-
systemd-network-not-applying-routingpolicyrule for details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Package changed: linux (Ubuntu) => apport (Ubuntu)
** Changed in: apport (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1799118
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
I started a kernel bisect between v4.14 final and v4.15-rc1. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
1be2172e96e33bfa22a5c7a651f768ef30ce3984
The test kernel can be downloaded from:
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Public bug reported:
slows computer
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Sun Sep 30
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (unable to
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/796588
Title:
Fine-grained network mediation
Status in AppArmor:
In Progress
Status in
** Changed in: iproute2 (Ubuntu)
Status: Expired => Triaged
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
** Package changed: linux (Ubuntu) => apport (Ubuntu)
** Changed in: apport (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1790253
It looks like libx11-1.6.6 was pulled into cosmic. So this is fixed
there. This still needs a backport to earlier releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788321
Title:
swapon failed: invalid argument
*** This bug is a security vulnerability ***
Public security bug reported:
There are 3 security issues reported in libx11 that are fixed upstream
in libx11 1.6.6.
Bugs announced:
https://lists.x.org/archives/xorg-announce/2018-August/002915.html
Release announcement of libx11 1.6.6 with
** Tags added: kernel-key
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Assignee: (unassigned) =>
** Changed in: intel
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1591833
Title:
[Featue] Upgrade Openssl for Intel QAT
Thanks for filing this bug. This project is being shut down as it’s not
actively monitored by any team or individual. This bug will not be
deleted but will be closed as <>. If this bug is something
that is still affecting a product in Ubuntu, you can take one of the
following steps to report
ric x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: joseph17719 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 24 19:46:33 2018
InstallationDate: Installed on 2018-07-22 (2 days ago)
InstallationMed
Do you have a way to reproduce this issue, or was it a one time event?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1782893
Title:
Bluetooth not
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Cosmic)
Importance: High
Status: Triaged
** Tags added: kernel-da-key
** Also affects: lxc (Ubuntu)
Importance: Undecided
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
It's not a bug !
** Changed in: openssh (Ubuntu)
Status: Incomplete => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/openssh/+question/669164
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thank you for your reply.
I'm sorry, I did not think about watching the ChangeLog. Indeed, it is not a
bug, it may be closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Public bug reported:
Since Bionic upgrade (from Artful) I encounter problem to call HP switch
with SSH.
After the upgrade, trying to ssh some switch give me this message :
$ ssh 192.168.0.1
Unable to negotiate with 192.168.0.1 port 22: no matching cipher found. Their
offer:
Public bug reported:
Had filed a bug report earlier and the problem was not there for 2 days
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
no #121 don't work for me
I can access my desktop because i have blacklisted nouveau and using my intel
gpu system which I assume is functioning via mesa drivers nomodeset also works
only issue is if i try to run nvidia
--
You received this bug notification because you are a member of Ubuntu
@tom-lorinthe
I have no issues with accessing Intel I just blacklisted nouveau for
that purpose. I wanted to use Nvidia but on evry install it seems to
crash the OS
will try and fix nvidia-prime after getting nvidia driver working
there is also dkms seems not to install in the kernel 4.15.21
hey
There i am using ubuntu bionic 18.04 kernel 04.15.21
cant login on gdm or lightdm freezes on entering password or access tty
on install nvidia-390 , nvidia 396 from ppa:graphics-drivers/ppa and
nvidia-driver-390 from bionic main repo
used to have black screen on boot suddenly rectified
And now it is working on Dell 1440x900. Thanks a lot for the immediate
support.
-VK Joseph
On Sat, May 5, 2018 at 12:29 PM, Launchpad Bug Tracker <
1769...@bugs.launchpad.net> wrote:
> Status changed to 'Confirmed' because the bug affects multiple users.
>
> ** Changed i
Public bug reported:
Monitor resolution is limited to 1024x768 with no option for higher
resolution
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion:
Sorry, I forgot to give my workaround :
* Turn off the monitor (electrically), disconnect the power cord if need...
* Turn back on the monitor.
* There you go.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
1 - 100 of 312 matches
Mail list logo
