(It’s in testing now, earlier than I assumed, due to the autopkgtests)
** Summary changed:
- Please sync rs 20200313-1 (universe) from Debian sid (main)
+ Please sync rs 20200313-1 (universe) from Debian testing (main)
--
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
A roll-up of a couple of bugfixes (this is almost identical to the
upcoming new upstream release), but, more importantly, introduction of
autopkgtests. I’d prefer these fixes to be in focal due to LTS, and
especially as mksh 58 will be very close to this code, have the chance
Public bug reported:
I’ve just fixed some bugs upstream in rs (mostly by rebasing on top of
OpenBSD’s latest) and modernised the Debian packaging (debhelper 12,
autopkgtests, etc). Those bugs were reported by a user on Ubuntu.
As DebianImportFreeze is active (as far as I can tell, anyway), here’s
** Changed in: ksh (Ubuntu)
Status: Triaged => 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/768591
Title:
ksh93: segmentation fault with printf
To manage notifications about th
@s: Yes, I have a model with nfc typ: 20KGS03900
@Kai-Heng Fen: I didn’t need the nosleep workaround (second patch). The
first patch from Aaron (https://lkml.org/lkml/diff/2019/2/20/700/1) was
sufficient. (The nosleep option has only been necessary for the kernels
provided by Aaron which were
I do not just claim that, I am just sharing what helped me... With older
kernels my touchpad hardly survived 5 suspends. With 5.3 it just works
(4 weeks without a dead touchpad with at least 50 suspends). Okay the
trackpoint issue is still there but i give a ...
Before that I had to build my own k
The touchpad problem seems to be solved (for me) using linux 5.3. The
trackpoint sometimes still dies but the touchpad keeps working. Luckily,
i don't care about the trackpoint...
I was using mainline 5.3 since 4 weeks on ubuntu 19.04 and i am now
using 19.10 (uses 5.3 by default) since a week and
Yeah, I saw the mail; much better. I fixed one of these in dietlibc the
other day…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850184
Title:
losetup -f broken in 2.0.6-1ubuntu2
To manage notific
How is this even a fix?
Also, does this affect other applications built against klibc?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850184
Title:
losetup -f broken in 2.0.6-1ubuntu2
To manage no
Fun: this works with 2.0.7-1 built with gcc-9 in Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850184
Title:
losetup -f broken in 2.0.6-1ubuntu2
To manage notifications about this bug go t
-- Forwarded message --
From: Adam Conrad
Message-ID:
<157106879908.15546.2658970073129703906.mal...@soybean.canonical.com>
2.0.7-1 fails to build in the same way on Ubuntu 19.10. I'm assuming
it's either glibc 2.30 (Debian is at 2.29) or linux 5.3 (Debian is at
5.2), with th
Probably fixed in 2.0.7 which fixed a parallel make issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843743
Title:
klibc ftbfs in eoan
To manage notifications about this bug go to:
https://bug
In my opinion this is serious bug. I created an AWS AMI using packer and
one of the installed packages (salt-minion) pulled in ifupdown. This
then broke network connectivity of instances started from the custom
AMI. I took me five hours to find out what the problem was.
--
You received this bug n
The same problem also happens in EC2-VPC mode if the network interface changes.
This happens if you create a custom AMI, e.g. using Packer, from the official
Ubuntu 18.04 LTS AMI. The first start by packer writes the MAC address into
/etc/netplan/50-cloud-init.yaml which gets part of the custom
but is there any update on this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
Carbon 6th
To manage noti
Public bug reported:
Hi,
after successfully logged out of tty2 it is not possible to change back
to tty2, tty3 etc.
to reproduce:
with sddm running and graphically logged out:
1) login tty2
2) logout tty2 -> sddm login screen is visible after tty2 logout
4) pressing [CTRL][ALT][F2]-[F8] not work
I’ve forwarded this upstream, please follow up with the developers at
https://github.com/performous/performous/issues/481 instead.
Closing on the Launchpad side, as this is not a packaging bug.
** Bug watch added: github.com/performous/performous/issues #481
https://github.com/performous/perfo
Please try running the following command:
env LIBGL_ALWAYS_SOFTWARE=true performous
This forces CPU rendering (disables GPU 3D rendering), by Mesa with
llvmpipe (on modern systems), which is still quite fast and supports
newer OpenGL versions than some old graphics cards.
Please indicate if this
** Changed in: performous (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/1668324
Title:
/usr/games/performous:6:__gnu_cxx::__verbose_terminate_handler:__cxxabi
Fixed by Debian sync
** Changed in: performous (Ubuntu)
Status: New => 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/500268
Title:
performous does not include content (songs, ..
Forwarded upstream as: https://musescore.org/en/node/291905
** Also affects: musescore
Importance: Undecided
Status: New
** Changed in: musescore
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi AaronaMa,
I‘ve seen that Dmitry Torokhov has some concerns about your patch and
would like to try another way of fixing it. I just wanted to let you
know that i am still here and able to test your patches :)
best regards
@alinuxuser: the issue is still present for me using the newest
bios/fir
Thanks, Sebastien. I reported the issue upstream since it's not specific
to Ubuntu (I could reproduce it on Arch Linux).
https://gitlab.gnome.org/GNOME/rhythmbox/issues/1711
** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #1711
https://gitlab.gnome.org/GNOME/rhythmbox/issues/1711
-list-view-sort-reversed: false
gio info -f /mnt/nfs/tfuehrerldap
Attribute:
filesystem::size: 3928343838720
filesystem::free: 1362925715456
filesystem::type: nfs
filesystem::used: 2565296488448
filesystem::remote: FALSE
cheers,
Thorsten
--
You received this bug notification because you
any news? Is the patch submission ignored? This bug is still present in
5.1.6 :/ I am using your patch since you published it and it is working
great, no issues at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
...because?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830551
Title:
rhythmbox loses daap connection everytime when dhcp lease expires
To manage notifications about this bug go to:
https://bugs
Public bug reported:
rhythmbox loses daap connection everytime the host (of rhythmbox) has to
renew his dhcp lease. The daap server has a static IP.
Here is the corresponding part of journalctl:
Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCP lease lost
Mai 26 22:06:05 myhostname
Public bug reported:
Hi all,
to make a long story short: There's a segfault in svnserve 1.9.3
distributed by UB 16.04 LTSm which is very likely available in 1.9.7
distributed with UB 18.04 LTS as well and has been fixed upstream by the
following patch in version 1.9.9:
https://svn.apache.org/vie
Fixed in 1:20190224-1 (in disco)
** Changed in: pax (Ubuntu)
Status: New => 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/1823638
Title:
pax ftbfs in cosmic
To manage notific
Hi, please make sure you have followed all the steps posted by AaronMa
(#94):
1. ensure that the i2c-i801 is loaded! Ubuntu currently blacklists this module
by default in /etc/modprobe.d/blacklist.conf - Thus, the patches won’t have any
effect.
2. ensure that your touchpad AND trackpoint firmwar
** Changed in: tilix (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818991
Title:
Drop pcre2-version-update.patch
To manage notifications about this bu
Ah sry, i missed the series file/thought it was still applied
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818991
Title:
Drop pcre2-version-update.patch
To manage notifications about this bug go
Public bug reported:
Should be easy, there are no Ubuntu changes, just the import of the
latest Debian version is missing.
As this fixes an only haphazardly patched security issue with a proper
fix including proper autoconf-like detection, this release is urgent.
** Affects: ubuntu
Importan
Public bug reported:
Should be easy, there are no Ubuntu changes, just the import of the
latest Debian version is missing.
This is mostly a rollup release replacing accumulated Debian patches
with a new upstream version collecting all fixes that have piled up in
the last year or so, thus of prior
@ALinuxUser: the patches are not yet upstream and thus one has to build
a patched kernel yourself. You can follow the upstream process in the
links posted from aaronma.
For some people it is working because they have a different touchpad.
But according to the above discussion even the patches prob
i am now using 5.0.x with your patches and it is working great!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
C
Public bug reported:
The pcre2-version-update.patch in disco should not be necessary anymore
and should be removed, since pcre2 has been accepted in main [0] and vte
has been build with pcre2 support [1]. Moreover, the pcre2 backport in
vte caused various confusion [2] and other issues [3].
[0] h
small update: i am using 4.20.11 with your patches on top since Friday
without any issue! I don't even need the nosleep option.
For others ensure that blacklist i2c_i801 is removed from
/etc/modprobe.d/blacklist.conf ...
--
You received this bug notification because you are a member of Ubuntu
Bu
Okay, thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
Carbon 6th
To manage notifications about thi
@Aaron Ma: Thanks for upstreaming! Have you also found time to look into
the crash-on-resume with your kernel, which I reported in #121. Is this
somehow related? I have not encountered a crash with 4.20.x from
mainline.
--
You received this bug notification because you are a member of Ubuntu
Bugs
@AaronMa: Would be really nice if you could post your patch here, so we
could build our own kernels until your patch lands upstream. This would
also allow users of other distros to provide feedback. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I also still have this issue with the default 18.04.1 version. However,
i installed a newer mesa version (which also upgrades a bunch of other
dependencies) using the padoka stable ppa and since then the issue is
gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Unfortunately, I have to report a strange resume: the screen remained black
after opening the lid. I pressed the powerbutton and after a few seconds and
flickering the screen came back.
The log shows a Kernel Call Trace but also a gnome-shell crash. Thus, I
appended my complete journalctl log. (
thanks for doing this! Could you please also add the debug kernel
parameter which AronaMa requested in #94: rmi_core.debug_flags=0x7 (it
is missing according to your log). Maybe thats also the reason why the
other two logs are empty.
--
You received this bug notification because you are a member
I think you should try it again, even if wireguard is not working. Just
for testing and creating a log of your issue, which would probably be
very helpful for AaronMa and thus for all of us if this damn bug is
finally resolved. Just try somehow to get "journalctl -b 0 -k >
journal.log" after a resu
hi, more feedback from me: i am now running this kernel since sa morning
without any issue with at least 20 suspend/resumes. Just in case, i
appended my journalctl log (but without the debug kernelparameter).
@ALinuxUser: do you see any output when typing journalctl -b 0 -k?
** Attachment added:
Hi, I have performed 11 suspend/resumes and no issue! Big thanks for
looking into it and fixing it!
nosleep mode sounds like a mitigation so that the bug cannot occur but
is not actually fixing it? Is the issue then in the firmware/bios and we
have to contact lenovo or is it still there in the ker
Hi, here is the journalctl log
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5230010/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I added the kernel parameter and did a suspend/resume and attached the
dmesg log. Btw I never noticed that the trackpoint didn’t survived
suspend/resume (which occasional also happens with 4.19.x)
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+at
I now have performed 5 suspend/resumes and the first 4 times the
touchpad did work 5-40s after the resume. However, after the 5th resume
the touchpad didn’t wake up again (waited 8min).
I also noticed that I can use the touchpad to perform clicks even if the
cursor is not moving (not by using the
Ugh, i think i was wrong, it is working. But directly after a resume the
touchpad is not working and can it can take quite an amount to work
(more than 30s)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Hi, the trackpoint worked well but the touchpad did not after the first
suspend/resume (I really did try to use it). However, I will test it
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791427
thanks for looking into this issue and trying to fix it. I've installed your
kernel, however, the issue is still there (at least for me). I've attach my
dmesg log. The first suspend/resume at ~122 causes that the touchpad is not
working anymore. There is also
"[ 122.097687] psmouse serio1: Fai
Hi, thanks for the reply. The touchpad stopped working and was
completely unresponsive and was reactivated by the subsequent
suspend/resume. (The trackpoint was working all the time) Is there an
advanced logging which i could activate?
--
You received this bug notification because you are a membe
oky i could reproduce it with psmouse.synaptics_intertouch=0. Here my
dmesg. As above the last suspend/resume restored the touchpad and the
last but one deactivated it.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5222385/+files/dmesg
-
oky, i now also experienced the issue a couple of times but it only
occurs in 1 out of 10 times and i resolved by an additional
suspend/resume.
In dmesg i see:
psmouse serio1: Failed to disable mouse on isa0060/serio1
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*more info: i am using ubuntu 18.04.1, 4.19.9 from mainline, libinput 1.12.1,
attached is my dmesg, the last but one suspend/resume deactivated the touchpad
and the last one restored it.
i had psmouse.synaptics_intertouch=1, i am now testing
psmouse.synaptics_intertouch=0
** Attachment added:
Putting the Launchpad bug into Cc.
-- Forwarded message --
Message-ID:
Date: Mon, 10 Dec 2018 18:23:56 +0100 (CET)
Subject: rng-tools: replaced with inferior version
Source: rng-tools
Version: 5-1
Severity: serious
Justification: breaks existing uses of this package
This is the
@scott moser thanks a lot for the snap! This tool is really missing in
the normal repository :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764450
Title:
pdftk missing in 18.04 (bionic) and later
Hi, I also have the :00:1f.4 and the nfc model (20KG-S03900) and I
don’t have this issue. Even my trackpoint now survives resumes/suspends
since using 4.19.1 and upgrading all firmware (using windows)
(touchpad/trackpoint/bios/thunderbolt).
I can just repeat the steps, which where necessary fo
It's also a workaround
# date
Thu Nov 22 19:06:07 CET 2018
# stat /etc/modules
File: '/etc/modules'
Size: 200 Blocks: 8 IO Block: 4096 regular file
Device: fd00h/64768dInode: 272949 Links: 1
Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/ro
# lsmod | grep ip_
ip_vs_wlc 16384 3
ip_vs 151552 5 ip_vs_wlc
nf_conntrack 131072 1 ip_vs
libcrc32c 16384 3 nf_conntrack,xfs,ip_vs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
My work-a-round is that I'm knewing this problem and so I load it manually.
Bionic is working, I wrote it 2018-10-26.
We still use Debian 6-9 and Ubuntu 12-18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
global_defs {
notification_email {
r...@domain.tld
}
notification_email_from r...@hosteurope.de
smtp_server 127.0.0.1
smtp_connect_timeout 15
router_id lb2.domain.tld
}
vrrp_instance VRRP_SERVICE {
virtual_router_id 24
interface uplink0
state
@pqa It's not running in a container we want stable software
--
@kstenerud
# dmsg
...
[Fri Nov 16 10:45:58 2018] nf_conntrack version 0.5.0 (65536 buckets, 262144
max)
[Fri Nov 16 10:45:58 2018] IPVS: Registered protocols (TCP,
OK, then it’s not a bug. Please use a proper Unix filesystem.
I even looked at the part of the source code in question and verified
it’s correct, so the problem comes from your NTFS.
** Changed in: cvs (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because y
Please verify whether this also occurs on an ext4 or so filesystem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802162
Title:
"Operation not permitted" error when update
To manage notifications
Is this on a FAT or other MS-DOS world filesystem?
If so, failure to operate correctly is expected.
** Changed in: cvs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Hi Martijn,
this has not been fixed in Debian, it affects openjdk-8 and openjdk-10
there.
As far as has been analysed to date, this is caused by a new, stricter,
JAR check that went from OpenJDK to Debian/*buntu’s Java 10 and 8 (but
not Debian’s Java 11), missing that the new check should be disab
The testcase needs the “package test;” in the first line removed /
commented-out, then it works.
This works in 11.0.1+13-2 on Debian sid, as a new data point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
dvhart: can you please attach that file (and related resources) so I can
try to reproduce?
In a similar vain, I just uploaded mgp 1.13a+upstream20090219-9 and
would like for you to see whether this still occurs for you.
** Changed in: mgp (Ubuntu)
Status: New => Incomplete
--
You receive
MagicPoint no longer uses dlopen() and was rebuilt from source, so the
original bug is gone.
You’re pointing out a couple of things in the comments which may or may
not have been separate bugs, but with the recent upload of
1.13a+upstream20090219-9 ought to be gone as well, for the actual
software
Bionic is working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800159
Title:
keepalived ip_vs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+b
Public bug reported:
1)
Description:Ubuntu 16.04.5 LTS
Release:16.04
2) keepalived:
Installed: 1:1.2.24-1ubuntu0.16.04.1
Candidate: 1:1.2.24-1ubuntu0.16.04.1
Version table:
*** 1:1.2.24-1ubuntu0.16.04.1 500
500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com
xenial-
Hi, i did a complete new installation with the ubuntu 18.04.1 iso and
the touchpad was always working after suspend/resume only the
trackpoints gets lost. Does it make a difference if s3 is available
during installation?
The only modification i had to do was to remove the blacklist of i2c_i801 in
you probably have to apply the ubuntu tilix "pcre2-version-update" patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666264
Title:
FFe: Update gnome-terminal to 3.24 and vte to 0.48
To manage no
a small update: the tlp settings have no effect and are thus not
necessary... Even with the settings the trackpoint is sometimes not
working after resume. However, an additional suspend/resume does
activate the trackpoint again!
So removing the blacklist of i2c_i801 (which is a critical bug: #1786
Hi, for me the following combination for ubuntu 18.04 using x1c6 with
nfc (20KG) seems to be working:
- touchpad and trackpoint both enabled in bios
- nfc disabled in bios (because i dont need it, dont know if it would work)
- linux (s3) sleep in bios
- upgrading to the newest kernel, i am using 4
This was my first idea too. I did the following:
Download Ubuntu 18.04 - error as described.
So I found this bug:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1771059
and downloaded the daily ISO with the same error.
Then i found Ubuntu 18.04.01 with the same error.
So I verified th
I'm not sure if nightlight breaks after dim or after it turns off
completely. (since it cannot dim any more after having lowest possible
backlight already)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
For me nightlight is working perfectly after each reboot - but as soon as the
display is turned off nightlight is off when the screen is powered on again.
As a workaround I turn the setting off and on again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
tilix seems to be warning-free with unpatched vte. Someone has posted
these warnings upstream: https://github.com/gnunn1/tilix/issues/1428 and
the response was "Please open a bug with Ubuntu, since they patch vte to
remove pcre2 regular expressions this issue is likely caused by that." a
** Bug wa
thanks a lot for the clarification, this is really helping me to
understand that! I am just a noob who wants to learn something and wants
to find the cause of a problem which annoys me. Thus, i invested some
time to dig into the problem :)
So the cause is that the MULTILINE flag is just that not s
i should be more precise with the file name... the specific line is in
src/vtegtk.cc line 1906
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666264
Title:
FFe: Update gnome-terminal to 3.24 and vte
Hi everyone,
I don't know which is the right place to post this, but the discussion
here seems to be the most appropriate for bringing this up.
I looked more into the tilix warnings. After all, the warnings seem to be
caused by the vte lib and especially in the reverted parts.
Therefore, I downl
works perfect!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about this bug
ari, i already have created a bug report for the tilix log messages:
https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1785885
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666264
Title:
FFe: Up
Public bug reported:
I downloaded Ubuntu 18.04.1
Created a bootable USB Stick with Rufus (MBR UEFI or BIOS?)
Booted - Try ubuntu -
after boot: Install ubuntu
Then the installer stops with error number 5 ... error copying files ... faulty
CD/DVD ...
Unfortunately I do not know how to further deb
Public bug reported:
Hi, tilix causes warnings in the syslog (ubuntu 18.04):
Aug 07 21:04:44 x1 tilix[5865]: (../../src/vtegtk.cc:1906):int
vte_terminal_match_add_gregex(VteTerminal*, GRegex*, GRegexMatchFlags):
runtime check failed: (g_regex_get_compile_flags(gregex) &
G_REGEX_MULTILINE)
Someon
** Attachment added: "screencast"
https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1783011/+attachment/5170090/+files/lp.gif
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783011
Title:
Works for me (and this is not a user support channel, but a package
bugreport one).
Basically, you have to select the entire note, not just the noteheads
(round things). Shift-click is the devise. I’m attaching a screencast of
how it works.
** Changed in: musescore (Ubuntu)
Status: New =>
oky i will create a new bug report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532508
Title:
Screen contents revealed briefly on resume, before even unlocking
To manage notifications about this
still not possible in ubuntu 18.04 with calendar 3.28.2. I also tried a
posteo calendar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731628
Title:
Cannot add caldav calendar
To manage notificati
this bug still occurs for me on ubuntu 18.04 using gdm 3.28.2 and gnome-
shell 3.28.2. However, my laptop (x1 carbon gen6) only supports S0i3
(activated with the kernel parameter "acpi.ec_no_wakeup=1") and not s3.
So is it possible that this bug is only fixed for S3? It does not occur
when using wa
** Summary changed:
- pax is not POSIX compliant
+ pax is not compliant with the latest version of POSIX yet
** Changed in: pax (Ubuntu)
Status: New => Confirmed
** Changed in: pax (Ubuntu)
Assignee: (unassigned) => Thorsten Glaser (mirabilos)
--
You received this bug notifi
** Changed in: kwalletcli (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to Kubuntu PPA.
https://bugs.launchpad.net/bugs/1283014
Title:
KMail + GPG-Agent with pinentry-kwallet vanishes in backgro
User configuration issue in tomcat
** Changed in: guacamole-client (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/1703528
Title:
package guacamole-tomcat (not
Feel free to provide some test data…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679356
Title:
Missing dep8 tests
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
Hi Christopher,
On Fri, 22 Jun 2018, Christopher Hogan wrote:
> Please let me know if there's anything I can do to facilitate this
> process. Thanks.
the latest version of libctl is already uploaded to experimental.
Thorsten
--
You received this bug notification because you a
@Trent Nelson: thanks for the patch! I applied it and it's working
flawlessly!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work
101 - 200 of 1677 matches
Mail list logo
