apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810379/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810377/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
st
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810378/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Ti
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810374/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810376/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
st
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810375/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Titl
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810373/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/207
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810372/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810371/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810370/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810369/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
st
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810368/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810367/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810366/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810365/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
stan
apport information
** Tags added: apport-collected
** Description changed:
I'm on Ubuntu 22.04 with HWE, so I recently got the upgrade from 6.5 to
6.8 and since then, standby doesn't work anymore. The screen goes black,
the keyboard backlight goes off and the status LED goes from on to
f
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810364/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810363/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2077575/+attachment/5810362/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
standb
The laptop also won't power off after shutting down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077575
Title:
standby broken on ThinkPad 260 Yoga with 6.8
To manage notifications about this bug
$ apport-collect 2077575
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=...&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about you
Public bug reported:
I'm on Ubuntu 22.04 with HWE, so I recently got the upgrade from 6.5 to
6.8 and since then, standby doesn't work anymore. The screen goes black,
the keyboard backlight goes off and the status LED goes from on to
fading, but the fan and the LEDs on the keyboard stay on.
The la
Public bug reported:
I'm on Ubuntu 22.04 HWE, so the kernel switched from 6.5 to 6.8 recently
and the newly generated initramfs is missing the CPU microcode:
[…]
dracut: Generating /boot/initrd.img-6.5.0-45-generic
Mode: real
Files: 664
Linked: 2 files
Compared: 0
Well, the bad experience comes from disabling the feature. :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1999345
Title:
please add luks2 module to the signed grub2 images
To manage notifications
This hasn't happened in a long time, yes. (And I'm still on 22.04.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2019953
Title:
plasma-discover crashes on exit
To manage notifications about this b
you probably can, but you won't be able to enter grub anymore, so I
wouldn't recommend it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964719
Title:
GRUB shows up by default, even though GRUB_TIME
Public bug reported:
I'm using grub2, but with a configuration that may be a bit special:
1) I'm using native UEFI boot.
2) I have / formatted using btrfs (and no external /boot).
3) / is contained inside a LUKS volume with just grub on the ESP. (with
GRUB_ENABLE_CRYPTODISK=y)
Everything works s
If I take a look at /boot/grub/grub.cfg I see the lines:
function recordfail {
set recordfail=1
# GRUB lacks write support for btrfs, so recordfail support is disabled.
}
So, I guess this is intentional, at least.
Are you booting via UEFI or BIOS?
I could at least reduced the timeout by set
I have the same problem.
I guess this relates to
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/425979?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878107
Title:
flicker-free boot gets int
Oh, sorry. I had 2.54.3+20.04.1ubuntu0.1 installed, the newer one seems to
mostly work.
I can log in and snap apps appear in the menu.
XDG_DATA_DIRS now contains /var/lib/snapd/desktop twice, but that does not seem
to be a major problem.
--
You received this bug notification because you are a m
The new snapd release 2.54.3+20.04.1ubuntu0.2 in focal makes this error message
go away for me, but it completely broke my (Plasma) desktop session, because
XDG_DATA_DIRS was not set before (making something fill it on start; don't know
where that happens), but it now contains only /var/lib/snap
It would be really nice if someone could take a look at
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1958022 before this
gets widely released to Focal.
I guess this part in data/env/snapd.fish.in is the culprit:
+# Expand $PATH to include the directory where snappy applications go.
+set -
I used the new version on Focal for about a day now and everything seems
to work fine. I can see the new users that I haven't seen before and
messages are received immediately.
I didn't try chatting with any new user or creating a call though.
Thanks!
--
You received this bug notification becau
Public bug reported:
After upgrading snapd from 2.51.1+20.04ubuntu2 to 2.54.2+20.04 I get the
following stacktrace upon each start of the fish shell:
/usr/share/fish/vendor_conf.d/snapd.fish (line 3):
fish_add_path -aP $snap_bin_path
^
from sourcing file /usr/share/fish/vendor_conf.d/snapd.fish
The messages in the popup in the app are getting more aggressive. Also,
new messages are sometimes not received until I restart the application.
Is there anything happening here or do I need to switch to a flatpak or
snap or something?
--
You received this bug notification because you are a membe
Telegram 2.1.7 in Focal is now also showing this popup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823299
Title:
Package out of date
To manage notifications about this bug go to:
https://bugs.l
Public bug reported:
I installed pympress and it failed to start with the following
exception:
Traceback (most recent call last):
File "/usr/bin/pympress", line 11, in
load_entry_point('pympress==1.5.1', 'gui_scripts', 'pympress')()
File "/usr/lib/python3/dist-packages/pkg_resources/__in
Is there a chance to get this backported to focal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880393
Title:
tootle crashes on start after logging in
To manage notifications about this bug go to
I don't get this message when using pkcon, so I figured it might be
interesting to compare the different environments debconf-kde-helper
runs in when invoked by each of those.
When invoked by pkcon, it has access to a whole load of environment variables.
When invoked by aptdcon, it only sees the f
Public bug reported:
I'm using "aptdcon --refresh" and "aptdcon --full-upgrade" to update my
system.
I'm getting the following informational message on every upgrade (twice
on start and twice on end):
debconf-kde-helper - KDialog
Configuration file "//.config/debconf-kde-helperrc" not writable.
** Patch added: "apport-kde.patch"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+attachment/5372882/+files/apport-kde.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879150
T
Public bug reported:
I had some other software crashing and wanting to report a bug, Apport
displayed a pretty nonsensical message box (see the screenshot).
$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
$ apt-cache policy apport-kde
apport-kde:
Installed: 2.20.11-0ubu
*** This bug is a duplicate of bug 1758629 ***
https://bugs.launchpad.net/bugs/1758629
I can't look at bug #1758629 as it is private.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878695
Title:
(um, I'm on 18.04.4 amd64)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665822
Title:
fish crashed with SIGSEGV in __GI__IO_wfile_xsputn()
To manage notifications about this bug go to:
https://bu
I think I'm affected by the same bug. The weird thing is: I think I only
get this when starting Atom but I'm not sure.
It sure doesn't crash one of the shells I'm actively using. I just get
the "an application on your system has crashed" dialog.
$ locale
LANG=de_DE.UTF-8
LANGUAGE=
LC_CTYPE="de_DE
I think this is really a bug in packagekit. On 18.04 I can also trigger
this by just running pkcon get-distro-upgrades in a terminal:
Transaction:Getting upgrades
Status: Waiting in queue
Status: Starting
Status: Finished
Results:
Fatal error: Spawn of helper
'/usr/sha
** Patch added: "patch removing pk_backend_get_distro_upgrades and disabling
the feature"
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1709699/+attachment/5360831/+files/remove-get-distro-upgrades.patch
--
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
I was installing Kubuntu 20.04 to an empty (virtual) hard disk.
It had the size of about 20GB (as you can see in the drop-down), but the
preview show the new system as "1.0 B" which is a bit small.
(The installation worked as expected, so that's not a big issue for me.)
Pro
Public bug reported:
Opening the main regional settings page makes systemsettings crash.
The timezone page, the spellcheck page and the formats page work, but the
language one does not.
user@user-VirtualBox:~$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:
I just ran into this bug on bionic with a pretty custom configuration.
Is there any chance that this can be backported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565950
Title:
Grub 2 fails to b
Yes, there are solutions to this that don't expose the whole kernel to
root.
* This project's kernel module could use DKMS. This could make use of the MOK
workflow already present in Ubuntu.
* This project's kernel module could be included in the upstream kernel.
The last option would be more
So, um, is there a simple way to get this fix into the other affected
distributions or do I have to open an issue in each one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851380
Title:
root can l
Comment #3 suggested to set CDR_FIFOSIZE=6m in /etc/wodim.conf. This did
work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769848
Title:
wodim no longer works from non-root accounts
To ma
I can confirm that this bug is fixed in bionic:
# echo "x" > /proc/sysrq-trigger
Nov 14 20:38:58 panzersperre kernel: sysrq: SysRq :
Nov 14 20:38:58 panzersperre kernel: This sysrq operation is disabled from
userspace.
I don't have a disco or eoan to test.
** Tags removed: verification-needed
I'm no expert in either kernel or C programming and I didn't test this
patch, but it looks good to me.
Also, the resulting code is quite similar to the one Fedora is currently using
- they accidentally fixed this bug in
https://src.fedoraproject.org/rpms/kernel/c/5df4c5562f191b434edf57e8c92b176b
For me this message mentions multiple supported versions: flatpak
(1.4.2;1.2.5;1.0.9;)
So updating from 1.0.8 to 1.0.9 would be enough to be able to update
org.freedesktop.Platform.openh264.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I encountered the same problem today, but with scipy 0.19.1-2ubuntu1 in Bionic.
sudo apt install --reinstall python\*-decorator also solved this for me.
@shirayann are you still working on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes, there's a workaround.
You can install the package (with the same version) from Debian:
https://packages.debian.org/stretch/libnative-platform-jni
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/168
Public bug reported:
Hyde hasn't been updated it a while - the current upstream version is 0.8.9
since 2015 (see https://pypi.org/project/hyde/#history).
Still, Ubuntu ships 0.8.5 for quite a while.
It would be great if the package could be updated.
** Affects: hyde (Ubuntu)
Importance: Und
I've just experienced this bug on Zesty with duplicity 0.7.06-2ubuntu3.
I was doing a full backup when the underlying filesystem disappeared (partly my
fault).
I remounted it and trying to resume the backup, but duplicity won't start with
Traceback (most recent call last):
File "/usr/bin/duplic
*** This bug is a duplicate of bug 1186793 ***
https://bugs.launchpad.net/bugs/1186793
Is this really a duplicate?
The other bug is about the update process using HTTP.
This bug is about the mirrors not supporting HTTPS.
--
You received this bug notification because you are a member of Ubun
This is relatively hard to reproduce. It happens sometimes directly
after boot and login, sometimes after more than a week uptime.
I've simply selected an older kernel at boot (4.8.0-46-generic; the
newest one I had installed from Yakkety) and I didn't experience a
crash, yet.
--
You received th
I'm experiencing the same issue for a while now. I think it occurred
after I upgraded form Yakkety to Zesty.
I'm currently on 4.10.0-21-generic.
I think the issue is more likely to happen when I run CPU and / or RAM
intensive applications.
If this happens, all my screens are stuck.
** Attachmen
It is still weird that this problem doesn't appear with the Debian
package. They are both the same version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683761
Title:
undefined symbol: tgetent
To
I've ran into the same issue.
After reading
https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1238322/comments/8,
I installed the package from Debian: https://packages.debian.org/sid
/libnative-platform-jni.
This works only partially. It fails with a different error message:
FAILURE: Build f
Is this likely to happen anytime soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363896
Title:
[needs-packaging] pypy3
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Since I've upgraded to yakkety, this issue seems to be gone.
But the weird thing is: I'm not even able to reproduce it with a live
version of xenial with the exact same software I ran when I first
encountered the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I think I've got the same problem.
DejaDup with Ubuntu 16.04 prints the same error message and even
duplicity can't do anything in the backup folder. ("remove-older-than"
fails with "(, IOError('CRC check failed
0xb1276c7b != 0x9b944aa5L',), )".)
If I delete or move duplicity-new-
signatures.2016
This seems to be fixed in systemd 231. (Tested with a recent version of
Fedora.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652918
Title:
systemd-sysctl crashes when there's a comment at the end
Public bug reported:
I have this line in /etc/sysrq.d/10-magic-sysrq.conf:
kernel.sysrq = 1 #176
This has worked in Ubuntu 14.04.
Although there are errors and warnings, the setting seems to be applied
on boot.
niklas@panzersperre~> systemctl status systemd-sysctl.service
● systemd-sysctl.serv
This doesn't work for me. (But I've got a 7265D and not a 7260.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588637
Title:
iwlwifi: Microcode SW error detected. Restarting 0x200
To manage n
Just got this warning when installing linux-signed-
image-4.4.0-51.72-generic:
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section table?
And the new kernel won't boot.
The old one still works.
--
You received this
So, this seems to be the same bug as
https://bugzilla.kernel.org/show_bug.cgi?id=114501.
** Bug watch added: Linux Kernel Bug Tracker #114501
http://bugzilla.kernel.org/show_bug.cgi?id=114501
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is the thread on the mailing list:
https://marc.info/?t=14681417051&r=1&w=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588637
Title:
iwlwifi: Microcode SW error detected. Restarting 0x
Yes, this problem still occurs with 4.7-rc6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588637
Title:
iwlwifi: Microcode SW error detected. Restarting 0x200
To manage notifications about t
I didn't manage to bisect the commits because every version failed to
build.
Then I started from 4.1.0-1 and reverted commits with "iwlwifi" in the
title.
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
wily.git/commit/?id=8d193ca26cc28019e760b77830295a0c349d90dc seems to be
the culprit. (Resuming fr
I can't build the second commit to test.
The build fails with the following:
II: Checking modules for generic...
reading new modules...read 4341 modules.
reading old modules...
MISS: bcm_sf2
MISS: dsa_core
MISS: hid-huion
MISS: intel_mid_dma
MISS: mv88e6060
So, I'm done with versions bisecting. The issue has been introduced
somewhere between 4.0.0-4 and 4.1.0-1.
I'll commit bisect later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588637
Title:
iw
** Description changed:
My wifi won't work after I wake my laptop up from standby.
This problem looks quite the same as #1099487 or #944271.
But I experienced this bug on Xenial with 4.4.0-22-generic (amd64).
- A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" doesn't solve the
I've tested it with rc2 and rc3.
It does still happen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588637
Title:
iwlwifi: Microcode SW error detected. Restarting 0x200
To manage notificati
** Attachment added: "iwlwifi.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+attachment/4685023/+files/iwlwifi.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588637
Title:
** Tags added: kernel-bug-exists-upstream
** 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/1588637
Title:
iwlwifi: Microcode SW er
This error occurs in 4.4.0-21-generic as well, but not in
3.19.0-59-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588637
Title:
iwlwifi: Microcode SW error detected. Restarting 0x200
Public bug reported:
My wifi won't work after I wake my laptop up from standby.
This problem looks quite the same as #1099487 or #944271.
But I experienced this bug on Xenial with 4.4.0-22-generic (amd64).
A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" doesn't solve the
problem. (A reboo
I'm not affected with duplicity 0.7.06 on Ubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted file
To manage not
85 matches
Mail list logo
