[Touch-packages] [Bug 1944107] Re: No archive files for static compilation are included in the -dev package
this broke flutter classic snap, and I had to revert the change ** Changed in: libdrm (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1944107 Title: No archive files for static compilation are included in the -dev package Status in libdrm package in Ubuntu: Triaged Bug description: There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not possible to compile statically against this library. See attached debdiff to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1944107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945982] Re: Display zoom 125%
What application are you talking about? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1945982 Title: Display zoom 125% Status in Ubuntu: Incomplete Bug description: The zoom of my notebook monitor is set to 125%. After pressing F11 to enter the full screen state most of the time, when sliding up / down quickly, two same windows will appear, one smaller window is in the upper left corner, and the zoom ratio of the other window becomes larger (exceeding the screen size). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 19:55:29 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.11.0-36-generic, x86_64: installed acpi-call, 1.1.0, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc Renoir [152d:1268] InstallationDate: Installed on 2021-09-09 (24 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: HUAWEI BOHL-WXX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=d99779ec-6120-48ce-9e05-7cc9ec47539e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2020 dmi.bios.release: 1.5 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BOHL-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1120 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1120 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnHUAWEI:bvr1.05:bd07/20/2020:br1.5:efr1.5:svnHUAWEI:pnBOHL-WXX9:pvrM1120:skuC233:rvnHUAWEI:rnBOHL-WXX9-PCB:rvrM1120:cvnHUAWEI:ct10:cvrM1120: dmi.product.family: MateBook D dmi.product.name: BOHL-WXX9 dmi.product.sku: C233 dmi.product.version: M1120 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1945982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?
As can be seen here, the package doesn't pass its own tests even when
triggered against only itself:
https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/amd64/libs/libsoup2.4/20211004_230503_77208@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1945713
Title:
Flaky test brotli/basic on focal amd64?
Status in libsoup2.4 package in Ubuntu:
New
Bug description:
The brotli/basic test case periodically fails. It appears that a few
retriggers can result in a pass:
https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64
The failures look like this in autopkgtest logs:
ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
"***\n")
I've replaced most of the text with '***' to highlight the difference
is a 'U' character appended.
The test case is essentially doing a decompression of 'brotli-
data/compressed.br' and comparing that it matches 'brotli-
data/uncompressed.txt'. I've done this manually using the brotli cli,
and the files do indeed have the same content. I've also built the
package and run the test case locally in a focal lxc container on
amd64:
$ cd
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
$ while : ; do ./brotli-decompressor-test | grep 'brotli/basic'; sleep
0.1; done
I left that to run several hundred cycles but no failures reported at
all.
There are a bunch of instances of this failure, here's a few for
reference:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz
That last link is the earliest instance I've been able to find.
You'll notice in the second two links they also have a failure "not ok
2 /ssl/tls-interaction", but the first link shows only the brotli
failure.
Interestingly, I've not found instances of this failure against other
architectures than amd64, nor have I seen it on releases other than
focal. No dice from googling for bug reports or other reports of test
failures with libsoup2.4 + brotli.
The test's code is doing this, basically:
SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
do {
result = g_converter_convert (G_CONVERTER (dec), in_buf,
length, out_buf, sizeof out_buf, 0,
&bytes_read, &bytes_written,
&error);
g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
length -= bytes_read;
} while (result == G_CONVERTER_CONVERTED);
soup_brotli_decompressor's code is here:
https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
decoder/soup-brotli-decompressor.c
But I'm not spotting anything that would obviously cause a 'U' to be
randomly appended sometimes. And why 'U'? UINT? Unknown? User error?
There are some interesting bug reports in GNOME about brotli in
libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
match this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901966] Re: Unable to stop at breakpoint in 32-bit executable
I have same issue as James described. A static link of execution file,
"-static" option in gcc, works in gdb while shared is not.
Any updates on this issue?
bulssi@bulssi:~/work$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"
bulssi@bulssi:~/work$ lscpu
Architecture:aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0,1
Off-line CPU(s) list:2,3
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
Vendor ID: ARM
Model: 0
Model name: Cortex-A55
Stepping:r2p0
BogoMIPS:100.00
L2 cache:256 KiB
L3 cache:512 KiB
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Spec store bypass: Not affected
Vulnerability Spectre v1:Mitigation; __user pointer sanitization
Vulnerability Spectre v2:Not affected
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32
atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
bulssi@bulssi:~/work$ uname -a
Linux bulssi 5.4.96+ #4 SMP PREEMPT Tue Sep 28 02:25:02 UTC 2021 aarch64
aarch64 aarch64 GNU/Linux
bulssi@bulssi:~/work$ cat test.c
#include
int main (int argc, char **argv)
{
printf ("hello\n");
return 0;
}
bulssi@bulssi:~/work$ arm-linux-gnueabihf-gcc -o a32.out test.c
bulssi@bulssi:~/work$ ./a32.out
hello
bulssi@bulssi:~/work$ gdb ./a32.out
GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
...
Reading symbols from ./a32.out...
(No debugging symbols found in ./a32.out)
(gdb) set architecture arm
The target architecture is assumed to be arm
(gdb) r
Starting program: /home/bulssi/work/a32.out
^C
Program received signal SIGINT, Interrupt.
0xf7fd12c4 in ?? () from /lib/ld-linux-armhf.so.3
(gdb) bt
#0 0xf7fd12c4 in ?? () from /lib/ld-linux-armhf.so.3
#1 0xf7fc81e4 in ?? () from /lib/ld-linux-armhf.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
(gdb) set debug infrun 1
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/bulssi/work/a32.out
infrun: infrun_async(1)
infrun: proceed (addr=0xf7fc5a80, signal=GDB_SIGNAL_0)
infrun: proceed: resuming process 19335
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[process 19335] at 0xf7fc5a80
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun: -1.0.0 [process -1],
infrun: status->kind = ignore
infrun: handle_inferior_event status->kind = ignore
infrun: prepare_to_wait
^Cinfrun: target_wait (-1.0.0, status) =
infrun: 19335.19335.0 [process 19335],
infrun: status->kind = stopped, signal = GDB_SIGNAL_INT
infrun: handle_inferior_event status->kind = stopped, signal = GDB_SIGNAL_INT
infrun: stop_pc = 0xf7fd12fe
infrun: random signal (GDB_SIGNAL_INT)
infrun: stop_waiting
infrun: stop_all_threads
infrun: stop_all_threads, pass=0, iterations=0
infrun: process 19335 not executing
infrun: stop_all_threads, pass=1, iterations=1
infrun: process 19335 not executing
infrun: stop_all_threads done
Program received signal SIGINT, Interrupt.
0xf7fd12fe in ?? () from /lib/ld-linux-armhf.so.3
infrun: infrun_async(0)
(gdb) bt
#0 0xf7fd12fe in ?? () from /lib/ld-linux-armhf.so.3
#1 0xf7fc81e4 in ?? () from /lib/ld-linux-armhf.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) quit
bulssi@bulssi:~/work$ arm-linux-gnueabihf-gcc -static -o a32.out test.c
bulssi@bulssi:~/work$ file a32.out
a32.out: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux),
statically linked, BuildID[sha1]=e1f35070879490a0c809ac5b4b32159457ae0150, for
GNU/Linux 3.2.0, not stripped
bulssi@bulssi:~/work$ gdb a32.out
GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
...
Reading symbols from a32.out...
(No debugging symbols found in a32.out)
(gdb) r
Starting program: /home/bulssi/work/a32.out
hello
[Inferior 1 (process 19358) exited normally]
(gdb) quit
bulssi@bulssi:~/work$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1901966
Title:
Unable to stop at breakpoint in 32-bit executable
Status in gdb package in Ubuntu:
Confirmed
Bug description:
I believe I'm having the problem described in #1846557 and #1848200.
Those bugs were reported fixed in 8
[Touch-packages] [Bug 1901966] Re: Unable to stop at breakpoint in 32-bit executable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1901966 Title: Unable to stop at breakpoint in 32-bit executable Status in gdb package in Ubuntu: Confirmed Bug description: I believe I'm having the problem described in #1846557 and #1848200. Those bugs were reported fixed in 8.1.1 but I'm observing them in 9.2 so I suspect a regression (in fact, if I read the notes correctly, the earlier reports were from another regression!). I create a new EC2 server on AWS with Ubuntu Server 20.04 LTS (64-bit Arm) then perform the following installs (not sure what is needed or if something is missing): ``` sudo dpkg --add-architecture armhf sudo apt update sudo apt upgrade -y sudo apt install -y build-essential vim binutils-arm-linux-gnueabi \ gdb libc6:armhf libstdc++6:armhf ``` Then I create hello.s: ``` .text .global _start _start: MOV R7, #4 MOV R0, #1 LDR R1, =hello LDR R2, =hello_size SWI 0 MOV R7, #1 SWI 0 .data hello: .asciz "Hello world!\n" .equhello_size, (.-hello) ``` Then I assemble, link, and run, all with success. Finally, I try to debug: ``` $ arm-linux-gnueabi-as -ggdb -mcpu=cortex-a57 -o out.o hello.s $ arm-linux-gnueabi-ld out.o -dynamic-linker=/usr/lib/ld-linux-armhf.so.3 -o out $ rm out.o $ ./out Hello world! $ gdb out GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2 ... Reading symbols from out... (gdb) b _start Breakpoint 1 at 0x10074: file hello.s, line 4. (gdb) run Starting program: /home/ubuntu/280/out ``` At this point everything hangs until I press ^C: ``` ^C Program received signal SIGINT, Interrupt. 0xba072284 in ?? () (gdb) bt #0 0xba072284 in ?? () #1 0x7232 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) l 1 .text 2 .global _start 3 _start: 4 MOV R7, #4 5 MOV R0, #1 6 LDR R1, =hello 7 LDR R2, =hello_size 8 SWI 0 9 MOV R7, #1 10SWI 0 (gdb) q A debugging session is active. Inferior 1 [process 29234] will be killed. Quit anyway? (y or n) y $ ``` It appears that gdb generally works and recognizes the executable, but breakpoints don't work. I'm new at Arm and don't have a lot of experience with assembly (at least not since the early 1970s), so it could easily be my problem but it seems suspiciously like an earlier problem and I think what I've done should work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1901966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945527] Please test proposed package
Hello Brian, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2021a-2ubuntu0.20.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: tzdata (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Hirsute:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945527] Please test proposed package
Hello Brian, or anyone else affected,
Accepted tzdata into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2021a-2ubuntu0.18.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Hirsute:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945527] Re: Update tzdata to version 2021a-2
Hello Brian, or anyone else affected,
Accepted tzdata into hirsute-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2021a-2ubuntu0.21.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: tzdata (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-hirsute
** Changed in: tzdata (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Hirsute:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945894] Re: Translated strings not imported from damned lies
@Ask: If you want to talk more about the translation related workflow, please feel free to post to the ubuntu-translators mailing list. https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators ** Changed in: ubuntu-translations Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945894 Title: Translated strings not imported from damned lies Status in Ubuntu Translations: Invalid Status in gtk+3.0 package in Ubuntu: Invalid Bug description: The newly translated strings in GTK does not seem to be imported from Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but is fully translated in Damned Lies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1945894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945817] Re: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic
Hi carnage-mode, Thanks for your report. We could make it install fonts-noto-core by default when you install the Amharic language. That package provides both "Noto Serif Ethiopic" and "Noto Sans Ethiopic". As a test, can you please run these commands: sudo apt purge fonts-sil-abyssinica sudo apt install fonts-noto-core and let us know if the result is an improved rendering of Amharic. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: language-selector (Ubuntu) Status: New => In Progress ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ubuntu-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1945817 Title: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic Status in language-selector package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Bug description: Description of problem: Abyssinica SIL is an old font. It's barely legible and breaks in most apps. Noto Serif Ethiopic, on the other hand, is a modern and well designed font. Noto Serif Ethiopic is distributed with the Open Font License, so packaging it won't be a problem. Link https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amharic¬o.script=Ethi Version: 20.04.3 How reproducible: always Steps to Reproduce: 1. Pretty much using the the Amharic language anywhere on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1945817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945527] Re: Update tzdata to version 2021a-2
tzdata (2021a-2ubuntu1) impish; urgency=medium
* Merge from Debian unstable. Remaining changes:
- Ship ICU timezone data files which are utilized by php and update them
to 2021a1.
tzdata (2021a-2) unstable; urgency=critical
* Set urgency to critical as the Samoa DST change is already effective.
* Update Provides to tzdata-bookworm.
* debian/control: remove Adam Conrad from Uploaders. RIP. Closes: #986954.
* Cherry-pick patches from tadata-2021b until the upstream situation gets
less confused:
- 01-no-leap-second-2021-12-31.patch: No leap second on 2021-12-31 as per
IERS Bulletin C 62.
- 02-samoa-dst.patch: Samoa no longer observes DST.
- 03-jordan-dst.patch: Jordan now starts DST on February's last Thursday.
-- Brian Murray Wed, 29 Sep 2021 12:14:22 -0700
** Changed in: tzdata (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
In Progress
Status in tzdata source package in Focal:
In Progress
Status in tzdata source package in Hirsute:
In Progress
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
Performing the verification for Hirsute. First, install the problematic package and reproduce the error: # apt policy gssproxy gssproxy: Installed: 0.8.2-2 Candidate: 0.8.2-2 Version table: *** 0.8.2-2 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 100 /var/lib/dpkg/status # /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock [2021/10/04 18:34:27]: Debug Enabled (level: 3) [2021/10/04 18:34:27]: Keytab /etc/krb5.keytab has no content (-1765328203) [2021/10/04 18:34:27]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18 [2021/10/04 18:34:27]: Client [2021/10/04 18:34:27]: (/usr/sbin/gssproxy) [2021/10/04 18:34:27]: connected (fd = 12)[2021/10/04 18:34:27]: (pid = 1676) (uid = 0) (gid = 0)Segmentation fault (core dumped) Now, install the version from -proposed and verify that it works correctly: # apt install gssproxy Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: gssproxy 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 88.0 kB of archives. After this operation, 13.3 kB disk space will be freed. Get:1 http://archive.ubuntu.com/ubuntu hirsute-proposed/universe amd64 gssproxy amd64 0.8.2-2ubuntu0.21.04.1 [88.0 kB] Fetched 88.0 kB in 0s (236 kB/s) (Reading database ... 15225 files and directories currently installed.) Preparing to unpack .../gssproxy_0.8.2-2ubuntu0.21.04.1_amd64.deb ... Unpacking gssproxy (0.8.2-2ubuntu0.21.04.1) over (0.8.2-2) ... Setting up gssproxy (0.8.2-2ubuntu0.21.04.1) ... # apt policy gssproxy gssproxy: Installed: 0.8.2-2ubuntu0.21.04.1 Candidate: 0.8.2-2ubuntu0.21.04.1 Version table: *** 0.8.2-2ubuntu0.21.04.1 500 500 http://archive.ubuntu.com/ubuntu hirsute-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.8.2-2 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages # /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock [2021/10/04 18:35:20]: Debug Enabled (level: 3) [2021/10/04 18:35:20]: Keytab /etc/krb5.keytab has no content (-1765328203) [2021/10/04 18:35:20]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18 [2021/10/04 18:35:20]: Client [2021/10/04 18:35:20]: (/usr/sbin/gssproxy) [2021/10/04 18:35:20]: connected (fd = 12)[2021/10/04 18:35:20]: (pid = 2029) (uid = 0) (gid = 0)[2021/10/04 18:35:20]: ^C[2021/10/04 18:35:24]: Exiting after receiving a signal Therefore, the new package indeed fixes the problem. ** Tags removed: verification-needed verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute ** Tags removed: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd Status in gssproxy package in Ubuntu: In Progress Status in libselinux package in Ubuntu: Invalid Status in gssproxy source package in Focal: Fix Committed Status in libselinux source package in Focal: Invalid Status in gssproxy source package in Hirsute: Fix Committed Status in libselinux source package in Hirsute: Invalid Bug description: [ Impact ] gssproxy users on Focal and Hiruste who configure the package to handle NFS mountpoints using Kerberos authentication will experience a segmentation fault when invoking the service either through systemd or by hand. [ Test Case] Inside a Focal LXD container: $ lxc launch images:ubuntu/focal gssproxy-bug1788459-focal $ lxc shell gssproxy-bug1788459-focal # apt update # apt install -y gssproxy nfs-kernel-server # cat > /etc/gssproxy/gssproxy.conf << __EOF__ [gssproxy] debug = true debug_level = 3 __EOF__ # cat >> /etc/gssproxy/25-nfs-server.conf << __EOF__ [service/nfs-server] mechs = krb5 socket = /run/gssproxy.sock cred_store = keytab:/etc/krb5.keytab trusted = yes kernel_nfsd = yes euid = 0 __EOF__ # /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock [2021/06/30 14:34:14]: Debug Enabled (level: 3) [2021/06/30 14:34:14]: Keytab /etc/krb5.keytab has no content (-1765328203) [2021/06/30 14:34:14]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18 [2021/06/30 14:34:14]: Client [2021/06/30 14:34:14]: (/usr/sbin/gssproxy) [2021/06/30 14:34:14]: connected (fd = 12)[2021/06/30 14:34:14]: (pid = 3428) (uid = 0) (gid = 0)Segmentation fau lt (core dumped) [ Where problems could occur ] * The backported patch is simple and it is very unlikely that it will introduce a regression. * As usual, it is always risky to rebuild a package that hasn't been touched for more than 1 year, albeit in this case the risk is very low because the
[Touch-packages] [Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
Performing the verification for Focal. First, install the problematic package and reproduce the error: # apt policy gssproxy gssproxy: Installed: 0.8.2-2 Candidate: 0.8.2-2 Version table: *** 0.8.2-2 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status # /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock [2021/10/04 18:30:15]: Debug Enabled (level: 3) [2021/10/04 18:30:15]: Keytab /etc/krb5.keytab has no content (-1765328203) [2021/10/04 18:30:15]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18 [2021/10/04 18:30:15]: Client [2021/10/04 18:30:15]: (/usr/sbin/gssproxy) [2021/10/04 18:30:15]: connected (fd = 12)[2021/10/04 18:30:15]: (pid = 1877) (uid = 0) (gid = 0)Segmentation fault (core dumped) Now, install the version from -proposed and verify that it works correctly: # apt install gssproxy Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: gssproxy 1 upgraded, 0 newly installed, 0 to remove and 13 not upgraded. Need to get 88.4 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 gssproxy amd64 0.8.2-2ubuntu0.20.04.1 [88.4 kB] Fetched 88.4 kB in 0s (224 kB/s) (Reading database ... 15068 files and directories currently installed.) Preparing to unpack .../gssproxy_0.8.2-2ubuntu0.20.04.1_amd64.deb ... Unpacking gssproxy (0.8.2-2ubuntu0.20.04.1) over (0.8.2-2) ... Setting up gssproxy (0.8.2-2ubuntu0.20.04.1) ... # apt policy gssproxy gssproxy: Installed: 0.8.2-2ubuntu0.20.04.1 Candidate: 0.8.2-2ubuntu0.20.04.1 Version table: *** 0.8.2-2ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.8.2-2 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages # /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock [2021/10/04 18:31:59]: Debug Enabled (level: 3) [2021/10/04 18:31:59]: Keytab /etc/krb5.keytab has no content (-1765328203) [2021/10/04 18:31:59]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18 [2021/10/04 18:31:59]: Client [2021/10/04 18:31:59]: (/usr/sbin/gssproxy) [2021/10/04 18:31:59]: connected (fd = 12)[2021/10/04 18:31:59]: (pid = 2244) (uid = 0) (gid = 0)[2021/10/04 18:31:59]: ^C[2021/10/04 18:32:10]: Exiting after receiving a signal Therefore, the new package indeed fixes the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd Status in gssproxy package in Ubuntu: In Progress Status in libselinux package in Ubuntu: Invalid Status in gssproxy source package in Focal: Fix Committed Status in libselinux source package in Focal: Invalid Status in gssproxy source package in Hirsute: Fix Committed Status in libselinux source package in Hirsute: Invalid Bug description: [ Impact ] gssproxy users on Focal and Hiruste who configure the package to handle NFS mountpoints using Kerberos authentication will experience a segmentation fault when invoking the service either through systemd or by hand. [ Test Case] Inside a Focal LXD container: $ lxc launch images:ubuntu/focal gssproxy-bug1788459-focal $ lxc shell gssproxy-bug1788459-focal # apt update # apt install -y gssproxy nfs-kernel-server # cat > /etc/gssproxy/gssproxy.conf << __EOF__ [gssproxy] debug = true debug_level = 3 __EOF__ # cat >> /etc/gssproxy/25-nfs-server.conf << __EOF__ [service/nfs-server] mechs = krb5 socket = /run/gssproxy.sock cred_store = keytab:/etc/krb5.keytab trusted = yes kernel_nfsd = yes euid = 0 __EOF__ # /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock [2021/06/30 14:34:14]: Debug Enabled (level: 3) [2021/06/30 14:34:14]: Keytab /etc/krb5.keytab has no content (-1765328203) [2021/06/30 14:34:14]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18 [2021/06/30 14:34:14]: Client [2021/06/30 14:34:14]: (/usr/sbin/gssproxy) [2021/06/30 14:34:14]: connected (fd = 12)[2021/06/30 14:34:14]: (pid = 3428) (uid = 0) (gid = 0)Segmentation fau lt (core dumped) [ Where problems could occur ] * The backported patch is simple and it is very unlikely that it will introduce a regression. * As usual, it is always risky to rebuild a package that hasn't been touched for more than 1 year, albeit in this case the risk is very low because the package is not very complex. [ Original Description ] I have apache configured to perform a kerberized NFS4 mount using rpc.gssd and gssproxy. If I request a web page that requires NF
[Touch-packages] [Bug 1946016] [NEW] Unable to print via usb (HP Deskjet 6980)
Public bug reported: I'm unable to print documents via usb connection (HP Deskjet 6980). There is no connection problem, (lsusb: Bus 001 Device 040: ID 03f0:8804 HP, Inc DeskJet 6980 series correctly detected), it just doesn't work... ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 18:42:29 2021 InstallationDate: Installed on 2019-06-03 (853 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Deskjet-6980-series: usb://HP/Deskjet%206980%20series?serial=MY796BS11G04Q7 device for HP-Color-LaserJet-CM4540-MFP: socket://158.227.246.36:9100 MachineType: LG Electronics 13Z990-G.AA52B Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-CM4540-MFP.ppd', '/etc/cups/ppd/Deskjet-6980-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-CM4540-MFP.ppd: Permission denied grep: /etc/cups/ppd/Deskjet-6980-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=30e4f9a7-3fb6-4a39-a72e-b1a51a899771 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: W1ZD1180 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 13Z990 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrW1ZD1180X64:bd01/29/2019:br0.1:svnLGElectronics:pn13Z990-G.AA52B:pvr0.1:sku:rvnLGElectronics:rn13Z990:rvrFAB1:cvnLGElectronics:ct10:cvr0.1: dmi.product.family: Z Series dmi.product.name: 13Z990-G.AA52B dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1946016 Title: Unable to print via usb (HP Deskjet 6980) Status in cups package in Ubuntu: New Bug description: I'm unable to print documents via usb connection (HP Deskjet 6980). There is no connection problem, (lsusb: Bus 001 Device 040: ID 03f0:8804 HP, Inc DeskJet 6980 series correctly detected), it just doesn't work... ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 18:42:29 2021 InstallationDate: Installed on 2019-06-03 (853 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Deskjet-6980-series: usb://HP/Deskjet%206980%20series?serial=MY796BS11G04Q7 device for HP-Color-LaserJet-CM4540-MFP: socket://158.227.246.36:9100 MachineType: LG Electronics 13Z990-G.AA52B Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-CM4540-MFP.ppd', '/etc/cups/ppd/Deskjet-6980-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-CM4540-MFP.ppd: Permission denied grep: /etc/cups/ppd/Deskjet-6980-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=30e4f9a7-3fb6-4a39-a72e-b1a51a899771 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: W1ZD1180 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 13Z990 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrW1ZD1180X64:bd01/29/2019:br0.1:svnLGElectronics:pn13Z990-G.AA52B:pvr0.1:sku:rvnLGElectronics:rn13Z990:rvrFAB1:cvnLGElectronics:ct10:cvr0.1: dmi.product.family: Z Series dmi.product.name: 13Z990-G.AA52B dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1946016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : h
[Touch-packages] [Bug 1946017] [NEW] no IPV6 from wlan0 via dhcp
Public bug reported: neither during boot nor during a manual sudo dhclient -6 -v wlan0 the box does get a IPv6 on WLAN0. ipv4 works perfectly verbose output: Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ no link-local IPv6 address for wlan0 If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: isc-dhcp-client 4.4.1-2.2ubuntu6.2 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Oct 4 16:31:14 2021 ImageMediaBuild: 20201022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: Upgraded to hirsute on 2021-07-17 (78 days ago) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image hirsute raspi-image uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1946017 Title: no IPV6 from wlan0 via dhcp Status in isc-dhcp package in Ubuntu: New Bug description: neither during boot nor during a manual sudo dhclient -6 -v wlan0 the box does get a IPv6 on WLAN0. ipv4 works perfectly verbose output: Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ no link-local IPv6 address for wlan0 If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: isc-dhcp-client 4.4.1-2.2ubuntu6.2 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Oct 4 16:31:14 2021 ImageMediaBuild: 20201022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: Upgraded to hirsute on 2021-07-17 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1946017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945787] Re: heimdal: fails to build, symbols don't match
** Merge proposal linked: https://code.launchpad.net/~paride/ubuntu/+source/heimdal/+git/heimdal/+merge/409587 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1945787 Title: heimdal: fails to build, symbols don't match Status in heimdal package in Ubuntu: New Bug description: heimdal 7.7.0+dfsg-2ubuntu1 fails to build with dpkg-gensymbols: warning: debian/libroken18-heimdal/DEBIAN/symbols doesn't match completely debian/libroken18-heimdal.symbols --- debian/libroken18-heimdal.symbols (libroken18-heimdal_7.7.0+dfsg-2ubuntu1_riscv64) +++ dpkg-gensymbolsYtlvSr 2021-10-01 12:31:59.102451503 + @@ -42,7 +42,7 @@ rk_cloexec_dir@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_file@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_socket@HEIMDAL_ROKEN_1.0 1.6~git20131117 - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 +#MISSING: 7.7.0+dfsg-2ubuntu1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_copyhostent@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_free_data@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_lookup@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1945787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945894] Re: Translated strings not imported from damned lies
Those are indeed missing from the da.po provided in the 3.24.30 upstream tarball. Note that any Danish translator could upload an update translation to launchpad meanwhile if you don't want to wait for the next version. There is no bug in the package or system there so closing ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945894 Title: Translated strings not imported from damned lies Status in Ubuntu Translations: Incomplete Status in gtk+3.0 package in Ubuntu: Invalid Bug description: The newly translated strings in GTK does not seem to be imported from Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but is fully translated in Damned Lies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1945894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945645] Re: cups-pdf prints blank pages
Two confirmations that the problem is solved, so I close this bug as fixed. Thanks for the bug report and the confirmations that it is fixed. ** Changed in: cups-pdf (Ubuntu) Status: Confirmed => Fix Released ** Changed in: cups (Ubuntu) Status: Confirmed => Invalid ** Changed in: ghostscript (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Invalid Status in cups-pdf package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Invalid Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945787] Re: heimdal: fails to build, symbols don't match
Thanks for this bug report; I can reproduce the issue and will prepare an upload with your debdiff. ** Changed in: heimdal (Ubuntu) Assignee: (unassigned) => Paride Legovini (paride) ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1945787 Title: heimdal: fails to build, symbols don't match Status in heimdal package in Ubuntu: New Bug description: heimdal 7.7.0+dfsg-2ubuntu1 fails to build with dpkg-gensymbols: warning: debian/libroken18-heimdal/DEBIAN/symbols doesn't match completely debian/libroken18-heimdal.symbols --- debian/libroken18-heimdal.symbols (libroken18-heimdal_7.7.0+dfsg-2ubuntu1_riscv64) +++ dpkg-gensymbolsYtlvSr 2021-10-01 12:31:59.102451503 + @@ -42,7 +42,7 @@ rk_cloexec_dir@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_file@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_socket@HEIMDAL_ROKEN_1.0 1.6~git20131117 - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 +#MISSING: 7.7.0+dfsg-2ubuntu1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_copyhostent@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_free_data@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_lookup@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1945787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945894] Re: Translated strings not imported from damned lies
Ubuntu presumably ships a particular version of GNOME. I understand that this version is no longer based on the major (September) release, but rather a previous minor release, in this case from July. Is that always the case now and is that documented somewhere? As can be seen here, the aforementioned 50 translated strings are missing: https://translations.launchpad.net/ubuntu/impish/+source/gtk+3.0/+pots/gtk-3.0/da/+translate?show=untranslated -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945894 Title: Translated strings not imported from damned lies Status in Ubuntu Translations: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: The newly translated strings in GTK does not seem to be imported from Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but is fully translated in Damned Lies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1945894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945645] Re: cups-pdf prints blank pages
I confirm that after installing printer-driver-cups-pdf 3.0.1-13 from impish/proposed the cups-pdf-printer is working properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945645] Re: cups-pdf prints blank pages
Everything works, 10x printer-driver-cups-pdf: Installed: 3.0.1-13 Candidate: 3.0.1-13 Version table: *** 3.0.1-13 100 100 /var/lib/dpkg/status 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages ghostscript: Installed: 9.54.0~dfsg1-0ubuntu2 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: *** 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status libgs9: Installed: 9.54.0~dfsg1-0ubuntu2 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: *** 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status libgs9-common: Installed: 9.54.0~dfsg1-0ubuntu2 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: *** 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages 500 http://bg.archive.ubuntu.com/ubuntu impish/main i386 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945982] [NEW] Display zoom 125%
Public bug reported: The zoom of my notebook monitor is set to 125%. After pressing F11 to enter the full screen state most of the time, when sliding up / down quickly, two same windows will appear, one smaller window is in the upper left corner, and the zoom ratio of the other window becomes larger (exceeding the screen size). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 19:55:29 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.11.0-36-generic, x86_64: installed acpi-call, 1.1.0, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc Renoir [152d:1268] InstallationDate: Installed on 2021-09-09 (24 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: HUAWEI BOHL-WXX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=d99779ec-6120-48ce-9e05-7cc9ec47539e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2020 dmi.bios.release: 1.5 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BOHL-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1120 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1120 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnHUAWEI:bvr1.05:bd07/20/2020:br1.5:efr1.5:svnHUAWEI:pnBOHL-WXX9:pvrM1120:skuC233:rvnHUAWEI:rnBOHL-WXX9-PCB:rvrM1120:cvnHUAWEI:ct10:cvrM1120: dmi.product.family: MateBook D dmi.product.name: BOHL-WXX9 dmi.product.sku: C233 dmi.product.version: M1120 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1945982 Title: Display zoom 125% Status in xorg package in Ubuntu: New Bug description: The zoom of my notebook monitor is set to 125%. After pressing F11 to enter the full screen state most of the time, when sliding up / down quickly, two same windows will appear, one smaller window is in the upper left corner, and the zoom ratio of the other window becomes larger (exceeding the screen size). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 19:55:29 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.11.0-36-generic, x86_64: installed acpi-call, 1.1.0, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc Renoir [152d:1268] InstallationDate: Installed on 2021-09-09 (24 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: HUAWEI BOHL-WXX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=d99779ec-6120-48ce-9e05-7cc9ec47539e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2020 dmi.bios.release: 1.5 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BOHL-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1120 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendo
[Touch-packages] [Bug 1945894] Re: Translated strings not imported from damned lies
Could you give examples of strings missing? And which Ubuntu serie are you using? ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945894 Title: Translated strings not imported from damned lies Status in Ubuntu Translations: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: The newly translated strings in GTK does not seem to be imported from Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but is fully translated in Damned Lies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1945894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945645] Re: cups-pdf prints blank pages
I have synced cups-pdf 3.0.1-13 into Ubuntu Impish now (see bug 1945939). As soon as you get this version with your updates, please re-test and tell us here how far it solves your problems. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945645] Re: cups-pdf prints blank pages
The newest package (3.0.1-13) has just been imported. Please check whether this fixes the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752]
*** Bug 443069 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
Looks like Debian already fixed it. And their patch names are different :P -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Triaged Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault
My system is focal. Can't try Hirsute yet, dont have any systems with such error appearing. It doesnt work at all for me, fail to resolve anything Link 2 (enp3s0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 2a0d:e40:0:4000::1 DNS Servers: 2a0d:e40:0:4000::1 fd2c:bf12:1194::1 10.255.255.1 8.8.8.8 DNS Domain: ~. spinesystems.solutions udp0 0 127.0.0.53:53 0.0.0.0:* 4106635/systemd-res resolv.conf nameserver: nameserver 127.0.0.53 dig @127.0.0.53 ; <<>> DiG 9.16.1-Ubuntu <<>> @127.0.0.53 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4404 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;. IN NS ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Mon Oct 04 12:34:50 EEST 2021 ;; MSG SIZE rcvd: 28 dig +short @2a0d:e40:0:4000::1www.google.com 142.250.200.196 # systemd-resolve -4 www.google.com www.google.com: resolve call failed: No appropriate name servers or networks for name found But didnt rebooted yet after fetching new systemd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Hirsute: Confirmed Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e
[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault
Sorry for very long delay, many bad events in life. I will give it a try now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Hirsute: Confirmed Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922130] Re: Request addition of Fedora / Redhat "sftp-force-permissions" patch
** Bug watch added: OpenSSH Portable Bugzilla #1844 https://bugzilla.mindrot.org/show_bug.cgi?id=1844 ** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=1844 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1922130 Title: Request addition of Fedora / Redhat "sftp-force-permissions" patch Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Confirmed Bug description: Fedora / Redhat ships openssh with a patch which adds "-m force permission" flag to sftp-server. This is quite a common feature request / support request on the various stackexchange sites - https://superuser.com/questions/332284/in-sftp-how-to-set-the-default- permission-for-all-files-in-a-folder You will see that someone has answered "add -m" there which is indeed the simplest answer by a distance but unfortunately it's a non standard patch: https://src.fedoraproject.org/rpms/openssh/blob/f34/f/openssh-6.7p1-sftp- force-permission.patch This I think should supersede #563216 because they have been shipping this in production presumably since at least 2015 (I see it in fedora 22 branch), so it is a known stable patch compared to the one suggested there. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1922130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945958] [NEW] neon27: Fail to build against OpenSSL 3.0
Public bug reported: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099167/+files/buildlog_ubuntu- impish-amd64.neon27_0.31.2-1.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 A PR has been submitted and merged upstream, and is present in the 0.32.x releases: https://github.com/notroj/neon/pull/59 ** Affects: neon27 (Ubuntu) Importance: Undecided Status: New ** Tags: transition-openssl3-jj -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/1945958 Title: neon27: Fail to build against OpenSSL 3.0 Status in neon27 package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099167/+files/buildlog_ubuntu- impish-amd64.neon27_0.31.2-1.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 A PR has been submitted and merged upstream, and is present in the 0.32.x releases: https://github.com/notroj/neon/pull/59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/1945958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
Just tested the proposed gssproxy fix, and can confirm that it solved the issue Tested on Ubuntu Focal (20.04) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd Status in gssproxy package in Ubuntu: In Progress Status in libselinux package in Ubuntu: Invalid Status in gssproxy source package in Focal: Fix Committed Status in libselinux source package in Focal: Invalid Status in gssproxy source package in Hirsute: Fix Committed Status in libselinux source package in Hirsute: Invalid Bug description: [ Impact ] gssproxy users on Focal and Hiruste who configure the package to handle NFS mountpoints using Kerberos authentication will experience a segmentation fault when invoking the service either through systemd or by hand. [ Test Case] Inside a Focal LXD container: $ lxc launch images:ubuntu/focal gssproxy-bug1788459-focal $ lxc shell gssproxy-bug1788459-focal # apt update # apt install -y gssproxy nfs-kernel-server # cat > /etc/gssproxy/gssproxy.conf << __EOF__ [gssproxy] debug = true debug_level = 3 __EOF__ # cat >> /etc/gssproxy/25-nfs-server.conf << __EOF__ [service/nfs-server] mechs = krb5 socket = /run/gssproxy.sock cred_store = keytab:/etc/krb5.keytab trusted = yes kernel_nfsd = yes euid = 0 __EOF__ # /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock [2021/06/30 14:34:14]: Debug Enabled (level: 3) [2021/06/30 14:34:14]: Keytab /etc/krb5.keytab has no content (-1765328203) [2021/06/30 14:34:14]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18 [2021/06/30 14:34:14]: Client [2021/06/30 14:34:14]: (/usr/sbin/gssproxy) [2021/06/30 14:34:14]: connected (fd = 12)[2021/06/30 14:34:14]: (pid = 3428) (uid = 0) (gid = 0)Segmentation fau lt (core dumped) [ Where problems could occur ] * The backported patch is simple and it is very unlikely that it will introduce a regression. * As usual, it is always risky to rebuild a package that hasn't been touched for more than 1 year, albeit in this case the risk is very low because the package is not very complex. [ Original Description ] I have apache configured to perform a kerberized NFS4 mount using rpc.gssd and gssproxy. If I request a web page that requires NFS4 access, then gssproxy crashes, reporting a segfault in libselinux.so.1 and the web request generates a 403 error. gssproxy[6267]: segfault at 0 ip 7f2f5bb1951a sp 7ffe861da150 error 4 in libselinux.so.1[7f2f5bb0d000+25000] If I run gssproxy at debug level = 3, and then load a web page, I can see the uid/principal request for www-data come in from rpc.gssd: # gssproxy -d --debug-level=3 -i -C /etc/gssproxy [2018/08/22 17:51:40]: Debug Enabled (level: 3) [2018/08/22 17:52:06]: Client [2018/08/22 17:52:06]: (/usr/sbin/rpc.gssd) [2018/08/22 17:52:06]: connected (fd = 10)[2018/08/22 17:52:06]: (pid = 4548) (uid = 33) (gid = 33)Segmentation fault (core dumped) Since gssproxy is required to initiate kerberos principals for any local application services - Ubuntu 18.04 does not currently support running application services with NFS4 kerberos dependencies. This has a fairly significant impact on anyone attempting to implement kerberos on Ubuntu 18.04 Ubuntu 18.04.1 LTS gssproxy 0.8.0-1 libselinux1:amd64 2.7-2build2 libgssrpc4:amd64 1.16-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942764] Re: Enable riscv64 build of mesa-opencl-icd
Note that this will be dropped from the next upload, as LLVM JIT is not available on riscv64 which means apps crash, see Debian bug #995618. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: Fix Released Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551515] Re: My phone's bluetooth is displayed dozens of times under the network list (wifi icon)
** Changed in: network-manager Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1551515 Title: My phone's bluetooth is displayed dozens of times under the network list (wifi icon) Status in One Hundred Papercuts: Expired Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Expired Bug description: I can hardly even start describing how screwed up this is. Have a look at the screenshot. I had seen this before and hadn't even realized that "XT1039 Network" repeated like 37 times had something to do with my own Android phone, a motorola Moto G. Needless to say I have only one. Out of curiosity I clicked on one of "them" (thinking this was some neighboor's device, obviously suspecting it was just one device repeated several times because of a bug), and then my phone vibrated prompting me whether to accept the connection from the computer. Which I did. As a result, the bluetooth indicator next to the network indicator showed a lock icon for a fraction of a second, which immediately disappeared. I guess that means that the computer and the phone peered via bluetooth for a few instants. At the same time, the wifi icon started animating (as if the computer was connecting to a wifi network... or a network of any kind I guess, since the same stupidly designed wifi-like animation is used when connecting to LAN via an ethernet cable). After that, the small lock below the bluetooth icon disappeared, the wifi icon stopped animating and went back to its normal "connected" status (I was previously and still connected to my home router's wifi network), and a baloon saying "Disconnected [NL] Network" appeared and disappeared. Then I repeated the test several times with the same result, except that the phone didn't prompt me any more to accept the connection. This is totally screwed up in several ways. First, there's no reason "XT1039 Network" should be listed AT ALL together with wifi and ethernet networks. What kind of "network" is it supposed to be?? Of course I have not turned on bluetooth tethering on the phone, and bluetooth connection to the phone is already available under the bluetooth indicator. If it makes any sense at all to show the mobile device as a "network" alongside with wifi and cable networks because, well, bluetooth is a network as well, then 1) the list of bluetooth "networks" should have a header, just like "wifi networks" and "ethernet network". Right now, there is just a list of networks that you don't know what kind they are 2) the device should be only listed once, not 37 times 3) I also suspect the 3 items called just "network" are related 4) If it is there at all, it must work. What is it supposed to do? The same as unfolding the menu under the Bluetooth indicator, hovering on the device there (which is listed only once there) and turning on the "Connection" switch? That one does work. This one (in the list of networks) doesn't. And if it is supposed to do something different, it's clearly failing as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 1 03:29:50 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (871 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.167 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2016-01-18 (42 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1551515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
