Many thanks for your help!
Arthur.
On 24 September 2023 9:33:06 pm ACST, Debian Bug Tracking System
wrote:
>This is an automatic notification regarding your Bug report
>which was filed against the konsole package:
>
>#1052542: konsole: version 4:23.08.1-1 missing changelog especially how to
Package: konsole
Version: 4:22.12.3-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading from 4:22.12.3-1 to 4:23.08.1-1
* What exactly did you do (or not do) that was effective (or
Package: libqt5core5a
Version: 5.15.8+dfsg-6
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
[UPGRADE] libqt5concurrent5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5core5a:amd64
Package: libqt5core5a
Version: 5.15.8+dfsg-4
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Doing the following upgrade:
[UPGRADE] libqt5concurrent5:amd64 5.15.8+dfsg-3 -> 5.15.8+dfsg-4
Package: plasma-workspace-data
Version: 4:5.24.2-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrade:
Preparing to unpack .../plasma-workspace-data_4%3a5.24.2-1_all.deb ...
Unpacking
Package: plasma-desktop
Version: 4:5.21.5-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Some recent upgrade of plasma-desktop or associated packages.
* What exactly did you do (or not
Package: plasma-workspace
Version: 4:5.13.5-1+b1
Severity: important
File: /usr/bin/plasmashell
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading packages that plasmashell depended on.
* What exactly
Package: libkwalletbackend5-5
Version: 5.47.0-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading kwallet related libraries from 5.47 to 5.49 I couldn't not access
my passwords stored
Package: konsole
Version: 4:17.08.3-1
Followup-For: Bug #829002
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
randomly seems to change with upgrading packages (latest case was with mesa
libraries)
konsole
Thanks, that helped!
Arthur.
Maximiliano Curia wrote on 06/08/17 06:32:
Control: block -1 by 674936
¡Hola Arthur!
This is a known issue, please disable the flat-volumes option in
pulseaudio adding a line:
flat-volumes = no
to /etc/pulse/daemon.conf
Happy hacking,
Package: kmix
Version: 4:16.08.0-1+b1
Followup-For: Bug #869766
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Playing sound from the analogue input of my Soundblaster Audigy 2ZS,
identified in alsamixer as:
Package: kmix
Version: 4:16.08.0-1+b1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
when playing audio from the analogue input of my Soundblaster Audigy IIZS,
sound levels can change randomly.
Package: plasma-workspace
Version: 4:5.8.4-1
Severity: normal
File: /usr/bin/plasmashell
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Some unknown upgrade, but this problem has persisted through several
Package: plasma-workspace
Version: 4:5.8.4-1
Followup-For: Bug #846389
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Did upgrades to current sid / experimental a few days ago after about 12 days
of no
Diederik de Haas wrote on 06/11/16 10:29:
On zaterdag 5 november 2016 20:25:32 CET Andrey Rahmatullin wrote:
If so, that is/was your problem and you'll likely have various qt5 package
at version 5.7.1~20161021+dfsg-N.
Downgrade those packages to their version in testing and there's a
Package: plasma-workspace
Version: 4:5.8.2-1
Followup-For: Bug #843332
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
After
Package: plasma-workspace
Version: 4:5.8.2-1
Severity: important
File: /usr/bin/plasmashell
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading plasma-workspace and related KDE/Qt packages
Plasma panel
Maximiliano Curia wrote on 30/06/16 16:16:
On Thursday, 30 June 2016 11:40:39 CEST Arthur Marsh wrote:
I've reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829002
Sometime yesterday due to upgrades or something happening when my
computer mouse behaved randomly for a minute or so
I've reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829002
Sometime yesterday due to upgrades or something happening when my
computer mouse behaved randomly for a minute or so, I've lost the
display of unicode/utf-8 characters in konsole, instead seeing the
diamond with a question
Package: konsole
Version: 4:16.04.2-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After some upgrades, prelinking and restarting a plasma session, Japanese
characters displayed as the
Package: kwin-x11
Version: 4:5.5.4-2
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
When using Plastik window decoration, kwin_x11 locks up when iceweasel
restores multiple windows
Package: kwin-x11
Version: 4:5.5.4-2
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After latest updates in unstable, had 3 attempts now in a row of logging into
a plasma session,
Arthur Marsh wrote on 25/02/16 23:46:
So a problem still exists but it doesn't happen as often.
Arthur.
Triggered another bug today: https://bugs.kde.org/show_bug.cgi?id=359839
Arthur.
Arthur Marsh wrote on 25/02/16 23:14:
...
it turned out that I had not applied this upgrade:
[UPGRADE] kwrited:amd64 4:5.4.3-1 -> 4:5.5.4-1
I gave this a try with using org.kde.breeze again after rebooting, then
set the window decoration back to Plastik and rebooted again, and
started f
Reply accidentally sent to sender only instead of to list at first,
resending to list:
Martin Steigerwald wrote on 25/02/16 21:40:
> Arthur,
>
> On Samstag, 20. Februar 2016 20:29:27 CET Arthur Marsh wrote:
>> After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1
Package: plasma-desktop-data
Version: 4:5.5.4-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempting to update plasma-desktop and plasma-desktop data to experimental:
Preparing to unpack
Lisandro Damián Nicanor Pérez Meyer wrote on 25/02/16 12:11:
On Wednesday 24 February 2016 23:04:42 Arthur Marsh wrote:
Arthur Marsh wrote on 20/02/16 20:29:
After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1
have gone, perhaps due to the fix of Debian bug #814958 in libc6
Package: kwin-x11
Version: 4:5.5.4-2
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I ran several tests using kernel:
linux-image-4. 4.4.2-3
* What exactly did you do (or not do)
Package: kwin-x11
Version: 4:5.5.4-2
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
bugs.kde.org marked my report as a duplicate of
https://bugs.kde.org/show_bug.cgi?id=352259
which
Package: kwin-x11
Version: 4:5.5.4-2
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
The last few times kwin_x11 would lock up on the first time running iceweasel
after upgrades of
Arthur Marsh wrote on 20/02/16 20:29:
After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1
have gone, perhaps due to the fix of Debian bug #814958 in libc6.
However, kwin-x11 4:5.5.4-2 locked up when starting iceweasel that
restored multiple windows.
At least I have a working
Package: kwin-x11
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
After a few more updates, I am not
Package: kwin-x11
Version: 4:5.5.4-2
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I was running ok for a few days up until the libstdc++ upgrade associated with
gcc 5.3.1, then tried
After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1
have gone, perhaps due to the fix of Debian bug #814958 in libc6.
However, kwin-x11 4:5.5.4-2 locked up when starting iceweasel that
restored multiple windows.
At least I have a working set-up, but was wondering if
Package: kwin-x11
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
After the latest libc6 update,
Package: kwin-x11
Version: 4:5.4.3-1.1
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After another kernel and other updates, the lock-ups have returned.
* What exactly did you do
Package: kwin-x11
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
At present, after the upgrade to:
Maximiliano Curia wrote on 09/02/16 19:15:
Control: severity -1 wishlist
Control: tag -1 + upstream
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=359169
...
I've forwarded your bug report upstream, if possible, please add yourself to
the cc list of the upstream bug, so if
Package: kwin-x11
Version: 4:5.4.3-1.1
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
With current kernel and libraries, first time to attempt restoring
iceweasel can still lock up
Diederik de Haas wrote on 07/02/16 08:33:
On Sunday 07 February 2016 08:15:35 Arthur Marsh wrote:
Checking the depencies needed to install kwin-x11 from experimental, there
is both a dependency on an unavailable libkinglutil7 package and an existing
libkwinglutils7 package.
And how
Package: kwin-common
Version: 4:5.5.4-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Checking the depencies needed to install kwin-x11 from experimental, there
is both a dependency on an
Diederik de Haas wrote on 07/02/16 10:09:
severity 813938 normal
merge 813938 813701
thanks
On Sunday 07 February 2016 09:50:59 Arthur Marsh wrote:
Sorry, all I read in that reply was:
"even with the fixed libkwinglutils7 package"
and the references didn't mention the libk
Package: kwin-common
Version: 4:5.5.4-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Looking at what was needed to upgrade kwin-related packages to experimental
due to problems with the
Package: kwin-x11
Version: 4:5.4.3-1.1
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
The problem still comes and goes semi-randomly when updating various packages.
This time when it
Package: kwin-x11
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
After experiences problems as late
Arthur Marsh wrote on 16/01/16 02:29:
Carsten Pfeiffer wrote on 16/01/16 00:09:
On Friday 15 January 2016 23:00:13 Arthur Marsh wrote:
Is there any documentation on what configuration file(s) kwin_x11 uses?
You can try starting kwin with strace, like this (when it's not
running
Package: kinit
Version: 5.16.0-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I read on the manual page for kdeinit5:
ENVIRONMENT VARIABLES
$HOME
Specifies the home
Arthur Marsh wrote on 15/01/16 16:54:
...
My next step in debugging was to rename the ~/.config directory when
logged out of KDE plasma, and then logging in and starting iceweasel.
That ran fine, so I reverted the ~/.config directory and moved the 16
most recently modified files
Carsten Pfeiffer wrote on 16/01/16 00:09:
On Friday 15 January 2016 23:00:13 Arthur Marsh wrote:
Is there any documentation on what configuration file(s) kwin_x11 uses?
You can try starting kwin with strace, like this (when it's not running at the
moment):
strace -f -e open kwin_x11 2>
Package: kwin-x11
Version: 4:5.4.3-1.1
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
When iceweasel locked up I did a gdb -p on the kwin_x11 process, I
obtained the backtrace as shown in the attached
Package: kwin-x11
Version: 4:5.4.3-1.1
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I've commented out oldstable from /etc/apt/sources.list, purged most of the
packages now listed as obsolete and re-run things with a
Package: kwin-x11
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
I copied my iceweasel profile
Diederik de Haas wrote on 15/01/16 11:13:
On Friday 15 January 2016 11:02:45 Arthur Marsh wrote:
I've used a stock Debian kernel and removed oldstable packages and still
seeing the same thing happening.
I think your last report was way better then (all) your other reports.
I don't know
Package: kwin-x11
Version: 4:5.4.3-1.1
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
In previous situation where I had started iceweasel alright with the original
account and profile, the panel (k start menu, iceweasel
Package: kinit
Version: 5.16.0-1
Followup-For: Bug #806213
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
This problem
Package: kwin-x11
Version: 4:5.4.3-1.1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Please see bug report #806213 - iceweasel would lock up when restoring
multiple windows.
* What
Package: libqt5core5a
Version: 5.5.1+dfsg-12
Followup-For: Bug #810243
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I was able to successfully start iceweasel using krunner (alt-F2 from
plasma desktop).
I had also been able to successfully
Lisandro Damián Nicanor Pérez Meyer wrote on 14/01/16 15:11:
Arthur: you have filed at least 3 bugs for this very same issue. Please
refrain from doing so in the future. Just file one and let the maintainers
decide.
Hi, thanks for your help in narrowing this down. I've been working
through
Package: kinit
Version: 5.16.0-1
Followup-For: Bug #806213
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I tried starting iceweasel avoiding kinit using krunner (alt F2 from
plasma desktop) and had no problems, therefore the issues appears to
Package: kwin-x11
Version: 4:5.4.3-1.1
Followup-For: Bug #810947
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I found that I could start iceweasel from krunner (alt F2 from plasma
desktop) without issue while kwin-x11 was running.
The problem
Package: kinit
Version: 5.16.0-1
Followup-For: Bug #806213
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After doing some other upgrades and restarting lxdm and KDE, I experienced
an iceweasel lock up earlier
Lisandro Damián Nicanor Pérez Meyer wrote on 09/01/16 11:04:
Is it possible start applications within the KDE plasma desktop without
them having kdeinit5 as a parent/grandparent process?
I tried opening iceweasel from krunner and from the K menu it works perfectly.
How does one open
Package: libqt5core5a
Version: 5.5.1+dfsg-11
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I have been having ongoing problems with iceweasel locking up on startup
from kdeinit5 (see Debian
Lisandro Damián Nicanor Pérez Meyer wrote on 08/01/16 05:48:
By the way, why using kdeini5 with iceweasel?
The purpose of kdeinit5, according to it's manpage, is:
Using kdeinit5 to launch KDE applications makes starting a typical KDE
application a couple times faster and reduces
Package: kinit
Version: 5.16.0-1
Followup-For: Bug #806213
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
I applied the fix at
Arthur Marsh wrote on 04/01/16 17:15:
PS, the problem listed at https://bugs.kde.org/show_bug.cgi?id=356580
also seems to apply to kinit 5.17.0-1 in the reported case. I don't know
if the kinit/kwin-x11 in Debian unstable have the same problem.
Arthur.
Applying the fix at https
Martin Steigerwald wrote on 29/12/15 17:34:
Am Mittwoch, 23. Dezember 2015, 23:11:59 CET schrieb Arthur Marsh:
Do you have any specific suggestions for a plasma-specific forum, or
just kde.org?
There are kde related user mailing lists for different languages. And well the
forums. Both
Martin Steigerwald wrote on 23/12/15 20:54:
Hi Arthur,
I'm again having to run under lxdm/xfce - am I the only person having
this problem with KDE?
As I think I said I have no issues with iceweasel on Plasma 5 session. Self-
compiled KF5 and KDEPIM together with Plasma 5 packages from
Arthur Marsh wrote on 20/12/15 09:29:
Arthur Marsh wrote on 19/12/15 21:43:
Arthur Marsh wrote on 19/12/15 14:01:
I managed to run KDE another day with iceweasel fine, then the more
recent updates stopped it again.
The general symptom is that the iceweasel windows lock up at the stage
when
Package: kinit
Version: 5.16.0-1
Followup-For: Bug #806213
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
This report lists a possible cause and solution:
https://bugs.kde.org/show_bug.cgi?id=356580
*** End of the template - remove these
Arthur Marsh wrote on 19/12/15 21:43:
Arthur Marsh wrote on 19/12/15 14:01:
I managed to run KDE another day with iceweasel fine, then the more
recent updates stopped it again.
The general symptom is that the iceweasel windows lock up at the stage
when multiple windows are being restored
Arthur Marsh wrote on 19/12/15 14:01:
I managed to run KDE another day with iceweasel fine, then the more
recent updates stopped it again.
The general symptom is that the iceweasel windows lock up at the stage
when multiple windows are being restored. Unless one kills the kdeinit
processes
Jimmy Johnson wrote on 17/12/15 14:52:
Besides XFCE4 I'm also looking at the "Trinity Desktop" ported to
Debian, currently I have both Jessie and Stretch installed with Trinity,
but I'm taking it slow, it's still a longtime before Stretch goes
finial, but it has been disturbing me with all the
Arthur Marsh wrote on 15/12/15 16:18:
and the problem seems to have gone away with the upgrade of packages
based on kde4libs from 4:4.14.14-1 to 4:4.14.14-1+b1
Arthur.
Back again with a vengeance, I can't even bring up iceweasel in gdb
under KDE without it locking up.
I can run
Arthur Marsh wrote on 15/12/15 08:27:
I'm again seeing the problem after the libxml2 and gtk2 updates to
unstable: iceweasel locks up when started from kdeinit (the start menu),
but starts fine from a konsole window inside kde.
The problem occurs at a time when numerous iceweasel windows
Jimmy Johnson wrote on 15/12/15 07:49:
On 12/14/2015 10:16 AM, Jimmy Johnson wrote:
On 12/12/2015 11:52 PM, Luc Castermans wrote:
...
Yes you are right it should have nothing to do with the driver you have
installed, but since testing plasma it has so far been the case, there
is a big
Arthur Marsh wrote on 03/12/15 23:23:
With an update to KDE from unstable, iceweasel from unstable locked up
every time until I upgraded iceweasel to experimental. Now iceweasel
runs fine under KDE.
As previously mentioned running with Radeon 3200HD (RS780) and vdpau
libraries installed
Arthur Marsh wrote on 26/11/15 23:10:
Martin Steigerwald wrote on 25/11/15 08:46:
Am Montag, 23. November 2015, 15:30:19 CET schrieb Arthur Marsh:
Arthur Marsh wrote on 19/11/15 16:26:
It appears that the fix applied to qt5base-opensource-src 5.5.1+dfsg-8
in relation to the bug: https
Package: kinit
Version: 5.15.0-1
Followup-For: Bug #806213
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I found that gimp from unstable didn't start properly and had to be started
from a konsole command line
Package: kinit
Version: 5.15.0-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Starting iceweasel from kdeinit (see also Debian bug 804060).
* What exactly did you do (or not do) that was
MERLIN Philippe wrote on 24/11/15 02:24:
Further to the last ones update Debian: gcc-5, libstdc kde jams
constantly, in the starting up with the only one the screen of starting
up and visible progress, black screen...
I had similar problems, so far my solution was to upgrade chromium to
the
Arthur Marsh wrote on 19/11/15 16:26:
It appears that the fix applied to qt5base-opensource-src 5.5.1+dfsg-8
in relation to the bug: https://bugreports.qt.io/browse/QTBUG-46323
has improved things.
The new gcc-5 libraries seemed to have caused problems also.
Both iceweasel and chromium
Brad Rogers wrote on 20/11/15 22:20:
On Fri, 20 Nov 2015 12:17:31 +0100
Holger Schramm wrote:
Hello Holger,
I have the same problem but it changes after the reboot. After one
reboot they are gone with the next some are back again. It's like
roulette but with icons in the
Source: qtbase-opensource-src
Followup-For: Bug #805341
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
iceweasel is running successfully under gdb under KDE with the kernel
linux-image-4.3.0-trunk-amd64
Diederik de Haas wrote on 19/11/15 10:59:
On Thursday 19 November 2015 10:30:20 Arthur Marsh wrote:
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Kernel: Linux 4.4.0-rc1+ (SMP w/4 CPU cores; PREEMPT)
Have you tried cleaning up
Source: qtbase-opensource-src
Followup-For: Bug #805341
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After upgrading packages based on qtbase-opensource-src from
5.5.1+dfsg-7 to 5.5.1+dfsg-8, running iceweasel
Arthur Marsh wrote on 17/11/15 19:18:
Funnily enough, iceweasel runs alright under KDE if started from the
command line in a konsole window, with or without gdb, but it locks up
if started from the K menu.
Arthur.
latest "fun" with the qt5base-opensource-src 5.5.1+dfsg-8 base
Arthur Marsh wrote on 19/11/15 10:46:
Arthur Marsh wrote on 17/11/15 19:18:
Funnily enough, iceweasel runs alright under KDE if started from the
command line in a konsole window, with or without gdb, but it locks up
if started from the K menu.
Arthur.
latest "fun" with t
I had one success running:
genkdmconf
to get things working after a downgrade, but after another upgrade then
downgrade even genkdmconf doesn't help me.
Arthur.
Funnily enough, iceweasel runs alright under KDE if started from the
command line in a konsole window, with or without gdb, but
Arthur Marsh wrote on 17/11/15 14:39:
Arthur Marsh wrote on 10/11/15 10:19:
Arthur Marsh wrote on 10/11/15 08:22:
Arthur Marsh wrote on 10/11/15 07:49:
For the second time I'm seeing this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060
some upgrade in the last few days did
Arthur Marsh wrote on 10/11/15 10:19:
Arthur Marsh wrote on 10/11/15 08:22:
Arthur Marsh wrote on 10/11/15 07:49:
For the second time I'm seeing this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060
some upgrade in the last few days did it, my local Debian mirror wasn't
updating
Package: qtbase-opensource-src
Version: 5.5.1+dfsg-7
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading packages based on qtbase-opensource-src 5.5.1+dfsg-6 -> 5.5.1+dfsg-7
iceweasel
Arthur Marsh wrote on 10/11/15 07:49:
For the second time I'm seeing this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060
some upgrade in the last few days did it, my local Debian mirror wasn't
updating and when I switched to an alternative had over 100 packages to
update
For the second time I'm seeing this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060
some upgrade in the last few days did it, my local Debian mirror wasn't
updating and when I switched to an alternative had over 100 packages to
update.
The problem could be related to using a
Arthur Marsh wrote on 10/11/15 08:22:
Arthur Marsh wrote on 10/11/15 07:49:
For the second time I'm seeing this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060
some upgrade in the last few days did it, my local Debian mirror wasn't
updating and when I switched to an alternative
Carlos Kosloff wrote on 06/11/15 03:02:
On 11/03/2015 09:40 PM, Carlos Kosloff wrote:
After the botched upgrade involving libqt5x11extras5, my computer
cannot start normally.
The latest upgrades brought newer versions of sddm and
glx-alternative-*, which are now at 0.6.93.
sddm is also in the
Carlos Kosloff wrote on 08/11/15 03:29:
It was at the end of the thread, but anyway here it is again:
1) run genkdmconf as root.
2) cd /usr/share/kde4/apps/kdm/faces/
3) cp .default.face.icon .default.face
4) set kdm to start to plasma, instead of previous (default), so it will
not revert to
Diederik de Haas wrote on 05/11/15 04:46:
On Thursday 05 November 2015 04:06:13 Arthur Marsh wrote:
I still get a lock-up with the stock Debian 4.2.0-1 kernel.
I hope that it isn't a sign of a GPU going bad...
Does the lockup also happen when you have your browser open but don't have a
tab
Diederik de Haas wrote on 04/11/15 21:52:
On Wednesday 04 November 2015 21:30:30 Arthur Marsh wrote:
kactivitymanage[3999]: segfault at 7ff6c35c7cd0 ip 00302bc14291 sp
7ffc7b321ff8 error 4 in libQt5Sql.so.5.5.1[302bc0+3f000]
That is a known issue: https://bugs.debian.org/803451
Diederik de Haas wrote on 04/11/15 22:52:
On Wednesday 04 November 2015 22:35:54 Arthur Marsh wrote:
Thanks, what I'm seeing is if I either upgrade the following packages to
the 5.5.1+dfsg-6 versions, or run a kernel later than 4.3.0 (or both), I
get the lock-up in KDE starting up iceweasel
1 - 100 of 201 matches
Mail list logo