Would you please configure buildlogs.centos.org and mirror.centos.org to host Ceph nautilus content for the alternative architectures?<br />
<br />
Buildlogs mapping (-testing tag):<br />
<br />
storage7-ceph-nautilus-testing|7/storage/aarch64/ceph-nautilus/|7/storage/aarch64/ceph-nautilus/|7/storage/aarch64/ceph-nautilus/<br />
storage7-ceph-nautilus-testing|7/storage/ppc64le/ceph-nautilus/|7/storage/ppc64le/ceph-nautilus/|7/storage/ppc64le/ceph-nautilus/<br />
<br />
mirror.centos.org mapping (-release tag):<br />
<br />
storage7-ceph-nautilus-release|7/storage/aarch64/ceph-nautilus/|7/storage/aarch64/ceph-nautilus/|7/storage/aarch64/ceph-nautilus/<br />
storage7-ceph-nautilus-release|7/storage/ppc64le/ceph-nautilus/|7/storage/ppc64le/ceph-nautilus/|7/storage/ppc64le/ceph-nautilus/
↧
0015699: configure buildlogs.centos.org and mirror.centos.org for ceph aarch64 and ppc64le
↧
0015700: set nautilus build tag to inherit from released devtoolset-7
Would you please set up our nautilus build tag to inherit from sclo7-devtoolset-7-rh-release instead of -candidate ?<br />
<br />
cbs remove-tag-inheritance storage7-ceph-nautilus-el7-build sclo7-devtoolset-7-rh-candidate<br />
cbs add-tag-inheritance --priority=25 storage7-ceph-nautilus-el7-build sclo7-devtoolset-7-rh-release<br />
<br />
We want to build against released packages, not candidate packages.
↧
↧
0015701: [abrt] kdelibs: KCrash::defaultCrashHandler(int)(): kdeinit4 killed by SIGSEGV
Description of problem:<br />
Doing very first steps, playing with TurboVNC 2.2.1 with multiple virtual monitors. <br />
Changed desktop mode from "Default" to "Folder view", moving icons around and so on.<br />
<br />
Version-Release number of selected component:<br />
kdelibs-4.14.8-6.el7_3<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (10 frames)<br />
#1 KCrash::defaultCrashHandler(int) at /lib64/libkdeui.so.5<br />
#3 Tasks::init at /usr/src/debug/kde-workspace-4.11.19/plasma/desktop/applets/tasks/tasks.cpp:103<br />
#4 Plasma::ContainmentPrivate::initApplets() at /usr/lib64/libplasma.so.3<br />
#5 Plasma::CoronaPrivate::importLayout(KConfigBase const&, bool) at /usr/lib64/libplasma.so.3<br />
#6 Plasma::Corona::loadLayout(QString const&) at /usr/lib64/libplasma.so.3<br />
#7 Plasma::Corona::initializeLayout(QString const&) at /usr/lib64/libplasma.so.3<br />
#8 PlasmaApp::corona at /usr/src/debug/kde-workspace-4.11.19/plasma/desktop/shell/plasmaapp.cpp:856<br />
#9 PlasmaApp::setupDesktop at /usr/src/debug/kde-workspace-4.11.19/plasma/desktop/shell/plasmaapp.cpp:314<br />
#10 PlasmaApp::qt_static_metacall at /usr/src/debug/kde-workspace-4.11.19/x86_64-redhat-linux-gnu/plasma/desktop/shell/plasmaapp.moc:128<br />
#11 QObject::event at kernel/qobject.cpp:1222
↧
0014444: [abrt] kdelibs: KCrash::defaultCrashHandler(int)(): kdeinit4 killed by SIGSEGV
Version-Release number of selected component:<br />
kdelibs-4.14.8-6.el7_3<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (10 frames)<br />
#1 KCrash::defaultCrashHandler(int) at /lib64/libkdeui.so.5<br />
#3 XRandROutput::update at /usr/src/debug/libkscreen-1.0.1/backends/xrandr/xrandroutput.cpp:123<br />
#4 XRandR::updateOutput at /usr/src/debug/libkscreen-1.0.1/backends/xrandr/xrandr.cpp:115<br />
#5 QMetaObject::activate at kernel/qobject.cpp:3547<br />
#6 outputChanged at /usr/src/debug/libkscreen-1.0.1/x86_64-redhat-linux-gnu/backends/xrandr/xrandrx11helper.moc:119<br />
#7 XRandRX11Helper::x11Event at /usr/src/debug/libkscreen-1.0.1/backends/xrandr/xrandrx11helper.cpp:140<br />
#8 KSystemEventFilterPrivate::filterEvent(void*) at /lib64/libkdeui.so.5<br />
#9 QAbstractEventDispatcher::filterEvent at kernel/qabstracteventdispatcher.cpp:542<br />
#10 x11EventSourceDispatch at kernel/qguieventdispatcher_glib.cpp:145<br />
#14 g_main_context_iteration at gmain.c:3988
↧
0015702: [abrt] kdelibs: qt_xio_errhandler(): kdeinit4 killed by SIGSEGV
Description of problem:<br />
Doing very first steps, playing with TurboVNC 2.2.1 with multiple virtual monitors. <br />
Changed desktop mode from "Default" to "Folder view", moving icons around and so on.<br />
<br />
Version-Release number of selected component:<br />
kdelibs-4.14.8-6.el7_3<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (10 frames)<br />
#8 qt_xio_errhandler at kernel/qapplication_x11.cpp:773<br />
#9 KApplication::xioErrhandler(_XDisplay*) at /lib64/libkdeui.so.5<br />
#12 XEventsQueued at Pending.c:43<br />
#13 x11EventSourceCheck at kernel/qguieventdispatcher_glib.cpp:85<br />
#14 g_main_context_check at gmain.c:3734<br />
#16 g_main_context_iteration at gmain.c:3962<br />
#17 QEventDispatcherGlib::processEvents at kernel/qeventdispatcher_glib.cpp:450<br />
#18 QGuiEventDispatcherGlib::processEvents at kernel/qguieventdispatcher_glib.cpp:207<br />
#19 QEventLoop::processEvents at kernel/qeventloop.cpp:149<br />
#20 QEventLoop::exec at kernel/qeventloop.cpp:204
↧
↧
0015522: Machine with older uefi fw doesn't boot with newer shim (like on Apple 2008 iMac)
With the shim pkgs being rebased on v15 (it was v12 before), there is a new check that is considered critical and then power off the machine instead of loading grub2 (in the normal shim => grub2 => kernel chain)
↧
0015703: cert for status.centos.org has expired
The https certificate for status.centos.org has expired.
↧
0009190: Automatic Logout Feature not working
Automatic Logout feature is not working as set forth in:<br />
<a href="https://people.gnome.org/~pmkovar/system-admin-guide/automatic-logout.html">https://people.gnome.org/~pmkovar/system-admin-guide/automatic-logout.html</a><br />
and<br />
(14.3.7) <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/user-sessions.html#configuring-automatic-logout">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/user-sessions.html#configuring-automatic-logout</a><br />
<br />
User recieves a notification that they will be logged off, however the actual logoff never takes place
↧
0015137: SELinux is preventing /usr/bin/mongod from 'read' accesses on the file snmp.
Description of problem:<br />
> installed mongodb 3.6 <br />
> semanage port -a -t mongod_port_t -p tcp 27017<br />
> added new service in firewalld and reloaded<br />
> systemctl enable mongod.service<br />
> systemctl start mongod.service<br />
<br />
ended up in selinux alert .<br />
<br />
/usr/bin/mongod attempted to read file [ snmp , netstat]<br />
SELinux is preventing /usr/bin/mongod from 'read' accesses on the file snmp.<br />
<br />
***** Plugin catchall (100. confidence) suggests **************************<br />
<br />
If you believe that mongod should be allowed read access on the snmp file by default.<br />
Then you should report this as a bug.<br />
You can generate a local policy module to allow this access.<br />
Do<br />
allow this access for now by executing:<br />
# ausearch -c 'ftdc' --raw | audit2allow -M my-ftdc<br />
# semodule -i my-ftdc.pp<br />
<br />
Additional Information:<br />
Source Context system_u:system_r:mongod_t:s0<br />
Target Context system_u:object_r:proc_net_t:s0<br />
Target Objects snmp [ file ]<br />
Source ftdc<br />
Source Path /usr/bin/mongod<br />
Port <Unknown><br />
Host (removed)<br />
Source RPM Packages mongodb-org-server-3.6.6-1.el7.x86_64<br />
Target RPM Packages <br />
Policy RPM selinux-policy-3.13.1-192.el7_5.4.noarch<br />
Selinux Enabled True<br />
Policy Type targeted<br />
Enforcing Mode Enforcing<br />
Host Name (removed)<br />
Platform Linux (removed) 3.10.0-862.9.1.el7.x86_64 #1 SMP<br />
Mon Jul 16 16:29:36 UTC 2018 x86_64 x86_64<br />
Alert Count 7774<br />
First Seen 2018-08-02 19:15:43 IST<br />
Last Seen 2018-08-03 16:41:09 IST<br />
Local ID 8481e838-3c4f-44af-9ecc-1a42e9f97651<br />
<br />
Raw Audit Messages<br />
type=AVC msg=audit(1533294669.0:10944): avc: denied { read } for pid=16268 comm="ftdc" name="snmp" dev="proc" ino=4026532002 scontext=system_u:system_r:mongod_t:s0 tcontext=system_u:object_r:proc_net_t:s0 tclass=file<br />
<br />
<br />
type=SYSCALL msg=audit(1533294669.0:10944): arch=x86_64 syscall=open success=no exit=EACCES a0=7fa28e290590 a1=0 a2=7fa28e290590 a3=4e7 items=0 ppid=1 pid=16268 auid=4294967295 uid=983 gid=976 euid=983 suid=983 fsuid=983 egid=976 sgid=976 fsgid=976 tty=(none) ses=4294967295 comm=ftdc exe=/usr/bin/mongod subj=system_u:system_r:mongod_t:s0 key=(null)<br />
<br />
Hash: ftdc,mongod_t,proc_net_t,file,read<br />
<br />
Version-Release number of selected component:<br />
selinux-policy-3.13.1-192.el7_5.4.noarch
↧
↧
0015704: [abrt] virt-manager: poll_for_event(): python2.7 killed by SIGABRT
Description of problem:<br />
closed a windows session and tried another user<br />
<br />
Version-Release number of selected component:<br />
virt-manager-1.5.0-1.el7<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (10 frames)<br />
#4 poll_for_event at xcb_io.c:256<br />
#5 poll_for_response at xcb_io.c:274<br />
#7 XPending at Pending.c:55<br />
#8 gdk_event_source_prepare at gdkeventsource.c:269<br />
#10 g_main_context_prepare at gmain.c:3473<br />
#12 g_main_context_iteration at gmain.c:3962<br />
#13 g_application_run at gapplication.c:2470<br />
#14 ffi_call_unix64 at ../src/x86/unix64.S:76<br />
#15 ffi_call at ../src/x86/ffi64.c:522<br />
#16 pygi_invoke_c_callable at pygi-invoke.c:679
↧
0015526: autofs stop working after upgrade to CentOS 7.6.1810
This morning yum-cron updated CentOS to 7.6.1810 and autofs stopped working. It's been working for at least one year before.<br />
<br />
When starting "/usr/sbin/automount -d -v --foreground --dont-check-daemon" I get the output shown in attached file "automount.txt". <br />
<br />
Dmesg shows:<br />
automount[25212]: segfault at 7fa6c8516320 ip 00007fa6c99926d0 sp 00007fa6c8dd63e8 error 4 in libcrypto.so.1.0.2k[7fa6c986b000+234000]<br />
<br />
Abrt message: see attached abort.txt<br />
<br />
The relevant Ldap entries are:<br />
<br />
ou=automount,ou=auto.master,BASEDN<br />
objectClass = automountMap<br />
(children)<br />
-- cn=/-<br />
automountInformation = auto.shares<br />
objectClass = automount<br />
<br />
ou=auto.shares,ou=automount,BASEDN<br />
objectClass = automountMap<br />
(children)<br />
-- cn = /data<br />
objectClass = automount<br />
automountInformation = -nfsvers=3 serverX:/export/data
↧
0015705: ps/2 mouse Fehler
System nicht mehr bedienbar
↧
0015469: NFV SIG: nfv-common directory target for release
Need directory target for nfv-common-release packages.<br />
<br />
I now have all dependent packages for build of new releases VPP 1810 tagged into nfv-common-release.<br />
(with exception of dev-toolset7 - bug#15370)<br />
<br />
Now need destination target directory for release<br />
<br />
nfv7-common-release -> <a href="http://mirror.centos.org/centos/7/nfv/x86_64/nfv-common">http://mirror.centos.org/centos/7/nfv/x86_64/nfv-common</a><br />
<br />
<a href="https://buildlogs.centos.org/centos/7/nfv/x86_64/nfv-common/">https://buildlogs.centos.org/centos/7/nfv/x86_64/nfv-common/</a>
↧
↧
0014578: 802.3ad emits kernel error option slaves: invalid value
We have lacp enabled network on two nics: ens1f0 and ensf1. After configurating bond0 with the appropriate configuration, the following error is shown:<br />
kernel: bond0: option slaves: invalid value (-ens1f0)<br />
kernel: bond0: option slaves: invalid value (-ens1f1)<br />
<br />
What is strange is the (-) in front of the name even though the correct interface name (ens1f[0|1] without the dash) exist in `ip link` or `cat /proc/net/dev`
↧
0014427: kernel panic at __kmalloc_track_caller+0x95/0x230
It has been happening from time to time in one VM (KVM) normally when the system has low memory avaliable, the machine crashes and reboot itself. Also, there was an app trying to restart an usb device at the same time this app was using ~70% of the memory when it happened. This output below was created by abrt-cli. <br />
<br />
I can see a similar error at <a href="https://access.redhat.com/solutions/1404013">https://access.redhat.com/solutions/1404013</a> whitout solution yet.<br />
<br />
from backtrace:<br />
<br />
general protection fault: 0000 [#1] SMP <br />
Modules linked in: fuse unix_diag tcp_diag inet_diag binfmt_misc nfsv3 nfs fscache ext4 mbcache jbd2 iosf_mbi crc32_pclmul ghash_clmulni_intel aesni_intel lrw ppdev gf128mul glue_helper ablk_helper cryptd pcspkr virtio_balloon parport_pc parport i2c_piix4 nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs libcrc32c ata_generic pata_acpi virtio_blk virtio_console virtio_net floppy cirrus drm_kms_helper crct10dif_pclmul crct10dif_common syscopyarea sysfillrect serio_raw sysimgblt ata_piix crc32c_intel fb_sys_fops ttm drm libata virtio_pci virtio_ring i2c_core virtio dm_mirror dm_region_hash dm_log dm_mod<br />
CPU: 3 PID: 5881 Comm: python Not tainted 3.10.0-514.10.2.el7.x86_64 #1<br />
Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011<br />
task: ffff88031d2d3ec0 ti: ffff880119460000 task.ti: ffff880119460000<br />
RIP: 0010:[<ffffffff811dffe5>] [<ffffffff811dffe5>] __kmalloc_track_caller+0x95/0x230<br />
RSP: 0018:ffff880119463b38 EFLAGS: 00010286<br />
RAX: 0000000000000000 RBX: 0000000000000008 RCX: 00000000007d2a3d<br />
RDX: 00000000007d2a3c RSI: 0000000000000000 RDI: 0000000000000000<br />
RBP: ffff880119463b70 R08: 0000000000019a20 R09: ffff88017fc01e00<br />
R10: 0000000000000008 R11: ffff88013b71a184 R12: 00000000000000d0<br />
R13: 48ffff8800365f79 R14: 0000000000000008 R15: ffff88017fc01e00<br />
FS: 00007fe95d316740(0000) GS:ffff88032dd80000(0000) knlGS:0000000000000000<br />
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br />
CR2: 00000000520b2003 CR3: 000000015562e000 CR4: 00000000001406e0<br />
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br />
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400<br />
Stack:<br />
ffff88017fc01e00 ffffffffa04e3b02 0000000000000008 ffff88013b71a184<br />
ffffea000724d800 ffff8801c9360000 ffff880119463d28 ffff880119463b90<br />
ffffffff8119f0b0 ffff880119463e68 0000000000000003 ffff880119463c98<br />
Call Trace:<br />
[<ffffffffa04e3b02>] ? nfs_readdir_page_filler+0x2f2/0x5b0 [nfs]<br />
[<ffffffff8119f0b0>] kmemdup+0x20/0x50<br />
[<ffffffffa04e3b02>] nfs_readdir_page_filler+0x2f2/0x5b0 [nfs]<br />
[<ffffffffa04e3fcd>] nfs_readdir_xdr_to_array+0x20d/0x3b0 [nfs]<br />
[<ffffffff8118aec6>] ? __alloc_pages_nodemask+0x176/0x420<br />
[<ffffffffa04e4170>] ? nfs_readdir_xdr_to_array+0x3b0/0x3b0 [nfs]<br />
[<ffffffffa04e4192>] nfs_readdir_filler+0x22/0x90 [nfs]<br />
[<ffffffff8118125f>] do_read_cache_page+0x7f/0x190<br />
[<ffffffff81212530>] ? fillonedir+0xe0/0xe0<br />
[<ffffffff811813ac>] read_cache_page+0x1c/0x30<br />
[<ffffffffa04e43db>] nfs_readdir+0x1db/0x6b0 [nfs]<br />
[<ffffffffa03ecbb0>] ? nfs3_xdr_dec_getattr3res+0x80/0x80 [nfsv3]<br />
[<ffffffff81212530>] ? fillonedir+0xe0/0xe0<br />
[<ffffffff81212420>] vfs_readdir+0xb0/0xe0<br />
[<ffffffff81212845>] SyS_getdents+0x95/0x120<br />
[<ffffffff81696b09>] system_call_fastpath+0x16/0x1b<br />
Code: d0 00 00 49 8b 50 08 4d 8b 28 49 8b 40 10 4d 85 ed 0f 84 20 01 00 00 48 85 c0 0f 84 17 01 00 00 49 63 47 20 48 8d 4a 01 4d 8b 07 <49> 8b 5c 05 00 4c 89 e8 65 49 0f c7 08 0f 94 c0 84 c0 74 b8 49 <br />
RIP [<ffffffff811dffe5>] __kmalloc_track_caller+0x95/0x230<br />
RSP <ffff880119463b38><br />
<br />
<br />
from vmcore-dmesg.txt:<br />
<br />
[2408779.877811] Out of memory: Kill process 29334 (python) score 834 or sacrifice child<br />
[2408779.877885] Killed process 29334 (python) total-vm:9764928kB, anon-rss:6364472kB, file-rss:780kB, shmem-rss:0kB<br />
[2410491.594856] python[2103]: segfault at 18 ip 00007fd8d054101d sp 00007ffc6b9b4730 error 4 in VimbaGigETL.cti[7fd8d04f9000+a0000]<br />
[2704262.601116] usb 1-3: USB disconnect, device number 15<br />
[3748370.544914] usb 1-4: new high-speed USB device number 16 using ehci-pci<br />
[3748370.848827] usb 1-4: New USB device found, idVendor=136e, idProduct=000c<br />
[3748370.848853] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0<br />
[3757493.529500] usb 1-4: USB disconnect, device number 16<br />
[3758393.420557] usb 1-5: new high-speed USB device number 17 using ehci-pci<br />
[3758393.720956] usb 1-5: New USB device found, idVendor=136e, idProduct=000c<br />
[3758393.720962] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0<br />
[3760531.985197] usb 1-5: USB disconnect, device number 17<br />
[3760533.412606] usb 1-6: new high-speed USB device number 18 using ehci-pci<br />
[3760533.699051] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64<br />
[3760533.701081] usb 1-6: New USB device found, idVendor=136e, idProduct=000c<br />
[3760533.701086] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
[3760533.701089] usb 1-6: Product: USB CAM<br />
[3760533.701092] usb 1-6: Manufacturer: ANDOR<br />
[3760533.723441] usb 1-6: usbfs: interface 0 claimed by usbfs while 'python' sets config #1<br />
[3760533.734346] usb 1-6: usbfs: interface 0 claimed by usbfs while 'python' sets config #1<br />
[3840490.630822] usb 1-6: USB disconnect, device number 18<br />
[4445054.331735] usb 1-1: new high-speed USB device number 19 using ehci-pci<br />
[4445054.632730] usb 1-1: New USB device found, idVendor=136e, idProduct=000c<br />
[4445054.632736] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0<br />
[4445133.710295] usb 1-1: USB disconnect, device number 19<br />
[4445135.389629] usb 1-2: new high-speed USB device number 20 using ehci-pci<br />
[4445135.674247] usb 1-2: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64<br />
[4445135.675748] usb 1-2: New USB device found, idVendor=136e, idProduct=000c<br />
[4445135.675753] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
[4445135.675757] usb 1-2: Product: USB CAM<br />
[4445135.675759] usb 1-2: Manufacturer: ANDOR<br />
[4445135.687434] usb 1-2: usbfs: interface 0 claimed by usbfs while 'python' sets config #1<br />
[4445135.700433] usb 1-2: usbfs: interface 0 claimed by usbfs while 'python' sets config #1<br />
[4577710.372066] general protection fault: 0000 [#1] SMP <br />
[4577710.372142] Modules linked in: fuse unix_diag tcp_diag inet_diag binfmt_misc nfsv3 nfs fscache ext4 mbcache jbd2 iosf_mbi crc32_pclmul ghash_clmulni_intel aesni_intel lrw ppdev gf128mul glue_helper ablk_helper cryptd pcspkr virtio_balloon parport_pc parport i2c_piix4 nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs libcrc32c ata_generic pata_acpi virtio_blk virtio_console virtio_net floppy cirrus drm_kms_helper crct10dif_pclmul crct10dif_common syscopyarea sysfillrect serio_raw sysimgblt ata_piix crc32c_intel fb_sys_fops ttm drm libata virtio_pci virtio_ring i2c_core virtio dm_mirror dm_region_hash dm_log dm_mod<br />
[4577710.372840] CPU: 3 PID: 5881 Comm: python Not tainted 3.10.0-514.10.2.el7.x86_64 #1<br />
[4577710.372909] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011<br />
[4577710.372961] task: ffff88031d2d3ec0 ti: ffff880119460000 task.ti: ffff880119460000<br />
[4577710.373026] RIP: 0010:[<ffffffff811dffe5>] [<ffffffff811dffe5>] __kmalloc_track_caller+0x95/0x230<br />
[4577710.373111] RSP: 0018:ffff880119463b38 EFLAGS: 00010286
↧
0015706: [abrt] systemd: udev_device_new_from_device_id(): systemd-journald killed by SIGABRT
Description of problem:<br />
unknown<br />
<br />
Version-Release number of selected component:<br />
systemd-219-57.el7<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (6 frames)<br />
#0 udev_device_new_from_device_id at src/libudev/libudev-device.c:838<br />
#1 dev_kmsg_record at src/journal/journald-kmsg.c:221<br />
#2 server_read_dev_kmsg at src/journal/journald-kmsg.c:348<br />
#3 source_dispatch at src/libsystemd/sd-event/sd-event.c:2115<br />
#4 sd_event_dispatch at src/libsystemd/sd-event/sd-event.c:2472<br />
#5 sd_event_run at src/libsystemd/sd-event/sd-event.c:2501
↧
0015707: Volume (and wireless) keys not working after upgrade
When switching from 3.10.0-862.14.4 to<br />
the newest kernel (3.10.0-956.1.3),<br />
the volume keys become unresponsive.<br />
(asus-nb-wmi is the module responsible for this, afaik).<br />
<br />
Also using the presenter key now results in an<br />
unrecoverable black screen (not sure if related to the other keys, but also triggered by new kernel).
↧
↧
0015708: The ipcalc command might be corrupt
When using the ipcalc command with / 31<br />
An error occurs<br />
Thank you
↧
0015709: 終端機程式游標消失
同時裝有漢語(zh)及漢語(chewing)酷音兩種輸入法，當使用酷音輸入法的英文模式時在終端機程式中輸入第一行指令後按Enter，原本閃爍的游標即消失再也不會出現。在游標已經消失的狀況下若同時有啟動另一個視窗程式將視窗焦點移至另一個視窗程式再移回來，消失的閃爍游標就會再出現。<br />
相同的環境下使用漢語(zh)則沒有上述問題。
↧
0015710: provide a new namespace for ember-csi STAGE environment
ember-csi namespace is our PROD environment<br />
STAGE environment is required to test new features without breaking production services
↧