Public bug reported:
The report has be sent
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.17
ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.26
Architecture: amd64
CasperVersion:
Public bug reported:
I have sent the report
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.17
ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.26
Architecture: amd64
CasperVersion:
Public bug reported:
With "linux-image-5.13.0-27-generic" on Ubuntu 20.04.3 LTS, my notebook
(Thinkpad T14) crashes when waking up after being suspended. The screen
displays what I would describe as "colourful snow" with some vertical
stripes on the right edge of the display. The only thing I can
yeah, if fact it is not a gnome-control-center bug, but a problem with
libWebKit2gtk-4.0 under Wayland. This affects both, Kubuntu as well as
stock Ubuntu (also in 21.04, which I use).
** No longer affects: gnome-control-center (Ubuntu)
** Also affects: webkit2gtk (Ubuntu)
Importance:
** Also affects: gnome-control-center (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/1908931
Title:
Kubuntu 20.04 System Settings Online Accounts
I have encountered the same problem while using Cisco AnyConnect. Found
out that it is libwebkit2gtk related. It seems it can't cope with
wayland. Does it work if you launch with
# WAYLAND_DISPLAY=no gnome-control-center ?
--
You received this bug notification because you are a member of Ubuntu
Thanks to all you guys for the description of the problem and the
suggested fix by changing the boot flag of the preexisting efi
partition. I spent quite some timee trying to fix this, since I thought
i might have done something wrong.
If I understand the problem correctly, Ubuntu has a bug for
Sorry, I'm no longer on Kubuntu and no longer using Firejail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925800
Title:
Many failures on Kubutu 20.10
To manage notifications about this bug go
Public bug reported:
Sorry that this will be light on detail. Consider it something of a
"quick glance" at the current state of Firejail from a normal user's
POV.
I gave Firejail a try on my Kubuntu 20.10 system, by running "sudo
firecfg" and then rebooting, and mostly it was a disaster:
-
Public bug reported:
Each profile file in /etc/firejail should contain a line saying what
version(s) of the app it applies to. And maybe a warning should be
logged if there is a version mismatch.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: firejail 0.9.62.4-3
ProcVersionSignature:
Public bug reported:
Man page says Snap and Flatpak not supported; I think it also should say
that Docker is not supported, right ?
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: firejail 0.9.62.4-3
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic
Okay, thanks, check-requirements gives:
WARN: detected other firewall applications:
firewalld
(if enabled, these applications may interfere with ufw)
Is there some way this check could be done in more places, and a warning
given to the user in each place ? The ufw and gufw GUI
What I am seeing seems to be a state change that happens at boot time,
so I can't capture it in gufw cli. I have filed
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1914816
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Sorry, this is going to be a very bad report. Here's what I did:
- installed gufw and enabled it, no rules, just default incoming=deny
outgoing=accept
- rebooted
- Ethernet says it connected
- no network access; ping 1.1.1.1 fails
- launch gufw, and it says it's disabled
I guess I can't close this issue myself, so please close it for me.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914606
Title:
Wiping .cache makes gufw fail, cuts network access ?
To
Okay, now I'm convinced my problems have nothing to do with ~/.cache, so
I'm closing this issue. But I'm still having gufw show "disabled" after
a reboot. When it happens, is that just reacting to some change that
ufw made to the iptables ? Such as setting the INPUT chain to empty ?
I think
Maybe ufw stores something important in ~/.cache ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914606
Title:
Wiping .cache makes gufw fail, cuts network access ?
To manage notifications about
Could it be something used by gufw ? Firewalld or iptables or something
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914606
Title:
Wiping .cache makes gufw fail, cuts network access ?
To
Public bug reported:
I added a line to /etc/fstab to put my ~/.cache on a tmpfs:
tmpfs /home/user1/.cache tmpfs
nodev,nosuid,mode=1777,size=1G,defaults 0 0
or:
tmpfs /home/user1/.cache tmpfs
noatime,nodiratime,nodev,nosuid,mode=1777,size=1G,defaults 0 0
[I tried a couple of versions,
** Description changed:
The CImg library uses an unsafe pattern to calculate memory allocations
size. At least in the PNM file format parser, an attacker can trivially
supply width/height fields that overflow the heap and result in
arbitrary heap writes. This probably also affects other
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25693
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900983
Title:
Multiple heap buffer overflows caused by int overflow
To manage
** Description changed:
The CImg library uses an unsafe pattern to calculate memory allocations
size. At least in the PNM file format parser, an attacker can trivially
supply width/height fields that overflow the heap and result in
arbitrary heap writes. This probably also affects other
Public bug reported:
Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04:
/snap/evince/532/usr/bin/evince: symbol lookup error:
/snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4: undefined
symbol: gdk_pixbuf_init_modules
** Affects: evince (Ubuntu)
Importance: Undecided
Sorry, I should have filed against update-manager. Can you please move
the bug over to there ?
It would be nice if these apps had "About" menu items.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been using various Snaps for about 5 months now, and I've never
seen any of those UI things appear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883250
Title:
Behavior while
Public bug reported:
While updating Snaps, the Details button doesn't work, and there is no
indication of what is happening or did happen, and no progress
indicator. Please fix/add these. Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-notifier 3.192.30
Okay, filed
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/543
** Bug watch added:
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #543
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/543
--
You received this bug notification
Public bug reported:
In Ubuntu MATE 20.04: If I connect to or disconnect from a VPN, I get a
notification that says something like "disconnected from Network". This
is too generic. Every notification involving a VPN change should
specify the VPN connection name, and the underlying network
Public bug reported:
In Ubuntu MATE 20.04: If you click on the icon next to a removable
device to dismount and eject it, the notifications you get are something
like "Writing to the drive, don't remove it yet" and "It is now safe to
remove the drive". If you have multiple devices
Public bug reported:
Installing Ubuntu MATE 20.04: After choosing options such as LVM, before
partitioning occurs, a dialog appears saying "Write the changes to disks
?". Some information seems to be missing or truncated. See last line
in attached screenshot.
ProblemType: Bug
DistroRelease:
Public bug reported:
Ubuntu MATE 20.04 installer: While user is setting password to use on
LVM encryption of disk, there should be some way for the user to see the
password they have typed, to make sure it is correct, no typos. Maybe a
hide/show toggle icon.
ProblemType: Bug
DistroRelease:
Public bug reported:
1. Hold down Shift key while booting, to get into GRUB
2. Choose options to get into Recovery menu (I forget exact wording)
3. As Ubuntu continues to finish booting, boot messages write over top of GRUB
menu (see attached screenshot)
4. I think you can use up/down arrow keys
Public bug reported:
1. Boot into GRUB recovery menu.
2. Select menu item "Drop to root shell prompt".
3. Get prompt that says "Press Enter for maintenance (or press control-D to
continue):"
This is confusing, and actually backwards. Control-D doesn't "continue"
with the menu item you
Public bug reported:
I uninstall something that affects Nautilus, such as the MEGA sync
package. I get a dialog that says "Nautilus Restart Required" (see
attached screenshot). I click the "Restart Nautilus" button. I get no
feedback that anything happened. I sit there wondering if it worked.
Maybe use these steps to create the archives, then double-click on the
first resulting archive file (tmp1.7z.001) and do an extract.
mkdir tmp1
cd tmp1
for f in a b c d e f g h i j
do
for g in a b c d e f g h i j
do
for h in a b c d e f g h
Public bug reported:
Suppose you have a four-file archive with files a.7z.001 a.7z.002
a.7z.003 a.7z.004 containing 500 files. While extracting from it, the
progress dialog will show filename "a.7z.001" and "500 files remaining"
and the progress-bar will stay near the left end, for the whole
Okay, filed https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021
Would be nice if ubuntu-bug sent me there directly. I'm getting tired
of having to file a lot of bug reports twice. Sometimes downstream says
go to upstream, sometimes upstream says go to downstream. The app
displays as
Public bug reported:
Please add a setting in the store app to show only open-source apps,
hiding proprietary apps. Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software 3.36.0-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic
Filed https://github.com/fwupd/fwupd/issues/2197
** Bug watch added: github.com/fwupd/fwupd/issues #2197
https://github.com/fwupd/fwupd/issues/2197
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please change the status of this bug to "wishlist". Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884387
Title:
fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet
controller
Okay, filed https://github.com/fwupd/fwupd/issues/2196
** Bug watch added: github.com/fwupd/fwupd/issues #2196
https://github.com/fwupd/fwupd/issues/2196
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, thanks for the info. Should there be a less-alarming message ?
Something like "this device does not support the verify operation" ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884387
Title:
Public bug reported:
sudo fwupdmgr verify [DEVICEID]
gives
failed to verify RTL810xE PCI Express Fast Ethernet controller: failed
to read firmware: Error reading from file: Input/output error
Is there some file-permission error in the system, or the fwupd
definition for this device is wrong,
Public bug reported:
fwupdmgr --show-all-devices get-devices
does show three devices, one updatable.
fwupdmgr refresh
says "Successfully downloaded new metadata: 0 local devices supported"
sudo fwupdmgr verify [DEVICEID]
gives
failed to verify [DEVICENAME]: no results for XPath query
Public bug reported:
I installed Ubuntu 20.04 GNOME LTS a month or so ago. IIRC, the only
easy choices given to the user were to encrypt using LVM, and to use
ZFS, and there was little or no explanation of them.
The installer should give simple radio-button or check-box ways to choose:
- ZFS or
Public bug reported:
I installed Ubuntu 20.04 GNOME LTS, and during installation /
partitioning some background process (partitioner ?) crashed. So the
installer led me into creating or logging in to an UbuntuOne account,
filing a bug report, etc. Who has access to their account information
in
Public bug reported:
Since a few days my Ubuntu 20.04 systems shows the following behavior:
The sound settings panel in part ignores the selected output device. I
can switch between the devices and in turn all volume controls seem to
affect that device (including the hotkeys etc.). But the sound
Public bug reported:
In the Software Updater application, while checking/updating
snaps:
- the Details button does not work
- there is no percent-progress indicator shown
Please fix/improve these.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-manager 1:20.04.10.1
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375551/+files/CurrentDmesg.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375556/+files/ProcEnviron.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375552/+files/Lspci.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375560/+files/UdevDb.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375561/+files/WifiSyslog.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375558/+files/ProcModules.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375559/+files/PulseList.txt
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375557/+files/ProcInterrupts.txt
--
You received this bug notification because you
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375554/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/537/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375553/+files/Lsusb.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1880119/+attachment/5375550/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1879997 ***
https://bugs.launchpad.net/bugs/1879997
apport information
** Tags added: apport-collected tricia
** Description changed:
System does not shut down properly with this Kernel: Kernel 5.3.0-51
seems to work OK
This is on a system
Public bug reported:
System does not shut down properly with this Kernel: Kernel 5.3.0-51
seems to work OK
This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working.
Attached is version.log and the output of inxi
** Affects: linux (Ubuntu)
Importance: Undecided
I can confirm, that the package in -proposed fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783994
Title:
systemd spams log with "Failed to dissect: Input/output error" on
Similar happens in Linux Mint 19 system with no Bluetooth devices.
In Settings/Bluetooth, I have no Bluetooth devices and all settings are set to
"off".
In output of journalctl, I see this while booting:
pulseaudio[2770]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed:
I see the messages (starting with "Could not find key with description")
on a fresh install of Linux Mint 19 Cinnamon.
Second line of kern.log says: "Linux version 4.15.0-36-generic
(buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
#39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783746
Title:
ipmmu is always registered
To manage notifications
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787945
Title:
Tango platform uses __initcall without further
I found a source reference here:
https://github.com/fanf2/bind-9/blob/master/lib/isc/unix/socket.c#L4127
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
bind9-host,
also attching a gdb full bt, which shows that epoll_wait is called it a
timeout value of "-1" (infinite) in thread #4.
** Attachment added: "gdb.txt"
https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1752411/+attachment/5182603/+files/gdb.txt
--
You received this bug notification
in fact, there are two host commands running, both show
wchan=sigsuspend, perf shows nothing and strace shows commands is
suspended. new strace is attached.
** Attachment added: "strace.txt"
well, I think you forgot to attach the patch. So I called editconfig
myself and disabled the TANGO platform. For unknown reasons, this also
enables CONFIG_ARCH_HAS_FILTER_PGPROT in config.common.ubuntu... Anyway,
the new kernel boots and suspends/resume just fine.
** Patch added: "q.diff"
Thanks for picking this up. While disabling all non-dt platforms seems a
bit rude, disabling all "non-multi_v7" defconfig platforms seems to be a
good idea to start with in order to avoid more of such problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** 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/1787945
Title:
Tango platform uses __initcall without further checks
To manage
Public bug reported:
The TANGO platform is enabled by default in the multiplatform ARM
kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c without
a check whether it actually runs on this hw. This causes an OOPS during
suspend on my Tegra platform. Please disable this (multiplatform
It is possible that it didn't show up in older kernels (4.4 for X)
because Tegra didn't used the IOMMU at that time.
** 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.
It started after upgrade from X to B. This may only show up on Tegra2, which
does not have an IOMMU, and which creates problems if one is registered. Sorry,
I don't understand the technical details. AFAICT, the whole driver is still
broken in mainline kernel (since 3.20). An upstream fixed is
here is an updated fix:
https://github.com/systemd/systemd/commit/cde942f61bf231ea4a0d50780cdb4e744458daeb
#diff-5be2770e81c14245e90d2916ded39491
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783994
Public bug reported:
If a device has an mmc installed, systemd-gpt-auto-generator will fail because
of "special partition" (rpmb, boot) and record a log message:
systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error
This issue was discussed here:
** 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/1783746
Title:
ipmmu is always registered
To manage notifications about this bug
Public bug reported:
Hi,
booting the bionic kernel (4.15.0-29-generic) on my Tegra20 device (no
iommu), I found it crashes during display driver setup. The bootlog (and
crash) is attached. Asking on Tegra IRC channel, digetx found that this
is caused by the IPMMU-VMSA driver which is always
I have been an issue with my printer for few days. I have tried your
method but I got no result after that I visit
https://printerssupport.org/ricoh-printer-support/ this site and they
give me to guide me to set up. Now My printer is working fine
--
You received this bug notification because you
Hello,
I have build locally an updated apt-setup.udeb with the patch from #12
and it works for me.
Installation of the rebuild udeb is a bit hacky via early_command:
d-i preseed/early_command string wget -q -O /tmp/apt-setup.udeb
http:///apt-setup-udeb_0.104ubuntu5_amd64.udeb; udpkg
-i
My system was upgraded, so maybe a leftover. So I uninstalled ifupdown and
upstart. Problem still persists :-(
I will attach a ltrace -Sf host output - maybe it helps...
** Attachment added: "output of "trace -Sf host -d -v -w5 -t soa local.""
I found the reason for this problem: it turned out to be the BIOS
setting "Boot Order Lock". After disabling it, I saw the above message
one more time, then Ubuntu started properly (and a new boot entry called
"ubuntu" appeared in the BIOS).
I don't know if this is possible, but it would be a
Before I submitted this, I had run the following command, per the web
page mentioned above.
sudo apt-get install libnl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1
libnl-genl-3-200=3.2.21-1
After submitting this, I ran the following commands:
sudo apt-get update
sudo apt-get install
Public bug reported:
I did an upgrade with "sudo apt-get dist-upgrade", and it removed
network-manager and network-manager-gnome. I could not connect to my LAN afer
that. I was able to find instructions for downgrading the libnl packages at
Public bug reported:
Bionic Beaver Final Beta doesn't install properly on my computer
(Thinkpad E480 with an NVMe SSD, no SATA disk). After finishing the
installation, the machine repeatedly shows these messages and reboots:
System BootOrder not found. Initializing defaults.
Creating boot entry
If you define "infinite" as longer than 10 seconds - yes. Something is
quite bogus here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
Can not ping IP addresses on remote network
in fact, the "host" command is hanging, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
Can not ping IP addresses on remote network after connect
To manage notifications about
I'm also affected. Looking at the process list (ps ax) I found:
23386 pts/4 S+ 0:00 openconnect -v -s /usr/share/vpnc-scripts/vpnc-script
vpn.example.com
23400 pts/4 S+ 0:00 /bin/sh -c /usr/share/vpnc-scripts/vpnc-script
23405 pts/4 S+ 0:00 /bin/sh /usr/share/vpnc-scripts/vpnc-script
23440 ?
sorry, above comment was meant to be added to bug 1752411.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731328
Title:
Periodically drops Tx frames and requires disconnect/reconnect
To manage
I'm also affected. Looking at the process list (ps ax) I found:
23386 pts/4S+ 0:00 openconnect -v -s
/usr/share/vpnc-scripts/vpnc-script vpn.example.com
23400 pts/4S+ 0:00 /bin/sh -c /usr/share/vpnc-scripts/vpnc-script
23405 pts/4S+ 0:00 /bin/sh
Apparently it is known for quite a while (read 6 years) that UPower has
some problem with dual battery systems:
https://bugs.freedesktop.org/show_bug.cgi?id=55278
** Bug watch added: freedesktop.org Bugzilla #55278
https://bugs.freedesktop.org/show_bug.cgi?id=55278
--
You received this bug
Joseph, since I am using the laptop as main working device I am very
reluctant to switch from the ubuntu custom kernel to mainline and let
the machine die willingly. I got a pointer via AskUbuntu
(https://askubuntu.com/questions/961278/how-to-prevent-shutdown-when-
one-of-two-batteries-is-empty)
patch above misses the device-tree, correction attached.
** Patch added: "db.diff"
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1333017/+attachment/5056934/+files/db.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: "patch to the machine db"
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1333017/+attachment/5053491/+files/db.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the late reply. Yes, current kernel works fine with the AC100.
I'll send an updated boot script and db patch. The old android/fastboot
bootloader is no longer used. The boot script should work on all tegras
AFAIK.
** Attachment added: "Boot script for Tegra SoCs (using uboot)"
reason the OS deemed it necessary to perform an emergency shutdown
without any warning.
I don't know whether this is a problem in gnome power management or the
kernel but please, please find a fix for this! Or provide some
workaround.
Best regards
Christoph Grimmer-Dietrich
** Affects: linux
Public bug reported:
during installation, when the bootloader should be written to a selected
partition the system hangs. System Ubuntu budgie 17.10 (downloaded).
release: 2.20.7-0ubuntu3 ?
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu
I'm running Ubuntu 17.04 on a Lenovo Thinkpad T460s. My Laptop just shut
down when the 2nd battery was empty and the 1st was at about 40%
capacity. That really sucks especially since this happend for the first
time in a year.
--
You received this bug notification because you are a member of
1 - 100 of 395 matches
Mail list logo
