March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1068647] New: btrfs send bails out on orphan inode
by bugzilla_noreply＠novell.com 01 Sep '20

01 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1068647 Bug ID: 1068647 Summary: btrfs send bails out on orphan inode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I can't create backups of my currently active subvolume with btrfs send any more. It proceeeds for several minutes, than bails out with the error message ERROR: send ioctl failed with -2: No such file or directory This situation has persisted throughout several reboots, remounts, and kernel updates. This first occured while I was doing lots of experiments with btrfs-send, working on my "btrfs-clone" utility (https://github.com/mwilck/btrfs-clone) and testing the efficiency of various cloning strategies within this tool. I made several successful snapshots, until suddenly the described situation came to pass which makes it impossible to do any more snapshots of the "main" subvol. Thus it's possible that the situation was caused by btrfs-send. I admit I did this while the subvolume was mounted. Of course I'd always set the cloned subvolume and its parent to read-only mode while ran btrfs-send (it will abort otherwise). Except for the btrfs-send, no other problems have been observed so far. All other tools (btrfs image, btrfs scrub, btrfs inspect-internal dump-tree) silently ignored this situation. I've traced the error down to the following call stack: > send_subvol() > full_send_tree() > changed_cb [btrfs]() > finish_inode_if_needed [btrfs]() > get_inode_info.constprop.48 [btrfs]() > apply_children_dir_moves [btrfs]() > send_utimes [btrfs]() > get_cur_path [btrfs]() > __get_cur_name_and_parent [btrfs]() > is_inode_existent.part.15 [btrfs]() > get_first_ref [btrfs]() get_first_ref() returns with -ENOENT. I used some instrumentation to find out what was causing this problem, and found the following situation in the file system tree: root tree 28090400768(level 0) / 28058992640(1) - subvol @/.subvols/1/snapshot is item 89 at 28061384704 > root tree > node 28058992640 level 1 items 5 free 488 generation 188885 owner 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > key (EXTENT_TREE ROOT_ITEM 0) block 28090400768 (1714502) gen 188885 > > leaf 28090400768 items 98 free space 6117 generation 188885 owner 1 > leaf 28090400768 flags 0x1(WRITTEN) backref revision 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > > item 5 key (ROOT_TREE_DIR INODE_ITEM 0) itemoff 14770 itemsize 160 > generation 3 transid 0 size 0 nbytes 16384 > block group 0 mode 40755 links 1 uid 0 gid 0 rdev 0 > sequence 0 flags 0x0(none) > atime 1493728330.0 (2017-05-02 14:32:10) > ctime 1493728330.0 (2017-05-02 14:32:10) > mtime 1493728330.0 (2017-05-02 14:32:10) > otime 1493728330.0 (2017-05-02 14:32:10) > > item 12 key (257 ROOT_ITEM 0) itemoff 13191 itemsize 439 > generation 180352 root_dirid 256 bytenr 36967874560 level 0 refs 1 > lastsnap 12 byte_limit 0 bytes_used 16384 flags 0x0(none) > uuid d4ad4958-2cc1-004e-934d-f223ef4c5f2a > ctransid 180352 otransid 8 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 13 key (257 ROOT_BACKREF 5) itemoff 13172 itemsize 19 > root backref key dirid 256 sequence 2 name @ > > item 33 key (258 ROOT_ITEM 0) itemoff 12290 itemsize 439 > generation 188511 root_dirid 256 bytenr 17933533184 level 1 refs 1 > lastsnap 0 byte_limit 0 bytes_used 163840 flags 0x0(none) > uuid e99de79b-c494-9445-812b-d08389f82947 > ctransid 188511 otransid 11 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 34 key (258 ROOT_BACKREF 257) itemoff 12262 itemsize 28 > root backref key dirid 256 sequence 3 name .snapshots > > item 89 key (259 ROOT_ITEM 12) itemoff 10419 itemsize 439 > generation 188884 root_dirid 256 bytenr 28061384704 level 2 refs 1 > lastsnap 186971 byte_limit 0 bytes_used 259981312 flags 0x0(none) > uuid 17c54832-5028-694c-9f97-1be0a1df8757 > parent_uuid d4ad4958-2cc1-004e-934d-f223ef4c5f2a > ctransid 188884 otransid 12 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 90 key (259 ROOT_BACKREF 258) itemoff 10393 itemsize 26 > root backref key dirid 257 sequence 2 name snapshot File system tree 28061384704 - btrfs path 28052832256(level 0) / 28045197312(1) / 28061384704(2) - item 8 (1746132 INODE_ITEM 0) has "links 0" and no ref - item 86 is an ORPHAN node linking to item 8. > file tree key (259 ROOT_ITEM 12) > node 28061384704 level 2 items 56 free 437 generation 188884 owner 259 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > > key (1732417 INODE_REF 830626) block 28045197312 (1711743) gen 188860 > > node 28045197312 level 1 items 341 free 152 generation 188860 owner 259 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > ... > key (1746122 INODE_ITEM 0) block 28052832256 (1712209) gen 188821 > > leaf 28052832256 items 66 free space 8146 generation 188821 owner 259 > leaf 28052832256 flags 0x1(WRITTEN) backref revision 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > ... > item 7 key (1746123 EXTENT_DATA 4096) itemoff 15701 itemsize 53 > generation 188295 type 1 (regular) > extent data disk byte 470392832 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 8 key (1746132 INODE_ITEM 0) itemoff 15541 itemsize 160 > generation 188295 transid 188472 size 940 nbytes 4096 > block group 0 mode 100644 links 0 uid 465 gid 464 rdev 0 > sequence 16 flags 0x6(PREALLOC) > atime 1510830949.715375999 (2017-11-16 12:15:49) > ctime 1510838729.976180731 (2017-11-16 14:25:29) > mtime 1510830949.687375946 (2017-11-16 12:15:49) > otime 1510830949.687375946 (2017-11-16 12:15:49) > item 9 key (1746132 EXTENT_DATA 0) itemoff 15488 itemsize 53 > generation 188295 type 1 (regular) > extent data disk byte 470614016 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 10 key (1746213 INODE_ITEM 0) itemoff 15328 itemsize 160 > generation 188342 transid 188819 size 6498 nbytes 8192 > block group 0 mode 100600 links 1 uid 0 gid 0 rdev 0 > sequence 0 flags 0x4(none) > atime 1510849204.24960545 (2017-11-16 17:20:04) > ctime 1510833103.94629539 (2017-11-16 12:51:43) > mtime 1510833103.86629524 (2017-11-16 12:51:43) > otime 1510833037.158509427 (2017-11-16 12:50:37) > ... > item 85 key (1746369 EXTENT_DATA 0) itemoff 7030 itemsize 53 > generation 188860 type 1 (regular) > extent data disk byte 368373760 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 86 key (ORPHAN ORPHAN_ITEM 1746132) itemoff 7030 itemsize 0 > orphan item So, while trying to process inode 1746213, btrfs send runs finish_inode_if_needed() on 1746132, and fails to send the utimes for this inode because it can't figure out the path. The way I'm reading the btrfs code, it seems that btrfs-send assumes that all orphans have been cleaned up when it starts running. Indeed, btrfs should have got rid of orphan nodes by running btrfs_orphan_cleanup() via btrfs_cleanup_fs_roots() at mount time, but that doesn't seem to be the case. In fact, I've run btrfs-debug tree on this file system two times with different FS generations, and found that the orphan inode hat changed its position (inode number) in the tree. Unfortunately I didn't keep the output of the first debug run, but I'm positive that the inode number of the failing inode was in the 1743xxx range first, and is now 1746132. Therefore I'm filing this as a kernel bug. The problem was first seen with kernel 4.13.11-1.1.g0526da3 now I'm running 4.14.0-1.1.gab9e909. There are 3 aspects to this problem: 1) how did it come to pass? 2) why doesn't the kernel clean up the orphan at boot time? Why does the orphan change inode number? Or is the orphan actually cleaned, but a new one is generated instead? 3) how do I recover? I'd really love to get rid of this broken inode. I could simply switch to a different snapshot of the file system, but AFAICS as long as I don't delete the offending subvolume, the situation would persist. Anyway, as long as 1) and 2) are open, I guess I'd rather keep the subvolume around to facilitate further debugging. I'm unsure if this is easily reproducible. -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 1051159] New: GTK3 file picker in print section of Firefox/Thunderbird
by bugzilla_noreply＠novell.com 31 Aug '20

31 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1051159 Bug ID: 1051159 Summary: GTK3 file picker in print section of Firefox/Thunderbird Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: roman(a)pletka.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Change the gtk3 file picker when printing a page as a pdf file. Steps: firefox is on any web page, print (Ctrl +P, or file->print...) select "print to file" click on file name opens a gtk3 file picker. The whole file dialog is GTK3, that needs to be implemented in mozilla-kde.patch. Thanks, Roman -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1069695] New: virt-manager doesn't grab the pointer correctly
by bugzilla_noreply＠novell.com 27 Aug '20

27 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1069695 Bug ID: 1069695 Summary: virt-manager doesn't grab the pointer correctly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: adrien.plazas(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- virt-manager doesn't capture the mouse anymore: when the mouse should be grabbed (because the guest has its own mouse pointer) if I move it too far I see the host's pointer reappearing outside the window, but unfortunately the two pointers don't match and I can't access all the elements on the guest's screen. It may be because I'm using GNOME/Wayland, I didn't check with GNOME/Xorg yet. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1010996] New: With Firefox 50, ISRG X1 CA to ca-certificates-mozilla should be added
by bugzilla_noreply＠novell.com 26 Aug '20

26 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1010996 Bug ID: 1010996 Summary: With Firefox 50, ISRG X1 CA to ca-certificates-mozilla should be added Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of Firefox 50's main feature is the inclusion of the ISRG Root X1 CA certificate. This is not reflected in Leap. ca-certificates-mozilla in all distributions, including Tumbleweed and Leap, is still 2.7 from March. Please include ISRG Root X1. -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 937020] New: pdfcsplain ommits czech characters
by bugzilla_noreply＠novell.com 26 Aug '20

26 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=937020 Bug ID: 937020 Summary: pdfcsplain ommits czech characters Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.jakl(a)qbicon.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36 Build Identifier: pdfcsplain from texlive ommits czech characters from resulting pdf document. At first it complained that there are some files generated with pdftex, so I've run sudo fmtutil --all, after that it works, but results are not correct. Reproducible: Always Steps to Reproduce: 1. install texlive 2. run 'sudo fmtutil --all' 3. run pdfcsplain test.tex 4. compare resulting pdf with test-13.2.pdf -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1080430] New: Mono console applications don't work with the update to terminfo 6.1
by bugzilla_noreply＠novell.com 25 Aug '20

25 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1080430 Bug ID: 1080430 Summary: Mono console applications don't work with the update to terminfo 6.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono Assignee: bnc-team-mono(a)forge.provo.novell.com Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the update of terminfo to 6.1, running console applications with mono doens't work anymore: ----------------------------------------------------- mono UnSIN.exe Unhandled Exception: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542 at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <8f8a76535f644930b25f735cdc17065c>:0 at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <8f8a76535f644930b25f735cdc17065c>:0 at System.TermInfoDriver..ctor (System.String term) [0x00055] in <8f8a76535f644930b25f735cdc17065c>:0 at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <8f8a76535f644930b25f735cdc17065c>:0 at System.ConsoleDriver..cctor () [0x0004d] in <8f8a76535f644930b25f735cdc17065c>:0 --- End of inner exception stack trace --- at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <8f8a76535f644930b25f735cdc17065c>:0 at System.Console..cctor () [0x0008e] in <8f8a76535f644930b25f735cdc17065c>:0 --- End of inner exception stack trace --- at UnSIN.Program.Main (System.String[] args) [0x00006] in <7c4247c4deca4ba5a7657dbbe6ac76e0>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542 at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <8f8a76535f644930b25f735cdc17065c>:0 at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <8f8a76535f644930b25f735cdc17065c>:0 at System.TermInfoDriver..ctor (System.String term) [0x00055] in <8f8a76535f644930b25f735cdc17065c>:0 at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <8f8a76535f644930b25f735cdc17065c>:0 at System.ConsoleDriver..cctor () [0x0004d] in <8f8a76535f644930b25f735cdc17065c>:0 --- End of inner exception stack trace --- at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <8f8a76535f644930b25f735cdc17065c>:0 at System.Console..cctor () [0x0008e] in <8f8a76535f644930b25f735cdc17065c>:0 --- End of inner exception stack trace --- at UnSIN.Program.Main (System.String[] args) [0x00006] in <7c4247c4deca4ba5a7657dbbe6ac76e0>:0 ----------------------------------------------------- My TERM is set to screen-256color, changing it to xterm fixed it. ----------------------------------------------------- TERM=xterm mono UnSIN.exe ERROR: Invalid parameters! ----------------------------------------------------- libslang2 seems to have had a similar issue see: https://build.opensuse.org/request/show/574532 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1006973] New: terminfo setting 'rxvt-unicode-256color' in /etc/DIR_COLORS is missing
by bugzilla_noreply＠novell.com 18 Aug '20

18 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1006973 Bug ID: 1006973 Summary: terminfo setting 'rxvt-unicode-256color' in /etc/DIR_COLORS is missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: wnereiz(a)eienteiland.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- (For both openSUSE Leap 42.1 and Tumbleweed) There is rxvt-unicode setting there in /etc/DIR_COLORS currently: #Below, there should be one TERM entry for each termtype that is colorizable ... TERM rxvt-unicode ... It's not working for 256color: $ echo $TERM rxvt-unicode-256color $ dircolors -b /etc/DIR_COLORS LS_COLORS=''; export LS_COLORS The ls command output results without any colors in rxvt-unicode terminal. Try to add 'rxvt-unicode-256color': ... TERM rxvt-unicode TERM rxvt-unicode-256color ... Then it works, and colors come back. I'm not sure if 'rxvt-16color', 'rxvt-88color' and 'rxvt-256color' need to be added, because I'm using rxvt-unicode only. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 968600] New: Journal is being flooded with "'/usr/sbin/crda' failed with exit code 255" errors
by bugzilla_noreply＠novell.com 17 Aug '20

17 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=968600 Bug ID: 968600 Summary: Journal is being flooded with "'/usr/sbin/crda' failed with exit code 255" errors Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: alex.richardson(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I get these messages every few seconds: Feb 28 19:35:55 Alex-laptop systemd-udevd[15510]: Process '/usr/sbin/crda' failed with exit code 255. Feb 28 19:35:58 Alex-laptop systemd-udevd[15513]: Process '/usr/sbin/crda' failed with exit code 255. Feb 28 19:35:58 Alex-laptop kernel: cfg80211: World regulatory domain updated: Feb 28 19:35:58 Alex-laptop kernel: cfg80211: DFS Master region: unset Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:35:58 Alex-laptop kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Feb 28 19:36:01 Alex-laptop systemd-udevd[15516]: Process '/usr/sbin/crda' failed with exit code 255. Feb 28 19:36:01 Alex-laptop kernel: cfg80211: World regulatory domain updated: Feb 28 19:36:01 Alex-laptop kernel: cfg80211: DFS Master region: unset Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:01 Alex-laptop kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Feb 28 19:36:05 Alex-laptop systemd-udevd[15519]: Process '/usr/sbin/crda' failed with exit code 255. Feb 28 19:36:05 Alex-laptop kernel: cfg80211: World regulatory domain updated: Feb 28 19:36:05 Alex-laptop kernel: cfg80211: DFS Master region: unset Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Feb 28 19:36:05 Alex-laptop kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Running crda manually also doesn't seem to work: # COUNTRY=GB crda Failed to set regulatory domain: -7 Alex-laptop:~ # echo $? 249 It seems to be an informational message, but it hides all useful output for me, for now I just commented the line KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/sbin/crda" in /usr/lib/udev/rules.d/85-regulatory.rules. I don't know if this can cause any problem, but so far wireless seems to still work. The only other related thing I have found is https://bugzilla.suse.com/show_bug.cgi?id=937756 but that seems to be fixed and https://github.com/systemd/systemd/issues/922 which seems to be a different issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1074181] New: Eclipse packaging
by bugzilla_noreply＠novell.com 17 Aug '20

17 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1074181 Bug ID: 1074181 Summary: Eclipse packaging Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Enhancement Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The Eclipse IDE and the Rich Client Platform (RCP) are very popular in the business and scientific world. According to https://pkgs.org/download/eclipse openSUSE is one of the few distributions which still lack support for it. While that might look grim, let's see what we already got: * https://software.opensuse.org/package/eclipse-swt * https://software.opensuse.org/package/swtchart * https://software.opensuse.org/package/swtcalendar However everything that is built with Maven/Tycho or has circular dependencies is still problematic. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1068424] New: xmlgraphics-fop exits with error (works on Leap)
by bugzilla_noreply＠novell.com 10 Aug '20

10 Aug '20

http://bugzilla.suse.com/show_bug.cgi?id=1068424 Bug ID: 1068424 Summary: xmlgraphics-fop exits with error (works on Leap) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fs(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 748931 --> http://bugzilla.suse.com/attachment.cgi?id=748931&action=edit FO file used for the fop command fop is called with this command: ADDITIONAL_FLAGS="-Djavax.xml.transform.URIResolver=org.apache.xml.resolver.tools.CatalogResolver -Djava.util.logging.config.file=/etc/fop/fop_logging.properties " ADDITIONAL_JARS="batik-all excalibur/avalon-framework-impl " ADDITIONAL_OPTIONS=" -Xss2048K " fop -q "hitchhiker-guide-fop_color_en.fo hitchhiker-guide_color_en.pdf" and errors out with ----------------------------- Java virtual machine used: /usr/lib64/jvm/jre/bin/java classpath used: /usr/share/java/xmlgraphics-fop.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/batik-all.jar:/usr/share/java/xml-commons-jaxp-1.3-apis.jar:/usr/share/java/xml-commons-jaxp-1.3-apis-ext.jar:/usr/share/java/batik-all.jar:/usr/share/java/excalibur/avalon-framework-impl.jar main class used: org.apache.fop.cli.Main flags used: '-Djavax.xml.transform.URIResolver=org.apache.xml.resolver.tools.CatalogResolver' '-Djava.util.logging.config.file=/usr/share/daps/etc/fop/fop_logging.properties' options used: '-Xss2048K' arguments used: -c /etc/fop.xconf /home/tux/suse-doc-howtos/build/.tmp/hitchhiker-guide-fop_color_en.fo /home/tux/suse-doc-howtos/build/hitchhiker-guide/hitchhiker-guide_color_en.pdf Exception in thread "main" java.lang.NoSuchMethodError: java.nio.CharBuffer.limit(I)Ljava/nio/CharBuffer; at org.apache.fop.fo.FOText.characters(FOText.java:137) at org.apache.fop.fo.FObjMixed.characters(FObjMixed.java:74) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.characters(FOTreeBuilder.java:388) at org.apache.fop.fo.FOTreeBuilder.characters(FOTreeBuilder.java:136) at com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.characters(ToXMLSAXHandler.java:546) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:546) at com.sun.org.apache.xerces.internal.xinclude.XIncludeHandler.characters(XIncludeHandler.java:1131) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:455) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(TransformerImpl.java:668) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:737) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:351) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:285) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:216) ----------------------------- daps-2.4.0-3.3.noarch suse-xsl-stylesheets-2.0.8-1.1.noarch xmlgraphics-fop-2.1-6.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 5