>@10dmar10
>Do you have lxapperance-obconf installed too? If yes, have you tried removing
>it?
lxapperance and lxapperance-obconf are installed on my system as a
required dependency of lxde.
Removing lxapperance-obconf would break lxde, I would prefer not to do that...
>And if poss
Package: lxappearance-obconf
Version: 0.2.3-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: 10dma...@gmail.com
Hi,
it seems since the last upgrade from 0.2.3-1 to 0.2.3-2 this package is
causing a segfault in lxappearance.
see also:
attached gdb backtrace text
Package: lxappearance
Version: 0.6.3-5
Followup-For: Bug #1052210
X-Debbugs-Cc: 10dma...@gmail.com
Hi,
same problem seems to be present in 0.6.3-5:
dmesg:
[47142.279706] lxappearance[34694]: segfault at 1449b354 ip 7f9a72442fa4
sp 7fff8dc57158 error 4 in
Package: lxappearance
Version: 0.6.3-3
Severity: important
Hi,
upgrading lxappearance from 0.6.3-1 to 0.6.3-3 leads to following error:
# console output:
:~$ lxappearance
(lxappearance:30166): dbind-WARNING **: 04:06:35.052: AT-SPI: Error retrieving
accessibility bus address:
Hi,
updating chromium to 99.0.4844.74-1 seems to have fixed this problem, thanks.
2022-02-19 0:08 GMT+01:00, 10dmar10 <10dma...@gmail.com>:
>> I just uploaded 98.0.4758.102-1, please let me know if it still happens
>> there.
>> Also, do you get symbols in the backtrac
I just uploaded 98.0.4758.102-1, please let me know if it still happens there.
Also, do you get symbols in the backtrace when you run "chromium -g"?
Hi,
the warning is still present in version 98.0.4758.102-1,
but there is a slight change:
the trap seems to be catched by chromium itself - gdb
Strange, with installed debug packages still no symbols:
# aptitude search chromium
i chromium - Webbrowser
p chromium-bsu - Schneller, scrollender
Space Shooter im Arkadestil
p chromium-bsu-data- data
Package: chromium
Version: 98.0.4758.80-1
Severity: minor
Hi,
since upgrading chromium to 97.0.4692.99-1 (and still present in 98.0.4758.80-1)
I noticed some debug breakpoint warnings in the system log.
The messages appear on browser start only.
There were no observable negative effects from
m 20.10.21 um 12:27 schrieb Michael Biebl:
> Am 20.10.21 um 12:08 schrieb 10dmar10:
>> Ok, thanks!
>>
>> You're right, the kernel should probably issue warnings only on
>> mounts, not remounts.
>>
>> * Any idea why those warnings started to appear only a
Ok, thanks!
You're right, the kernel should probably issue warnings only on
mounts, not remounts.
* Any idea why those warnings started to appear only after recent
systemd update?
* Is masking systemd-hostnamed.service a valid solution to prevent log spam?
At least until the kernel developers
Package: systemd
Version: 249.5-1
Severity: normal
Hi,
I noticed since upgrade to systemd 249.5-1 on 2021-10-15 following
remount warnings in my log files, usually when some service is started.
While there are no problems caused by this behavior so far (besides spamming
into log a lot),
I
Hi,
the problem is solved in libclc-r600 version: 0.2.0+git20180518-1, thanks.
Hi,
Applying suggested patch set from
http://lists.llvm.org/pipermail/libclc-dev/2018-March/002851.html has no
effect.
I've tried current commit 569bb0e5fea20e5ec9698650732303a19b196ee2 from
upstream, the problem seems to be fixed in that one.
(I used info from
Package: libclc-r600
Version: 0.2.0+git20180312-2
Severity: normal
Hi,
after recent upgrading I wasn't able to run any OpenCL application anymore.
Any attempt to compile an OpenCL kernel fails with following error:
fatal error: cannot open file '/usr/lib/clc/juniper-r600--.bc': Invalid record
Package: rox-filer
Version: 1:2.11-1
Followup-For: Bug #546907
Same problem: invoking Panel Options on a rox panel doesn't show the dialog
window,
instead following warnings are shown:
** (rox:17715): WARNING **: Failed to load builder file
/usr/share/rox/Templates.ui: Failed to open file
15 matches
Mail list logo
