[Bug 2019953] Re: plasma-discover crashes on exit
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2019953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964719] Re: GRUB shows up by default, even though GRUB_TIMEOUT=0
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_TIMEOUT=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1964719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968149] [NEW] grub ignores GRUB_TIMEOUT_STYLE when on efi+btrfs
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 so far, but what I'm seeing on boot is this:
1) the vendor logo
2) a password prompt beneath
3) a grub menu with a countdown
4) a bootsplash with the vendor logo
I'd like 3) to be gone, so I've set GRUB_TIMEOUT_STYLE to countdown, but
it does not seem to have any effect.
My /etc/default/grub looks like this:
GRUB_DEFAULT=0
# GRUB_HIDDEN_TIMEOUT=0
# GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_RECORDFAIL_TIMEOUT=5
GRUB_TIMEOUT=3
GRUB_TIMEOUT_STYLE=countdown
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash kaslr i915.alpha_support=1"
GRUB_CMDLINE_LINUX=""
GRUB_ENABLE_CRYPTODISK=y
My generated grub.cfg contains those two snippets which I guess are the cause:
function recordfail {
set recordfail=1
# GRUB lacks write support for btrfs, so recordfail support is disabled.
}
which is generated by the following lines in /etc/grub.d/00_header:
131 │ if [ "$quick_boot" = 1 ]; then
132 │ cat
[Bug 1964719] Re: GRUB shows up by default, even though GRUB_TIMEOUT=0
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 setting GRUB_RECORDFAIL_TIMEOUT.
--
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_TIMEOUT=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1964719/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878107] Re: flicker-free boot gets interrupted by GRUB menu
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 interrupted by GRUB menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1878107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
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/snapd/desktop. The session start adds some paths, but notably /usr/local/share and /usr/share are missing. I fixed it for me by wrapping the last lines of /usr/share/fish/vendor_conf.d/snapd.fish in an if: 12 │ if not set -q XDG_DATA_DIRS 13 │ if not contains $snap_xdg_path $XDG_DATA_DIRS 14 │ set XDG_DATA_DIRS $XDG_DATA_DIRS $snap_xdg_path 15 │ end 16 │ end -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] Re: [SRU] 2.54
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 -u snap_bin_path "@SNAP_MOUNT_DIR@/bin" +fish_add_path -aP $snap_bin_path -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 3.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958022] [NEW] fish integration broken in focal
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 called on line 294 of file /usr/share/fish/config.fish from sourcing file /usr/share/fish/config.fish called during startup I guess the fish integration was written for a newer version than the one I have. fish_add_path does not seem to exist here. The shell seems to work fine nevertheless, but it is still annoying. $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy snapd snapd: Installed: 2.54.2+20.04 Candidate: 2.54.2+20.04 Version table: *** 2.54.2+20.04 500 500 http://de.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.51.1+20.04ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.48.3+20.04 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2.44.3+20.04 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ apt-cache policy fish fish: Installed: 3.1.0-1.2 Candidate: 3.1.0-1.2 Version table: *** 3.1.0-1.2 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: snapd 2.54.2+20.04 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 15 15:27:14 2022 InstallationDate: Installed on 2011-11-29 (3699 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958022 Title: fish integration broken in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1958022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 3.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823299] Re: Package out of date
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.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1823299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913878] [NEW] dependency on gir1.2-poppler-0.18 missing
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/__init__.py", line 490, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2854,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2445,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2451,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/pympress/__main__.py", line 81, in
from pympress import extras, document, ui
File "/usr/lib/python3/dist-packages/pympress/extras.py", line 44, in
from pympress import document, builder, config
File "/usr/lib/python3/dist-packages/pympress/document.py", line 49, in
gi.require_version('Poppler', '0.18')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Poppler not available
Installing gir1.2-poppler-0.18 solved this problem.
Comparing this package to its Debian counterpart, some more dependencies
may be missing.
$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
$ env LANG=C apt-cache policy pympress
pympress:
Installed: 1.5.1+dfsg-3build1
Candidate: 1.5.1+dfsg-3build1
Version table:
*** 1.5.1+dfsg-3build1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pympress 1.5.1+dfsg-3build1
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sat Jan 30 14:47:37 2021
InstallationDate: Installed on 2011-11-29 (3349 days ago)
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
PackageArchitecture: all
SourcePackage: pympress
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: pympress (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913878
Title:
dependency on gir1.2-poppler-0.18 missing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pympress/+bug/1913878/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880393] Re: tootle crashes on start after logging 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: https://bugs.launchpad.net/tootle/+bug/1880393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887432] Re: configuration file //.config/debconf-kde-helperrc not writable
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 following:
DEBCONF_DB_OVERRIDE=Pipe{infd:none outfd:none}
DISPLAY=:0
DEBIAN_FRONTEND=kde
QT_LOGGING_RULES=org.kde.debconf.debug=false
PWD=/home/niklas
DEBCONF_DB_REPLACE=configdb
I'm a bit confused on how this came to be as
DebconfProxy._get_debconf_env copies os.environ first. But I couldn't
figure out where this function was really called from.
So, one possible solution would be to pass at least $HOME and $XDG_CONFIG_HOME.
(I'm not exactly sure how kconfig determines where to place the config file,
but I guess it's these two.)
Or just pass the whole environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887432
Title:
configuration file //.config/debconf-kde-helperrc not writable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1887432/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887432] [NEW] configuration file //.config/debconf-kde-helperrc not writable
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. Please contact your system administrator. This may be the same bug as #1851573, but I'm not sure. Also, the bug may be in debconf-kde-helper instead of aptdaemon, but again, I'm not sure. $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ env LANG=C apt-cache policy aptdaemon aptdaemon: Installed: 1.1.1+bzr982-0ubuntu32.1 Candidate: 1.1.1+bzr982-0ubuntu32.1 Version table: *** 1.1.1+bzr982-0ubuntu32.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.1.1+bzr982-0ubuntu32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: aptdaemon 1.1.1+bzr982-0ubuntu32.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 13 22:22:44 2020 InstallationDate: Installed on 2011-11-29 (3149 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all SourcePackage: aptdaemon UpgradeStatus: Upgraded to focal on 2020-05-16 (58 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-16T19:21:10.126162 ** Affects: aptdaemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887432 Title: configuration file //.config/debconf-kde-helperrc not writable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1887432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879150] Re: apport-kde shows 'text' instead of text in message box
** 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 Title: apport-kde shows 'text' instead of text in message box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879150] [NEW] apport-kde shows 'text' instead of text in message box
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-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal patch third-party-packages ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1879150/+attachment/5372875/+files/3e98f10f63f78f74.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878695] Re: filelight crashes when switching from root to home
*** 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: filelight crashes when switching from root to home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/filelight/+bug/1878695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665822] Re: fish crashed with SIGSEGV in __GI__IO_wfile_xsputn()
(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://bugs.launchpad.net/ubuntu/+source/fish/+bug/1665822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665822] Re: fish crashed with SIGSEGV in __GI__IO_wfile_xsputn()
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.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= -- 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://bugs.launchpad.net/ubuntu/+source/fish/+bug/1665822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"
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/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed: failed to
spawn /usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to
execute child process
?/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py?
The problem seems to be that in debian/rules this file is being deleted:
58 │ # Ubuntu-specific, broken
59 │ rm -f
$(INSTALLDIR)/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py
But it is still referenced in backends/aptcc/pk-backend-aptcc.cpp:
287 │ /**
288 │ * pk_backend_get_distro_upgrades:
289 │ */
290 │ void pk_backend_get_distro_upgrades(PkBackend *backend, PkBackendJob
*job)
291 │ {
292 │ pk_backend_spawn_helper(spawn, job, "get-distro-upgrade.py",
"get-distro-upgrades", NULL);
293 │ }
Newer upstream versions of PackageKit (1.1.13) seem to have this file
removed - and also the reference in backends/aptcc/pk-backend-aptcc.cpp.
** Also affects: packagekit (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/1709699
Title:
gpk-update-viewer fails with "Spawn of helper
'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ...
(No such file or directory)"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709699 Title: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869576] [NEW] partition screen shows wrong size below bar
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.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 29 13:48:03 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-03-29 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal iso-testing ubiquity-20.04.6 ** Attachment added: "screenshot of the partition screen" https://bugs.launchpad.net/bugs/1869576/+attachment/5342917/+files/20.04-ubiquity-part.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869576 Title: partition screen shows wrong size below bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869438] [NEW] systemsettings crashes when opening regional settings
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:20.04 user@user-VirtualBox:~$ LANG=C.utf8 apt-cache policy systemsettings systemsettings: Installed: 4:5.18.3-0ubuntu1 Candidate: 4:5.18.3-0ubuntu1 Version table: *** 4:5.18.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status user@user-VirtualBox:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemsettings 4:5.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 27 22:21:52 2020 InstallationDate: Installed on 2020-03-27 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200327) SourcePackage: systemsettings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemsettings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "systemsettings5-20200327-222709.kcrash.txt" https://bugs.launchpad.net/bugs/1869438/+attachment/5342348/+files/systemsettings5-20200327-222709.kcrash.txt -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to systemsettings in Ubuntu. https://bugs.launchpad.net/bugs/1869438 Title: systemsettings crashes when opening regional settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1869438/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1565950] Re: Grub 2 fails to boot a kernel on a luks encrypted volume with Secure Boot enabled
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 boot a kernel on a luks encrypted volume with Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1565950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851380] Re: root can lift kernel lockdown
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 secure, but more difficult to achieve. I don't think this can be solved in Ubuntu, so let's continue this discussion in the first upstream issue you linked. (Although I'd probably need to take a look at the source code and I don't know any C#.) -- 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 lift kernel lockdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851380] Re: root can lift kernel lockdown
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 lift kernel lockdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769848] Re: wodim no longer works from non-root accounts
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/1769848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851380] Re: root can lift kernel lockdown
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-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/1851380 Title: root can lift kernel lockdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851380] Re: root can lift kernel lockdown
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/5df4c5562f191b434edf57e8c92b176baad37cba. (Debian also seems to be affected: https://salsa.debian.org/kernel-team/linux/blob/4dcfa860/debian/patches/features/all/lockdown/0002-Add-a-SysRq-option-to-lift-kernel-lockdown.patch) -- 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 lift kernel lockdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844666] Re: [SRU] [bionic] new upstream microrelease flatpak 1.0.9
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 Ubuntu. https://bugs.launchpad.net/bugs/1844666 Title: [SRU] [bionic] new upstream microrelease flatpak 1.0.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1844666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621803] Re: package python3-scipy 0.17.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 Ubuntu. https://bugs.launchpad.net/bugs/1621803 Title: package python3-scipy 0.17.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1621803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
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/1683761 Title: undefined symbol: tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/gradle/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743534] [NEW] package is outdated - current version is 0.8.9
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: 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/1743534 Title: package is outdated - current version is 0.8.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hyde/+bug/1743534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)
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/duplicity", line 1532, in with_tempdir(main) File "/usr/bin/duplicity", line 1526, in with_tempdir fn() File "/usr/bin/duplicity", line 1380, in main do_backup(action) File "/usr/bin/duplicity", line 1405, in do_backup globals.archive_dir).set_values() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, in set_values self.get_backup_chains(partials + backend_filename_list) File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 835, in get_backup_chains add_to_sets(f) File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 829, in add_to_sets if new_set.add_filename(filename): File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, in add_filename self.set_manifest(filename) File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 149, in set_manifest self.set_files_changed() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, in set_files_changed mf = self.get_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, in get_manifest return self.get_local_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 225, in get_local_manifest return manifest.Manifest().from_string(manifest_buffer) File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 207, in from_string assert filecount == len(self.files_changed) AssertionError This bug is marked as fixed but I haven't seen an update for Zesty. Did I miss something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538333 Title: AssertionError in manifest.py: assert filecount == len(self.files_changed) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1538333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464064] Re: Ubuntu apt repos are not available via HTTPS
*** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464064 Title: Ubuntu apt repos are not available via HTTPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1464064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
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. ** Attachment added: "a snippet from dmesg; problem occurs at 15:15" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904/+attachment/4892288/+files/grafikcrash-2017-06-08.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
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 manage notifications about this bug go to: https://bugs.launchpad.net/gradle/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
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 failed with an exception. * What went wrong: java.lang.ExceptionInInitializerError (no error message) * Try: Run with --info or --debug option to get more log output. * Exception is: java.lang.ExceptionInInitializerError at org.gradle.initialization.DefaultClassLoaderRegistry.restrictTo(DefaultClassLoaderRegistry.java:40) at org.gradle.initialization.DefaultClassLoaderRegistry.restrictToGradleApi(DefaultClassLoaderRegistry.java:36) at org.gradle.initialization.DefaultClassLoaderRegistry.(DefaultClassLoaderRegistry.java:30) at org.gradle.internal.service.scopes.GlobalScopeServices.createClassLoaderRegistry(GlobalScopeServices.java:215) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:547) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73) at org.gradle.internal.service.DefaultServiceRegistry.invoke(DefaultServiceRegistry.java:462) at org.gradle.internal.service.DefaultServiceRegistry.access$1200(DefaultServiceRegistry.java:84) at org.gradle.internal.service.DefaultServiceRegistry$FactoryMethodService.invokeMethod(DefaultServiceRegistry.java:796) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:752) at org.gradle.internal.service.DefaultServiceRegistry$ManagedObjectProvider.getInstance(DefaultServiceRegistry.java:589) at org.gradle.internal.service.DefaultServiceRegistry$SingletonService.get(DefaultServiceRegistry.java:634) at org.gradle.internal.service.DefaultServiceRegistry.applyConfigureMethod(DefaultServiceRegistry.java:253) at org.gradle.internal.service.DefaultServiceRegistry.findProviderMethods(DefaultServiceRegistry.java:214) at org.gradle.internal.service.DefaultServiceRegistry.addProvider(DefaultServiceRegistry.java:352) at org.gradle.internal.service.ServiceRegistryBuilder.build(ServiceRegistryBuilder.java:52) at org.gradle.launcher.cli.BuildActionsFactory.createGlobalClientServices(BuildActionsFactory.java:153) at org.gradle.launcher.cli.BuildActionsFactory.runBuildWithDaemon(BuildActionsFactory.java:108) at org.gradle.launcher.cli.BuildActionsFactory.createAction(BuildActionsFactory.java:83) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.createAction(CommandLineActionFactory.java:249) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:239) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:217) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:210) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:174) at org.gradle.launcher.Main.doAction(Main.java:33) at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:547) at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60) at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37) at org.gradle.launcher.GradleMain.main(GradleMain.java:23) Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected java.lang.Package[] java.lang.ClassLoader.getPackages() accessible: module java.base does not "opens java.lang" to unnamed module @2657d4dd at
[Bug 1363896] Re: [needs-packaging] pypy3
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/ubuntu/+source/pypy/+bug/1363896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
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.20160922T090645Z.to.20160929T083644Z.sigtar.gz, it might work
again.
But this is really not good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652918] Re: systemd-sysctl crashes when there's a comment at the end of a line
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 of a line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652918] [NEW] systemd-sysctl crashes when there's a comment at the end of a line
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.service - Apply Kernel Variables Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2016-12-27 18:31:50 CET; 16h ago Docs: man:systemd-sysctl.service(8) man:sysctl.d(5) Process: 770 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE) Main PID: 770 (code=exited, status=1/FAILURE) Dez 27 18:31:50 panzersperre systemd[1]: Starting Apply Kernel Variables... Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Main process exited, code=exited, stat Dez 27 18:31:50 panzersperre systemd[1]: Failed to start Apply Kernel Variables. Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Unit entered failed state. Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'. niklas@panzersperre~> sudo /lib/systemd/systemd-sysctl Couldn't write '1 #176' to 'kernel/sysrq', ignoring: Invalid argument niklas@panzersperre~> sysctl kernel.sysrq kernel.sysrq = 1 niklas@panzersperre~> lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 niklas@panzersperre~> env LANG=C apt-cache policy systemd systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages niklas@panzersperre~> /lib/systemd/systemd-sysctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652918 Title: systemd-sysctl crashes when there's a comment at the end of a line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540406] Re: warning: file-aligned section .text extends beyond end of file
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540406 Title: warning: file-aligned section .text extends beyond end of file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1540406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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 Ubuntu. https://bugs.launchpad.net/bugs/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
This is the thread on the mailing list: https://marc.info/?t=14681417051=1=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 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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 from standby works without and not with it.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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 MISS: mv88e6xxx_drv MISS: phy-generic MISS: snd-soc-atmel-pcm MISS: snd-soc-sst-bytcr-dpcm-rt5640 MISS: snd-soc-wm8804 MISS: tc3589x-keypad MISS: tpm_i2c_stm_st33 NEW : spi-cadence NEW : comedi_8254 NEW : nhc_hop NEW : btbcm NEW : nhc_routing NEW : snd-soc-sst-bytcr-rt5640 NEW : vfio_virqfd NEW : nhc_dest NEW : nhc_udp NEW : snd-soc-sst-ipc NEW : btintel NEW : nhc_mobility NEW : usb_f_printer NEW : nhc_fragment NEW : snd-hda-core NEW : nhc_ipv6 read 4337 modules : new(16) missing(12) EE: Missing modules (start begging for mercy) I'm at d0a3997. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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: iwlwifi: Microcode SW error detected. Restarting 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
** 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 + A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: niklas 2175 F pulseaudio - /dev/snd/controlC0: niklas 2175 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: niklas 2175 F pulseaudio + /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. - - lxcbr0no wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. + + lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-22-generic N/A - linux-backports-modules-4.4.0-22-generic N/A - linux-firmware1.157 + linux-restricted-modules-4.4.0-22-generic N/A + linux-backports-modules-4.4.0-22-generic N/A + linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO ** 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 error detected. Restarting 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
** 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: iwlwifi: Microcode SW error detected. Restarting 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
** 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 error detected. Restarting 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] [NEW] iwlwifi: Microcode SW error detected. Restarting 0x2000000
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 reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Attachment added: "a snippet from the systemd journal" https://bugs.launchpad.net/bugs/1588637/+attachment/4675656/+files/iwlwifi-error.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: iwlwifi: Microcode SW error detected. Restarting 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252484] Re: Possible data loss when restarting in the middle of a deleted file
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 notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1252484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
