** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/prepare-package-
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Thank you for your reply Antoine,
As this wasn't a confirmed bug we're closing this report as being
"Invalid".
Thank you again for helping make Ubuntu better.
Paul White
[Ubuntu Bug Squad]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificati
** Changed in: f-spot
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/174117
Title:
Intro key to exit edit mode
To manage notifications about this bug go to:
https://b
:D
Well I most certainly hope people can *think* when they see the lines are
active by default.
Good luck to anyone who's trying to fix this bug !
Cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Hi Thiago, thank you for this suggestion - and for this app.
Unfortunately, aforemetioned workaround doesn't seems to work for me:
renat@renat-Lenovo-B50-80:~$ cd ~/dev/invesalius3
renat@renat-Lenovo-B50-80:~/dev/invesalius3$ export
PYTHONPATH=/usr/lib/python2.7/dist-packages/wxPython-4.0.1-py2.7
Same problem here reproducible on Ubuntu 18.04 LTS. SATA RAID 10 with
XFS filesystem. On each reboot the RAID does a resync. Any operation on
the RAID before the resync is finished causes the process to hang. Might
be also associated with another issue that causes the resync every time
on boot.
--
** Also affects: mate-themes (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-mate-artwork (Ubuntu)
Importance: Undecided
Status: New
** Also affects: light-themes (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification be
Sorry for my deleted comment, since you said "it's most likely THE issue
with..." I thought you were referring to some specific issue that you
failed to mention. I assume you meant "most likely AN issue with".
Anyway,
The icon is EXPECTED to become red when a sound plays and the volume is
muted.
The icon is EXPECTED to become red when a sound plays and the volume is
muted.
The issue is that the icon doesn't go back to normal and REMAINS red
when the sound is finished playing.
I find it hard to believe this is an issue with an icon-theme, but if
that is the case, could you please point to
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
** No longer affects: light-themes (Ubuntu)
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782722
Title:
MATE themes like Ambiant-MATE and Green-Submarine should h
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Public bug reported:
This issue was found on Bionic s390x zKVM and zVM
# http_proxy=http://squid.internal:3128 autopkgtest lxc -- null
autopkgtest [13:40:51]: version 5.3.1
autopkgtest [13:40:51]: host kernel02; command line: /usr/bin/autopkgtest lxc
-- null
autopkgtest [13:40:51]: testbed dpkg
Thanks for help
Have a nice day ;)
2018-07-20 13:10 GMT+02:00 paul <1779...@bugs.launchpad.net>:
> hello
>
> after this answer
>
> I did like Dimitri wrote
> hello
>
> Hello
> sudo apt-get install --reinstall hplip hplip-data
> sudo apt-get install --reinstall python3
>
> solve my problem very
Installed a clean bionic install, made sure grub2 binaries are at
version 2.02-2ubuntu8.1, running `sudo update-grub` resulted in printing
out the Warning: message. Then upgraded all grub2 binaries to
2.02-2ubuntu8.2 from bionic-proposed, re-ran the command and confirmed
no message is visible.
--
BTW it will be great if the error message can be more specific. (like
source package not found 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/1782750
Title:
Failed to start autopkgtest
It turns out that the deb-src was not fully enabled.
Closing this bug with Invalid.
** Changed in: autopkgtest (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire d
Public bug reported:
error
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libfreerdp-client2-2 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
libwinpr2-2:amd64: Install
libfre
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Hi,
Thanks for fixing the issue! I didn't see it the last weeks anymore, so
I think you can close the ticket.
Best regards
Martin
Am 20.07.2018 um 02:24 schrieb gf:
> Hello Martin,
> Thank you for submitting this bug and reporting a problem with text missing
> after suspend. You made this bu
Pablo, this bug is specifically for 18.04+ (Bionic and above).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746992
Title:
[SRU] gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3
co
** Description changed:
This issue can be found on different architectures of the Bionic kernel.
Steps:
- 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-b master-next
- 2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
- 3. rm -fr autotest/clie
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire d
You have a broken third party init script installed named "discagent".
You will need to remove it.
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire d
4.15.0-29.31 - generic
Regression test CMPL, RTB.
Issue to note in amd64:
monotonic_time - lodygin constantly failed with tsc test (bug 1732620)
ubuntu_kvm_unit_tests - 28 failed on amaura, 16 failed on harpo, 4 failed on
lodygin, 11 failed on michael
ubuntu_ltp_syscalls - inotify08 failed
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire d
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire d
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire d
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire d
*** This bug is a duplicate of bug 1718658 ***
https://bugs.launchpad.net/bugs/1718658
Doing a manual mount like so (used for safely storing private data in
the cloud) used to work since Ubuntu 12 or so.
However, today after updating from Ubuntu 16.04 LTS to 18.04 LTS, the
entire thing wouldn
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire d
It looks like your hard disk crashed during the install; you will need
to replace it.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781
This issue is gone after we migrated from XFS to EXT4, so it is
definitely XFS-related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767992
Title:
Linux md raid-10 freezes during resync
To manage
4.4.0-131.157 - lowlatency
Regression test CMPL, RTB.
Issue to note in amd64:
ubuntu_kvm_unit_tests - test failed to build (bug 1782120)
ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387)
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784)
fanotify07/fanotify08
If those files are being re-copied every kernel upgrade, then that is
probably something that should not be happening. They should only be
copied on grub-install, not update-grub.
The performance problems caused by discard on a root fs probably do not
apply to the ESP.
** Changed in: ubiquity (
*** This bug is a duplicate of bug 1718658 ***
https://bugs.launchpad.net/bugs/1718658
Oops sorry, I missed the duplicate warning!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726873
Title:
m
#26 fixed this for me.
Doing a manual mount like so (used for safely storing private data in
the cloud) used to work since Ubuntu 12 or so.
However, today after updating from Ubuntu 16.04 LTS to 18.04 LTS, the
entire thing wouldn't mount anymore:
```
$ echo mypassphrase | sudo ecryptfs-add-passp
Ah, looks like a different behaviour between testparm and samba-tool
testparm:
root@xenial-samba-include:~# testparm -s &>/dev/null; echo $?
0
root@xenial-samba-include:~# samba-tool testparm; echo $?
ERROR: Unable to load default file
255
--
You received this bug notification because you are a
Public bug reported:
Node: n1-highcpu-4
tag=inotify09 stime=1532045405
cmdline="inotify09"
contacts=""
analysis=exit
<<>>
tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
Test timeouted, sending SIGKILL!
tst_test.c:1055: INFO: If you are running on slow machine, try exporting
LTP_TIMEOUT_MUL
Public bug reported:
When viewing multiple videos fullscreen in sequence the image sometimes
block. Here are the steps to reproduce:
1. Create a folder with multiple videos in any format
2. Launch vlc by running something like "vlc *.mp4"
3. Make the video fullscreen by pressing F
4. Skip through
** Changed in: samba (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583324
Title:
Samba won't start when an include statement in smb.conf has a variable
4.4.0-1063.72 - aws
Regression test CMPL, RTB.
Issue to note in x86_64 (aws):
libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 1, bad config 3,
only spotted on t2.small, passed on the rest
ubuntu_kvm_unit_tests - test skipped due to no KVM support
ubuntu_ltp_syscalls - inotify07 fa
when i open this file link it shows the following information-
cat -n /etc/apt/sources.list.d/whatsie.listPackage: whatsie
Version: 2.0.15-442
License: MIT
Vendor: Alexandru Rosianu
Architecture: amd64
Maintainer: Alexandru Rosianu
Installed-Size: 140273
Depends: libappindicator1 | libappindicato
The test needs to be fixed.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin
(cypressyew)
--
You received this bug notificat
As a workaround, if you replace the indicated line in /etc/init.d/samba-ad-dc,
does it work?
--- /etc/init.d/samba-ad-dc.orig2018-07-20 13:33:22.418002978 +
+++ /etc/init.d/samba-ad-dc 2018-07-20 13:33:34.966042631 +
@@ -27,7 +27,7 @@
case "$1" in
start)
-
Mark, you reported this bug some time ago and there have been many
changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue so the bug report can now be closed? If we do not hear from you
the bug report will close itself in approximately two
Mark, you reported this bug some time ago and there have been many
changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue so the bug report can now be closed? If we do not hear from you
the bug report will close itself in approximately two
Yahya, you reported this bug some time ago and there have been many
changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue so the bug report can now be closed? If we do not hear from you
the bug report will close itself in approximately tw
linfan, you reported this bug some time ago and there have been many
changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue. So the bug report can now be closed? If we do not hear from you
the bug report will close itself in approximately
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/prepare-package-me
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-signe
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/prepare-package-lbm
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
878c33a does NOT have 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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
To manage notification
Werner, you reported this bug some time ago and there have been many
changes in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue. So the bug report can now be closed? If we do not hear from you
the bug report will close itself in approximately
AK, you reported this bug some time ago and there have been many changes
in Ubuntu since that time.
Presumably this problem was a one time occurrence and/or is no longer an
issue? So the bug report can now be closed? If we do not hear from you
the bug report will close itself in approximately two
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, the report indicates that an error report from openjdk was created at
/hs_err_pid8655.log, could you please attach any hs_err log files that you
hav
This bug was fixed in the package lttng-modules - 2.10.5-1ubuntu3
---
lttng-modules (2.10.5-1ubuntu3) cosmic; urgency=medium
* ubuntu_lttng_smoke_test failed on Azure 4.15 (LP: #1778642)
-
debian/patches/0009-Fix-do-not-use-CONFIG_HOTPLUG_CPU-for-the-new-hotplu.patch
- debi
** Changed in: screen (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: screen (Ubuntu)
Status: Triaged => In Progress
** Also affects: screen (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Bion
Thanks Corey Bryant
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746992
Title:
[SRU] gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3
conflicts with the python 2 version
To manag
Public bug reported:
Borked upgrade from 17:10 to 18:04
I had to go into Recovery Root and enter dpkg --configure -a
On reboot it appears that it's trying to "reverse upgrade"
ie: Bionic to Aardvark
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libapparmor1:amd64 2.11.0-2ubuntu17.1
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782785
Title:
package libapparmor1:amd64 2.11.0-2ubuntu17.1 failed to
install/upgrade: package libapparmor1:amd
Yes, this bug can be closed.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794423
Title:
Firefox 4 sometimes forgets that I
Hello Mark, or anyone else affected,
Accepted screen into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/screen/4.6.2-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
J'ai fait comme Dimitri a écrit
sudo apt-get install --reinstall hplip hplip-data
sudo apt-get installer --réinstall python3
Merci Excelent
JeanMa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Decided to not wait for this to get kernels released.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782183
T
Decided to not wait for this to get kernels released.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782186
T
Decided to not wait for this to get kernels released.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782185
T
Decided to not wait for this to get kernels released. Also for hwe-edge
there is no extra testing needed as it is the same as hwe.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bu
Decided to not wait for this to get kernels released.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782178
T
Overriding manually to get the kernels out.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782183
Title:
Decided to not wait for this to get kernels released.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782176
T
Pablo or anyone else affected, the fix for this bug is also available in
the queens-proposed cloud archive but the bug wasn't auto-updated for
some reason. Marked as fix-commited for queens cloud archive.
** Changed in: cloud-archive/queens
Status: Triaged => Fix Committed
--
You received
Any help verifying this bug would be very much appreciated! Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746992
Title:
[SRU] gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3
I am with comment #73 to #76 entirely. Anyhow. Not sure to what degree
this suggestion is still relevant, but I would like to add a tiny bit
more to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: cloud-init (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I upgraded from 16.04 to 18.04. Same problem with the exception that I
can't switch to the login screen from the lock screen by hitting a key.
I need to press CTRL-ALT-F1 to get to the login screen. Then I can log
in to get back to my session.
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification because you
Public bug reported:
This looks like has already been fixed for Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1594900
Ubuntu 18.04
I'm using the latest pidgin-sipe 1.23.2-1
pidgin version 1:2.12.0-1ubuntu4
remmina version 1.2.0-rcgit.29+dfsg-1ubuntu1
When trying to accept a screenshare in
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification because you
Pablo, I misspoke earlier. This is available on xenial via the queens
cloud-archive.
sudo add-apt-repository cloud-archive:queens-proposed
sudo apt-get update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Solution in #123 did not work for me, even with higher sleep time.
So I have to switch back to lightdm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphica
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
I looked into this a little more. Files on the ESP are not written on
every kernel image update. My current understanding is that they are
only written when grub-install is run.
So, yes, I think discard on ESP is not urgent at all, but still nice to
have.
--
You received this bug notification be
Error still present in 18.04 (German Apple wired USB keyboard)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/214786
Title:
Apple USB ISO keyboard has incorrectly swapped keys
To manage notification
It seems from prior comments, that while this system was still being
developed... well it was not clear yet precisely how apps might be using
this folder. What stuff they could be writing in there. So might have
been considered instead from the outset?
The suggestion was already discussed of cours
201 - 300 of 611 matches
Mail list logo
