Re: konsole 24.08.2
Hi Sedat. Sedat Dilek - 13.10.24, 05:01:03 MESZ: > I have build konsole 24.08.2 successfully. Thanks. For the instructions. They may come in handy for me in the future. I'd rather wait for 24.08.2 to arrive. Especially as I do not have any issues with 24.08.0. Did you have any which caused you to do the build? Or did you just build it cause you can? :) Given you start to build your own packages… if you have time at hand, do you consider contributing? The team can benefit from a helping hand. Best, -- Martin - please no carbon copy to me
konsole 24.08.2
Hi,
I have build konsole 24.08.2 successfully.
[ INSTRUCTIONS ]
[ KONSOLE 24.08.2 ]
[ EDIT /etc/apt/sources.list.d/debian-sources.list ]
# Debian/unstable sources
deb-src https://deb.debian.org/debian unstable main contrib non-free
non-free-firmware
# Debian/experimental sources
deb-src https://deb.debian.org/debian experimental main contrib
non-free non-free-firmware
-EOF-
root# apt-get update
root# apt-get build-dep konsole/experimental -s <--- XXX: Check
BUILD-DEPS (sid + exp) yourself!
[ AS USER ]
cd $HOME/src/konsole
APP_NAME="konsole"
APP_VER="24.08.2"
KDE_MIRROR="https://download.kde.org/stable/release-service";
wget -O ${APP_NAME}_${APP_VER}.orig.tar.xz
${KDE_MIRROR}/${APP_VER}/src/${APP_NAME}-${APP_VER}.tar.xz
wget -O ${APP_NAME}_${APP_VER}.orig.tar.xz.asc
${KDE_MIRROR}/${APP_VER}/src/${APP_NAME}-${APP_VER}.tar.xz.sig
apt-source konsole -t experimental
tar -xf konsole_${APP_VER}.orig.tar.xz
cp -av konsole-24.08.0/debian konsole-${APP_VER}/
export DEBFULLNAME="Sedat Dilek"
export DEBEMAIL="sedat.di...@gmail.com"
dch -i
$ head -10 debian/changelog
konsole (4:24.08.2-1~dileks) experimental; urgency=medium
* Non-maintainer upload.
* New upstream release (24.08.2).
-- Sedat Dilek Sun, 15 Sep 2024 19:14:44 +0200
konsole (4:24.08.0-1) experimental; urgency=medium
[ Sandro Knauß ]
...
LC_ALL=C debuild
sudo dpkg -i konsole_24.08.2-1~dileks_amd64.deb
konsole-kpart_24.08.2-1~dileks_amd64.deb
-dileks // 11-Oct-2024: konsole version 24.08.2
Best regards,
-Sedat-
Re: Building konsole version 24.08.0
[ KONSOLE 24.08.1 ]
[ EDIT /etc/apt/sources.list.d/debian-sources.list ]
# Debian/unstable sources
deb-src https://deb.debian.org/debian unstable main contrib non-free
non-free-firmware
# Debian/experimental sources
deb-src https://deb.debian.org/debian experimental main contrib
non-free non-free-firmware
-EOF-
root# apt-get update
root# apt-get build-dep konsole/experimental -s <--- XXX: Check
BUILD-DEPS (sid + exp) yourself!
[ AS USER ]
cd $HOME/src/konsole
APP_VER="24.08.1"
KDE_MIRROR="https://download.kde.org/stable/release-service";
wget -O konsole_${APP_VER}.orig.tar.xz
${KDE_MIRROR}/${APP_VER}/src/konsole-${APP_VER}.tar.xz
wget -O konsole_${APP_VER}.orig.tar.xz.asc
${KDE_MIRROR}/${APP_VER}/src/konsole-${APP_VER}.tar.xz.sig
apt-source konsole -t experimental
tar -xf konsole_${APP_VER}.orig.tar.xz
cp -av konsole-24.08.0/debian konsole-${APP_VER}/
export DEBFULLNAME="Sedat Dilek"
export DEBEMAIL="sedat.di...@gmail.com"
dch -i
$ head -10 debian/changelog
konsole (4:24.08.1-1~dileks) experimental; urgency=medium
* Non-maintainer upload.
* New upstream release (24.08.1).
-- Sedat Dilek Sun, 15 Sep 2024 19:14:44 +0200
konsole (4:24.08.0-1) experimental; urgency=medium
[ Sandro Knauß ]
...
LC_ALL=C debuild
sudo dpkg -i konsole_24.08.1-1~dileks_amd64.deb
konsole-kpart_24.08.1-1~dileks_amd64.deb
$ konsole --version
konsole 24.08.1
-dileks // 15-Sep-2024: konsole version 24.08.1
Re: Building konsole version 24.08.0
INFO: konsole (4:24.08.0-1) is available from D/exp. -sed@-
Re: Building konsole version 24.08.0
I use Sedat's build also. No issues sofar, I like it. Op wo 4 sep 2024 om 15:31 schreef Sedat Dilek : > Hi, > > So, I am using my selfmade konsole for more than 10 days. > Looks good - works good. > > Any chance to get an update of konsole-24.08.0 into Debian/experimental? > > Thanks. > > Best regards, > -Sedat- > > On Sat, Aug 24, 2024 at 5:06 PM Sedat Dilek wrote: > > > > Hi, > > > > yesterday someone asked for ktorrent from KDE/Apps version 24.08.0. > > > > Today, afternoon I played with NEW konsole. > > > > Here is my quick mini-howto. > > > > [ PREREQ ] > > > > INFO: You should have some experiences in Debian packaging. > > > > > > [ BUILD-DIR ] > > > > mkdir $HOME/src/konsole > > > > > > [ WGET ] > > > > wget > http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2-1.dsc > > wget > http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2-1.debian.tar.xz > > wget > http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2.orig.tar.xz > > wget > http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2.orig.tar.xz.asc > > > > wget -O konsole_24.08.0.orig.tar.xz > > > https://download.kde.org/stable/release-service/24.08.0/src/konsole-24.08.0.tar.xz > > wget -O konsole_24.08.0.orig.tar.xz.asc > > > https://download.kde.org/stable/release-service/24.08.0/src/konsole-24.08.0.tar.xz.sig > > > > > > [ STEAL DEBIAN-DIR ] > > > > dpkg-source -x *.dsc > > > > tar -xf konsole_24.08.0.orig.tar.xz > > > > cp -av konsole-24.05.2/debian konsole-24.08.0/ > > > > > > [ BUILDDEP - MANUALLY ] > > > > root# apt-get install -t experimental libkf6bookmarks-dev > > libkf6config-dev libkf6configwidgets-dev libkf6coreaddons-dev > > libkf6crash-dev libkf6dbusaddons-dev libkf6doctools-dev > > libkf6globalaccel-dev libkf6guiaddons-dev libkf6i18n-dev > > libkf6iconthemes-dev libkf6kio-dev libkf6newstuff-dev > > libkf6notifications-dev libkf6notifyconfig-dev libkf6parts-dev > > libkf6pty-dev libkf6service-dev libkf6textwidgets-dev > > libkf6widgetsaddons-dev libkf6windowsystem-dev libkf6xmlgui-dev > > qt6-5compat-dev/unstable qt6-multimedia-dev/unstable > > qt6-tools-dev/unstable qt6-wayland-dev/unstable > > qt6-declarative-dev/unstable libqt6core5compat6/unstable > > qt6-base-private-dev/unstable qt6-declarative-dev-tools/unstable > > qt6-qmllint-plugins/unstable qt6-qmltooling-plugins/unstable > > libqt6designercomponents6/unstable libqt6help6/unstable > > qt6-tools-dev-tools/unstable libkf6dbusaddons-dev/unstable > > > > INFO: QT-6 DEVEL packages from Debian/unstable. > > > > > > [ DCH ] > > > > export DEBFULLNAME="Sedat Dilek" > > export DEBEMAIL="sedat.di...@gmail.com" > > > > dch -i > > > > konsole (4:24.08.0-1~dileks) experimental; urgency=low > > > > * Non-maintainer upload. > > * New upstream release (24.08.0). > > * debian/konsole.install: > > - Copy data/konsolerc file to /etc/xdg/ directory > > - Copy data/konsole.knsrc file to /usr/share/knsrcfiles/ directory > > * debian/konsole-kpart.install: > > - Copy color-schemes, keyboard-layouts and layouts files from data/ > > to /usr/share/konsole/ directory > > > > -- Sedat Dilek Sat, 24 Aug 2024 15:21:34 +0200 > > > > konsole (4:24.05.2-1) experimental; urgency=medium > > ... > > > > > > [ DIFF ] > > > > git diff konsole-24.05.2/debian/konsole.install > > konsole-24.08.0/debian/konsole.installdiff --git > > a/konsole-24.05.2/debian/konsole.install > > b/konsole-24.08.0/debian/konsole.install > > index a7fe591e5bbb..970d0c685aca 100644 > > --- a/konsole-24.05.2/debian/konsole.install > > +++ b/konsole-24.08.0/debian/konsole.install > > @@ -1,4 +1,4 @@ > > -etc/xdg/konsolerc > > +data/konsolerc etc/xdg/ > > usr/bin/konsole > > usr/bin/konsoleprofile > > usr/lib/*/kconf_update_bin/konsole_globalaccel > > @@ -11,7 +11,7 @@ usr/share/kconf_update/konsole.upd > > usr/share/kconf_update/konsole_add_hamburgermenu_to_toolbar.sh > > usr/share/kglobalaccel/org.kde.konsole.desktop > > usr/share/kio/servicemenus/konsolerun.desktop > > -usr/share/knsrcfiles/konsole.knsrc > > +data/konsole.knsrc usr/share/knsrcfiles/ > > usr/share/locale/ > > usr/share/metainfo/org.kde.konsole.appdata.xml > > usr/share/qlogging-categories6/konsole.categories > > > > git diff konsole-24.05.2/
Re: Building konsole version 24.08.0
Hi, So, I am using my selfmade konsole for more than 10 days. Looks good - works good. Any chance to get an update of konsole-24.08.0 into Debian/experimental? Thanks. Best regards, -Sedat- On Sat, Aug 24, 2024 at 5:06 PM Sedat Dilek wrote: > > Hi, > > yesterday someone asked for ktorrent from KDE/Apps version 24.08.0. > > Today, afternoon I played with NEW konsole. > > Here is my quick mini-howto. > > [ PREREQ ] > > INFO: You should have some experiences in Debian packaging. > > > [ BUILD-DIR ] > > mkdir $HOME/src/konsole > > > [ WGET ] > > wget http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2-1.dsc > wget > http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2-1.debian.tar.xz > wget > http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2.orig.tar.xz > wget > http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2.orig.tar.xz.asc > > wget -O konsole_24.08.0.orig.tar.xz > https://download.kde.org/stable/release-service/24.08.0/src/konsole-24.08.0.tar.xz > wget -O konsole_24.08.0.orig.tar.xz.asc > https://download.kde.org/stable/release-service/24.08.0/src/konsole-24.08.0.tar.xz.sig > > > [ STEAL DEBIAN-DIR ] > > dpkg-source -x *.dsc > > tar -xf konsole_24.08.0.orig.tar.xz > > cp -av konsole-24.05.2/debian konsole-24.08.0/ > > > [ BUILDDEP - MANUALLY ] > > root# apt-get install -t experimental libkf6bookmarks-dev > libkf6config-dev libkf6configwidgets-dev libkf6coreaddons-dev > libkf6crash-dev libkf6dbusaddons-dev libkf6doctools-dev > libkf6globalaccel-dev libkf6guiaddons-dev libkf6i18n-dev > libkf6iconthemes-dev libkf6kio-dev libkf6newstuff-dev > libkf6notifications-dev libkf6notifyconfig-dev libkf6parts-dev > libkf6pty-dev libkf6service-dev libkf6textwidgets-dev > libkf6widgetsaddons-dev libkf6windowsystem-dev libkf6xmlgui-dev > qt6-5compat-dev/unstable qt6-multimedia-dev/unstable > qt6-tools-dev/unstable qt6-wayland-dev/unstable > qt6-declarative-dev/unstable libqt6core5compat6/unstable > qt6-base-private-dev/unstable qt6-declarative-dev-tools/unstable > qt6-qmllint-plugins/unstable qt6-qmltooling-plugins/unstable > libqt6designercomponents6/unstable libqt6help6/unstable > qt6-tools-dev-tools/unstable libkf6dbusaddons-dev/unstable > > INFO: QT-6 DEVEL packages from Debian/unstable. > > > [ DCH ] > > export DEBFULLNAME="Sedat Dilek" > export DEBEMAIL="sedat.di...@gmail.com" > > dch -i > > konsole (4:24.08.0-1~dileks) experimental; urgency=low > > * Non-maintainer upload. > * New upstream release (24.08.0). > * debian/konsole.install: > - Copy data/konsolerc file to /etc/xdg/ directory > - Copy data/konsole.knsrc file to /usr/share/knsrcfiles/ directory > * debian/konsole-kpart.install: > - Copy color-schemes, keyboard-layouts and layouts files from data/ > to /usr/share/konsole/ directory > > -- Sedat Dilek Sat, 24 Aug 2024 15:21:34 +0200 > > konsole (4:24.05.2-1) experimental; urgency=medium > ... > > > [ DIFF ] > > git diff konsole-24.05.2/debian/konsole.install > konsole-24.08.0/debian/konsole.installdiff --git > a/konsole-24.05.2/debian/konsole.install > b/konsole-24.08.0/debian/konsole.install > index a7fe591e5bbb..970d0c685aca 100644 > --- a/konsole-24.05.2/debian/konsole.install > +++ b/konsole-24.08.0/debian/konsole.install > @@ -1,4 +1,4 @@ > -etc/xdg/konsolerc > +data/konsolerc etc/xdg/ > usr/bin/konsole > usr/bin/konsoleprofile > usr/lib/*/kconf_update_bin/konsole_globalaccel > @@ -11,7 +11,7 @@ usr/share/kconf_update/konsole.upd > usr/share/kconf_update/konsole_add_hamburgermenu_to_toolbar.sh > usr/share/kglobalaccel/org.kde.konsole.desktop > usr/share/kio/servicemenus/konsolerun.desktop > -usr/share/knsrcfiles/konsole.knsrc > +data/konsole.knsrc usr/share/knsrcfiles/ > usr/share/locale/ > usr/share/metainfo/org.kde.konsole.appdata.xml > usr/share/qlogging-categories6/konsole.categories > > git diff konsole-24.05.2/debian/konsole-kpart.install > konsole-24.08.0/debian/konsole-kpart.install > diff --git a/konsole-24.05.2/debian/konsole-kpart.install > b/konsole-24.08.0/debian/konsole-kpart.install > index 1fabd3891ee9..3eba7a3db304 100644 > --- a/konsole-24.05.2/debian/konsole-kpart.install > +++ b/konsole-24.08.0/debian/konsole-kpart.install > @@ -1,4 +1,6 @@ > usr/lib/*/libkonsoleprivate.so.* > usr/lib/*/qt6/plugins/kf6/parts/konsolepart.so > usr/share/knotifications6/ > -usr/share/konsole/ > +data/color-schemes/*.colorscheme usr/share/konsole/ > +data/keyboard-layouts/*.keytab usr/share/konsole/ > +data/layouts/*.json usr/share/konsole/ > > INFO: Missing files from from data source director
Building konsole version 24.08.0
Hi, yesterday someone asked for ktorrent from KDE/Apps version 24.08.0. Today, afternoon I played with NEW konsole. Here is my quick mini-howto. [ PREREQ ] INFO: You should have some experiences in Debian packaging. [ BUILD-DIR ] mkdir $HOME/src/konsole [ WGET ] wget http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2-1.dsc wget http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2-1.debian.tar.xz wget http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2.orig.tar.xz wget http://deb.debian.org/debian/pool/main/k/konsole/konsole_24.05.2.orig.tar.xz.asc wget -O konsole_24.08.0.orig.tar.xz https://download.kde.org/stable/release-service/24.08.0/src/konsole-24.08.0.tar.xz wget -O konsole_24.08.0.orig.tar.xz.asc https://download.kde.org/stable/release-service/24.08.0/src/konsole-24.08.0.tar.xz.sig [ STEAL DEBIAN-DIR ] dpkg-source -x *.dsc tar -xf konsole_24.08.0.orig.tar.xz cp -av konsole-24.05.2/debian konsole-24.08.0/ [ BUILDDEP - MANUALLY ] root# apt-get install -t experimental libkf6bookmarks-dev libkf6config-dev libkf6configwidgets-dev libkf6coreaddons-dev libkf6crash-dev libkf6dbusaddons-dev libkf6doctools-dev libkf6globalaccel-dev libkf6guiaddons-dev libkf6i18n-dev libkf6iconthemes-dev libkf6kio-dev libkf6newstuff-dev libkf6notifications-dev libkf6notifyconfig-dev libkf6parts-dev libkf6pty-dev libkf6service-dev libkf6textwidgets-dev libkf6widgetsaddons-dev libkf6windowsystem-dev libkf6xmlgui-dev qt6-5compat-dev/unstable qt6-multimedia-dev/unstable qt6-tools-dev/unstable qt6-wayland-dev/unstable qt6-declarative-dev/unstable libqt6core5compat6/unstable qt6-base-private-dev/unstable qt6-declarative-dev-tools/unstable qt6-qmllint-plugins/unstable qt6-qmltooling-plugins/unstable libqt6designercomponents6/unstable libqt6help6/unstable qt6-tools-dev-tools/unstable libkf6dbusaddons-dev/unstable INFO: QT-6 DEVEL packages from Debian/unstable. [ DCH ] export DEBFULLNAME="Sedat Dilek" export DEBEMAIL="sedat.di...@gmail.com" dch -i konsole (4:24.08.0-1~dileks) experimental; urgency=low * Non-maintainer upload. * New upstream release (24.08.0). * debian/konsole.install: - Copy data/konsolerc file to /etc/xdg/ directory - Copy data/konsole.knsrc file to /usr/share/knsrcfiles/ directory * debian/konsole-kpart.install: - Copy color-schemes, keyboard-layouts and layouts files from data/ to /usr/share/konsole/ directory -- Sedat Dilek Sat, 24 Aug 2024 15:21:34 +0200 konsole (4:24.05.2-1) experimental; urgency=medium ... [ DIFF ] git diff konsole-24.05.2/debian/konsole.install konsole-24.08.0/debian/konsole.installdiff --git a/konsole-24.05.2/debian/konsole.install b/konsole-24.08.0/debian/konsole.install index a7fe591e5bbb..970d0c685aca 100644 --- a/konsole-24.05.2/debian/konsole.install +++ b/konsole-24.08.0/debian/konsole.install @@ -1,4 +1,4 @@ -etc/xdg/konsolerc +data/konsolerc etc/xdg/ usr/bin/konsole usr/bin/konsoleprofile usr/lib/*/kconf_update_bin/konsole_globalaccel @@ -11,7 +11,7 @@ usr/share/kconf_update/konsole.upd usr/share/kconf_update/konsole_add_hamburgermenu_to_toolbar.sh usr/share/kglobalaccel/org.kde.konsole.desktop usr/share/kio/servicemenus/konsolerun.desktop -usr/share/knsrcfiles/konsole.knsrc +data/konsole.knsrc usr/share/knsrcfiles/ usr/share/locale/ usr/share/metainfo/org.kde.konsole.appdata.xml usr/share/qlogging-categories6/konsole.categories git diff konsole-24.05.2/debian/konsole-kpart.install konsole-24.08.0/debian/konsole-kpart.install diff --git a/konsole-24.05.2/debian/konsole-kpart.install b/konsole-24.08.0/debian/konsole-kpart.install index 1fabd3891ee9..3eba7a3db304 100644 --- a/konsole-24.05.2/debian/konsole-kpart.install +++ b/konsole-24.08.0/debian/konsole-kpart.install @@ -1,4 +1,6 @@ usr/lib/*/libkonsoleprivate.so.* usr/lib/*/qt6/plugins/kf6/parts/konsolepart.so usr/share/knotifications6/ -usr/share/konsole/ +data/color-schemes/*.colorscheme usr/share/konsole/ +data/keyboard-layouts/*.keytab usr/share/konsole/ +data/layouts/*.json usr/share/konsole/ INFO: Missing files from from data source directory (see above) were not in the search path of debuild. [ BUILD ] LC_ALL=C debuild [ INSTALL ] sudo dpkg -i konsole_24.08.0-1~dileks_amd64.deb konsole-kpart_24.08.0-1~dileks_amd64.deb -dileks // 24-Aug-2024 [ FILES ] LC_ALL=C ll total 28M drwxrwxr-x 2 dileks dileks 4.0K Aug 24 17:03 . drwxrwxr-x 4 dileks dileks 4.0K Aug 24 17:03 .. -rw-r--r-- 1 dileks dileks 5.0M Aug 24 16:36 konsole-dbgsym_24.08.0-1~dileks_amd64.deb -rw-r--r-- 1 dileks dileks 19M Aug 24 16:36 konsole-kpart-dbgsym_24.08.0-1~dileks_amd64.deb -rw-r--r-- 1 dileks dileks 700K Aug 24 16:36 konsole-kpart_24.08.0-1~dileks_amd64.deb -rw-r--r-- 1 dileks dileks 21K Aug 24 16:28 konsole_24.08.0-1~dileks.debian.tar.xz -rw-r--r-- 1 dileks dileks 2.3K Aug 24 16:28 konsole_24.08.0-1~dileks.dsc -rw-r--r-- 1 dileks dileks 1.2M Aug 24 16:36 konsole_24.08.0-1~dileks_amd64.build -rw-r--r-- 1 dilek
Re: Konsole with osc52
Thanks for the detailed explanation. On Tuesday, August 13, 2024 6:33:19 PM MST Shmerl wrote: > On Tue, 13 Aug 2024 18:05:22 -0700 Soren Stoutner wrote: > > *> I am guessing by your comments that Ctrl+Shift+C and Ctrl+Shift+V > doesn’t work* > *> for some reason.* > > Those shortctuts should work as usual. But the idea is to use editors that > integrate with system > clipboard in some way. I.e. if in neovim you use clipboard providers, you > can copy editor's own > selection into system clipboard instead of relying on terminal's selection. > It makes a difference in > how easy it's to do things. > > In case of local usage, neovim would rely on xsel or wl-copy to send text > to system clipboard, > but when you do it remotely over ssh, you either need to forward X, or find > some other ways. > > Without forwarding X (good for Wayland world), OSC52 is such mechanism. > OSC = operating system command [escape sequence]. > > It basically signals to the terminal through some special escape sequence, > that some portion > of text should be copied to the clipboard. And it works very neatly. > > Regards, > Shmerl. -- Soren Stoutner so...@debian.org signature.asc Description: This is a digitally signed message part.
Re: Konsole with osc52
On Tuesday, August 13, 2024 5:02:40 PM MST Shmerl wrote: > For those unfamiliar, the benefit of OSC52 support is the ability to copy > to clipboard from a terminal, > so even in Wayland session when you are doing ssh to some remote host, you > can copy to clipboard > from neovim running there or any editor that supports OSC52. That’s interesting. I don’t have personal experience with Wayland (will probably be switching soon) and neovim, but I am guessing by your comments that Ctrl+Shift+C and Ctrl+Shift+V doesn’t work for some reason. -- Soren Stoutner so...@debian.org signature.asc Description: This is a digitally signed message part.
Konsole with osc52
Now finally it's possible to enable OSC52 for Debian's konsole!
Since konsole 24.05.2 was packaged (thanks a lot of that!) you can apply
upstream changes
to use it.
See: https://invent.kde.org/utilities/konsole/-/merge_requests/767
That's not yet in 24.05.2 but I refactored the patchset to apply correctly
(see attached).
You need to rebuild konsole packages with those patches to use it.
For those unfamiliar, the benefit of OSC52 support is the ability to copy
to clipboard from a terminal,
so even in Wayland session when you are doing ssh to some remote host, you
can copy to clipboard
from neovim running there or any editor that supports OSC52.
It's really a major usability feature, so may be it's worth including this
in the official Debian patches
until it lands in the newer versions.
Have fun!
Shmerl.
--- a/src/Vt102Emulation.cpp
+++ b/src/Vt102Emulation.cpp
@@ -12,7 +12,9 @@
#include
// Qt
+#include
#include
+#include
#include
#include
#include
@@ -1153,6 +1155,43 @@
return;
}
+
+if (attribute == Clipboard) {
+// Clipboard
+QStringList params = value.split(QLatin1Char(';'));
+if (params.length() == 0) {
+return;
+}
+
+bool clipboard = false;
+bool selection = false;
+if (params[0].isEmpty() || params[0].contains(QLatin1Char('c')) || params[0].contains(QLatin1Char('s'))) {
+clipboard = true;
+}
+if (params[0].contains(QLatin1Char('p'))) {
+selection = true;
+}
+
+if (params.length() == 2) {
+// Copy to clipboard
+if (clipboard) {
+QApplication::clipboard()->setText(QString::fromUtf8(QByteArray::fromBase64(params[1].toUtf8())), QClipboard::Clipboard);
+}
+if (selection) {
+QApplication::clipboard()->setText(QString::fromUtf8(QByteArray::fromBase64(params[1].toUtf8())), QClipboard::Selection);
+}
+} else {
+// Clear clipboard
+if (clipboard) {
+QApplication::clipboard()->clear(QClipboard::Clipboard);
+}
+if (selection) {
+QApplication::clipboard()->clear(QClipboard::Selection);
+}
+}
+
+return;
+}
if (value == QLatin1String("?")) {
// pass terminator type indication here, because OSC response terminator
--- a/src/Vt102Emulation.h
+++ b/src/Vt102Emulation.h
@@ -126,7 +126,6 @@
void resetModes();
void resetTokenizer();
-#define MAX_TOKEN_LENGTH 256 // Max length of tokens (e.g. window title)
void addToCurrentToken(uint cc);
int tokenBufferPos;
@@ -183,6 +182,7 @@
enum osc {
// https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-Operating-System-Commands
ReportColors = 4,
+Clipboard = 52,
ResetColors = 104,
// https://gitlab.freedesktop.org/Per_Bothner/specifications/blob/master/proposals/semantic-prompts.md
SemanticPrompts = 133,
[Fixed with upgrade] Re: konsole disappeared permanently
Fixed after upgrade.
However there is one remaining thing that could be confusing:
with configure window manager - special application/window settings,
we now add/remove features.
When you remove a feature it does not default to a default behavior, it only
remove the handle to that behavior.
That was not how it behaved in the past.
And the new way, the way it is, cannot be good. For instance you can't resize
a window, but you don't know why.
On Tuesday, December 29, 2020 3:59:50 PM CET you wrote:
> Hi all,
>
> I've been meddling with konsole transparency through "configure special
> application settings - configure window manager".
>
> I've only introduced "active opacity" and "inactive opacity", set them to
> "force" and dial them to, say, 20%. Then apply.
>
> I was not satisfy by the result, as many people are, so I took step to
> "remove" the properties. And did apply.
>
> But then nothing changed. So I said to myself: maybe only the handle to the
> property is removed...
>
> So I reintroduced the properties, and set them to an intermediary position,
> and force again, and apply, and
>
> Ta-da, all konsole are vanished.
>
> Like you can't see anything of them, whatever you do. Like too much of the
> potion of the invisible man.
>
> Since the transparency settings were realistic I did a reboot. But konsole
> remained invisible.
>
> Newly opened console: invisible, no way to see where it is, or if it is
> there at all.
>
> Ctrl-F10 not showing them.
>
> But Alt-Tab do show them, in the side panel list, I mean. So you sort of can
> select them.
>
> And mouse-hover cursor is modified when above them. If the window is alone
> on the screen, you can differentiate it from the background.
>
> So I carefully managed to have the focus in one konsole, and pasted:
>
> `qdbus org.kde.KWin /Compositor suspend`
>
> phew!
>
> I don't even know if it is fixable.
>
> So temporarily no compositor. Too bad, I liked my compositor.
>
> Also, I had to un-tick "enable compositor on startup", otherwise, no more
> konsole on reboot.
>
> Note: settings are:
> Crisp,
> OpenGL 3.0
> Automatic (tearing prevention ("vsync")
> Only for shown windows
> Allow applications to block conposition (un-ticked)
>
> My system is "last week" sid; without the experimental plasma, just plain
> sid.
>
> Thanks,
> Chris
konsole disappeared permanently
Hi all,
I've been meddling with konsole transparency through "configure special
application settings - configure window manager".
I've only introduced "active opacity" and "inactive opacity", set them to
"force" and dial them to, say, 20%. Then apply.
I was not satisfy by the result, as many people are, so I took step to
"remove" the properties. And did apply.
But then nothing changed. So I said to myself: maybe only the handle to the
property is removed...
So I reintroduced the properties, and set them to an intermediary position,
and force again, and apply, and
Ta-da, all konsole are vanished.
Like you can't see anything of them, whatever you do. Like too much of the
potion of the invisible man.
Since the transparency settings were realistic I did a reboot. But konsole
remained invisible.
Newly opened console: invisible, no way to see where it is, or if it is there
at all.
Ctrl-F10 not showing them.
But Alt-Tab do show them, in the side panel list, I mean. So you sort of can
select them.
And mouse-hover cursor is modified when above them. If the window is alone on
the screen, you can differentiate it from the background.
So I carefully managed to have the focus in one konsole, and pasted:
`qdbus org.kde.KWin /Compositor suspend`
phew!
I don't even know if it is fixable.
So temporarily no compositor. Too bad, I liked my compositor.
Also, I had to un-tick "enable compositor on startup", otherwise, no more
konsole on reboot.
Note: settings are:
Crisp,
OpenGL 3.0
Automatic (tearing prevention ("vsync")
Only for shown windows
Allow applications to block conposition (un-ticked)
My system is "last week" sid; without the experimental plasma, just plain sid.
Thanks,
Chris
Re: konsole: Tiling support and version 20.04
On Thu, Jun 4, 2020 at 1:54 PM Sedat Dilek wrote: > What about konsole v20.04 in unstable / testing? > If I would build a Debian package by myself are there any suggestions? > Is something missing in unstable/testing why it was not realized? > Thanks, I enjoy konsole=4:20.04.2-1 with tiling-support in Debian/testing AMD64. - Sedat -
Re: konsole: Tiling support and version 20.04
On Thu, Jun 4, 2020 at 1:54 PM Sedat Dilek wrote: > > Hi, > > formerly, I used tilix. > > Now, I see konsole v19.08 here on Debian/testing AMD64 has "tiling" support. > > If I have tiled left+right in one "konsole-session/windows" - > so-to-say "2 terminal screens" at one view. > I wonder how I can maximize the left or right one with a keyboard shortcut. > F11 is maximizing the "konsole-session/windows" with both l+r terminals. > Is that supported what I want? > /me ashamed... Ctrl + Shift + E = Maximize current terminal ...works as desired. - Sedat -
konsole: Tiling support and version 20.04
Hi, formerly, I used tilix. Now, I see konsole v19.08 here on Debian/testing AMD64 has "tiling" support. If I have tiled left+right in one "konsole-session/windows" - so-to-say "2 terminal screens" at one view. I wonder how I can maximize the left or right one with a keyboard shortcut. F11 is maximizing the "konsole-session/windows" with both l+r terminals. Is that supported what I want? What about konsole v20.04 in unstable / testing? If I would build a Debian package by myself are there any suggestions? Is something missing in unstable/testing why it was not realized? Thanks. Regards, - Sedat -
Re: Change of behaviour for Konsole in Bullseye
On 19/09/09 10:32, Alex DEKKER wrote: > On 22/08/2019 19:57, Erwan David wrote: > > Hi, > > > > I use bullseye, and I found that konsole has changed behaviour regarding > > Views and tabd. > > Something else tab-related that seems to have changed, the text colour on > the tab no longer changes to indicate un-seen activity in the tab. Is this > intentional? Has it become optional? Yes, something odd is going on :-/
Re: Change of behaviour for Konsole in Bullseye
On 22/08/2019 19:57, Erwan David wrote: Hi, I use bullseye, and I found that konsole has changed behaviour regarding Views and tabd. Something else tab-related that seems to have changed, the text colour on the tab no longer changes to indicate un-seen activity in the tab. Is this intentional? Has it become optional? alexd
Re: KDE version numbering, (K)ubunt vs. Debian, was: Re: Konsole empty
rhkra...@gmail.com - 23.08.19, 15:40:07 CEST: > My puzzlement and the answer (afaict): I started to see version > numbers for KDE apps very different from what I am used to. I found > out that (at least apparently) KDE has changed their version > numbering scheme. (It now looks like (at least to me, at a quick > glance) like the version numbers used by (K)ubuntu but I'm not sure > whether the scheme is the same or not -- I'd tend to bet that it is. > I guess I've resolved my puzzlement. In basic there are two version numbering schemes: 1) YY.MM in lockstep with the KDE Applications release, for example 19.08 or 18.04. 2) An application specific version number. Now some applications like Konsole tend to use scheme 1 only – at least since Konsole 19.08: % konsole --version konsole 19.08.0 Others like the applications of KDEPIM use scheme 2. But as they are packaged with KDEPIM, both schemes are used. The upstream bug tracker https://bugs.kde.org however uses the application specific number. % kmail --version kmail2 5.9.3 If you like to find out the YY.MM one, in Debian you can ask package management: % LANG=en apt policy kmail | grep Installed […] Installed: 4:18.08.3-1 Both schemes have different advantages and disadvantages: 1) Same version number in all applications. Version numbers get bumped even without major changes. So a specific KDE application in KDE Applications 18.08 could be the same as in 19.08. 2) Different version numbers in different applications. Mixed with the YY.MM numbers it can lead to confusion. Application maintainers bump version numbers. That may indicate a change in the application or not. But theoretically version numbers could be more meaningful. This has been discussed upstream, but no clear conclusion has been found. Some application maintainers use only scheme 1 others use scheme 2, but release with the KDE Applications bundle, and deal with the possible confusion, still others release independently and may use scheme 1 or 2. Can it be confusing? Yes, it can. But by comparing "binary --version" versus information from package management you can get a clearer picture about a specific application. Well and then there is the versioning of KDE Frameworks and Plasma. KDE Frameworks currently is 5.n and they just add 1 to n with every release. Plasma is 5.x.y and they add one to x for every major release and one to y for bug fix releases. As for Jessie: This has still been Plasma 4 and KDE SC 4. I don't go into detail how that was numbered. It is again different. As far as I know there is nothing Debian or Ubuntu specific in there. Debian and Kubuntu developers use scheme 2 for KDE Application packages. And they use the official Plasma and KDE Frameworks version for their packages. AFAIK this is not different between Debian and Kubuntu although Kubuntu may have a newer version of packages at times, at least as Debian Stable, but sometimes also as Debian Unstable. Hope this summarizes it quite well. Best, -- Martin
KDE version numbering, (K)ubunt vs. Debian, was: Re: Konsole empty
Ok, had a question, found an answer by googling, was going to save this as a draft and maybe put a copy on askRhk, but I decided to post it to the list in case it helps anyone else. My puzzlement and the answer (afaict): I started to see version numbers for KDE apps very different from what I am used to. I found out that (at least apparently) KDE has changed their version numbering scheme. (It now looks like (at least to me, at a quick glance) like the version numbers used by (K)ubuntu but I'm not sure whether the scheme is the same or not -- I'd tend to bet that it is. I guess I've resolved my puzzlement. A link: * [[https://forum.kde.org/viewtopic.php?f=265&t=129043][newbie question about version numbers]] ` To my limited knowledge the Kdenlive developers adopted a new versioning scheme when they ported Kdenlive to the recent KDE Framework 5 (KF5). They are following the versioning scheme adopted by the KDE Project, in particular, YY.MM.p. YY is the year of the release. MM the month. Typically, there are only few major releases, two this year so far: 15.04 in April, 15.08 in August. These releases should being follow the KF5 releases, as Kdenlive is now part of the KDE 5 Applications. The third number p then indicates the patchlevel releases, that is, bug fix releases that happen from time to tome in between the larger KDE Applications releases. ' My attempt at drafting the question: On Friday, August 23, 2019 06:40:16 AM Martin Steigerwald wrote: > I had the idea that this issue might come due to Konsole 19.08 on an I am puzzled by the version number. (I think I asked a similar question before but, unless I missed something, I got no response.) Some data points (or not): * In my mind, 19.08 looks like a (K)Ubuntu version number * The most recent version of Debian that I actually use is Jessie, my daily user is Wheezy (I know), but in which konsole is: Version 2.8.4 Using KDE Development Platform 4.8.4 (4.8.4) On Jessie, it is 2.14.2 on 4.14.2 Have the KDE numbers really jumped to something like 19.08? (I looked up the bug listed in the previous email in this thread (the one to which I am replying) which was: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935031 There, I see: Found in version konsole/4:19.08.0-1
Re: Konsole empty
Please use plain text mails, no HTML. They clear text of it did not show proper quotes. Michal Bulik - 23.08.19, 09:48:41 CEST: > Michal Bulik - 22.08.19, 10:39:32 CEST: […] >> I have that to with Konsole 19.08. But when I open a new window >> directly it works. > Same here, new konsole windows work fine. Sorry for not testing this. > I've considered that there was konsole general problem and I've > switched to another terminal. I see. Thanks for confirming. > I first thought it was an update issue, i.e. Konsole 19.08 would have > problems to restore a session of an older Konsole version, but it > happened also with a Konsole 19.08 window saved with the session. I had the idea that this issue might come due to Konsole 19.08 on an older version of KDE Frameworks. Sometimes there are changes in applications that depend on newer versions of KDE Frameworks. So the issues may go away with a newer version of KDE Frameworks in Debian. I will add this idea to konsoles started with KDE are black first https://bugs.debian.org/935031 Thanks, -- Martin
Re: Konsole empty
Hi Martin, Hi Michal. Michal Bulik - 22.08.19, 10:39:32 CEST: I'm on bullseye and after the recent upgrades my konsole is empty : just a window with no possibility to enter the commands (cf the attached image). The version I have : ii konsole4:19.08.0-1 amd64X terminal emulator Is that with a Konsole that was directly started with the session? Yes, I confirm that the problem concerns Konsoles started with the session (saved from the previous session). I have that to with Konsole 19.08. But when I open a new window directly it works. Same here, new konsole windows work fine. Sorry for not testing this. I've considered that there was konsole general problem and I've switched to another terminal. I first thought it was an update issue, i.e. Konsole 19.08 would have problems to restore a session of an older Konsole version, but it happened also with a Konsole 19.08 window saved with the session. Best, Best regards Michal --
Re: Change of behaviour for Konsole in Bullseye
On 22/08/2019 19:57, Erwan David wrote: I use bullseye, and I found that konsole has changed behaviour regarding Views and tabd. The old behaviour when you asked for a plit view was to have a second frame with the tabs of the window in each frame. Now, when I split the view, current tab is kep on left, other tabs are hidden, a new terminal is started in right frame. I can confirm this. It is as if "Split View" has become "Split Tab", because that's what it does. alexd
Re: Konsole empty
On Thursday, August 22, 2019 8:55:27 PM CEST Martin Steigerwald wrote: > Hi Michal. > > Michal Bulik - 22.08.19, 10:39:32 CEST: > > I'm on bullseye and after the recent upgrades my konsole is empty : > > just a window with no possibility to enter the commands (cf the > > attached image). > > > > The version I have : > > > > ii konsole4:19.08.0-1 amd64X terminal emulator > > Is that with a Konsole that was directly started with the session? For me after the first reboot I had lost all Konsole tabs from the previous session, and instead had a blank window, similar to that in the picture posted in that thread. However after the next reboot the konsole session tabs were reopened as they should. I'd say it is related to bug 935031. C. > I have that to with Konsole 19.08. But when I open a new window directly > it works. > > I first thought it was an update issue, i.e. Konsole 19.08 would have > problems to restore a session of an older Konsole version, but it > happened also with a Konsole 19.08 window saved with the session. > > Best,
Change of behaviour for Konsole in Bullseye
Hi, I use bullseye, and I found that konsole has changed behaviour regarding Views and tabd. The old behaviour when you asked for a plit view was to have a second frame with the tabs of the window in each frame. Now, when I split the view, current tab is kep on left, other tabs are hidden, a new terminal is started in right frame. Is there a way to get back the old behaviour ? Thanks.
Re: Konsole empty
Hi Michal. Michal Bulik - 22.08.19, 10:39:32 CEST: > I'm on bullseye and after the recent upgrades my konsole is empty : > just a window with no possibility to enter the commands (cf the > attached image). > > The version I have : > > ii konsole4:19.08.0-1 amd64X terminal emulator Is that with a Konsole that was directly started with the session? I have that to with Konsole 19.08. But when I open a new window directly it works. I first thought it was an update issue, i.e. Konsole 19.08 would have problems to restore a session of an older Konsole version, but it happened also with a Konsole 19.08 window saved with the session. Best, -- Martin
Re: Konsole empty
Il 22/08/19 10:39, Michal Bulik ha scritto: Hi, I'm on bullseye and after the recent upgrades my konsole is empty : just a window with no possibility to enter the commands (cf the attached image). The version I have : ii konsole 4:19.08.0-1 amd64 X terminal emulator Thank you, Michal It does not seem to depend on the konsole version: -- $ dpkg -l| grep konsole ii konsole 4:19.08.0-1 amd64 X terminal emulator ii konsole-kpart 4:19.08.0-1 amd64 Konsole plugin for Qt applications -- No problem here with debian testing. Best, Luca.
Konsole empty
Hi, I'm on bullseye and after the recent upgrades my konsole is empty : just a window with no possibility to enter the commands (cf the attached image). The version I have : ii konsole 4:19.08.0-1 amd64 X terminal emulator Thank you, Michal
Re: Request for cherry-picking konsole: Support for ECMA-48 REP
On Mittwoch, 11. April 2018 21:17:55 CEST Miguel A. Vallejo wrote: > Same here. Everything is working again just fine. > > A big thank you! +1 A big thank you from my side! Frank
Re: Request for cherry-picking konsole: Support for ECMA-48 REP
Same here. Everything is working again just fine. A big thank you!
Re: Request for cherry-picking konsole: Support for ECMA-48 REP
Lisandro Damián Nicanor Pérez Meyer - 11.04.18, 13:55: > Maxy uploaded a patched version today. Dak is still with issues, so it > might take a while to get it. Its available already. atop works again also with TERM=xterm-256color. I will keep TERM=konsole-256color anyway. It reduced size of tabs, nice :). Thanks to Maxy. Plasma/Qt in Debian Sid is really nice at the moment. Thanks to everyone involved, Pino for kmymoney and a lot of application packages as well as calligra and krita, Lisandro and others involved for Qt, Maxy for frameworks and plasma packages, Scarlett for taking care of updating some packages to KF5 based upstream versions and all the others involved with uploading and preparing packages and testing stuff. It may very well be that I omitted someone. If so… its by accident, not by intention. Upstream is doing fine work, Debian Qt/KDE team members are doing fine work… thinks look good for the next Debian release so far. Thanks, -- Martin
Re: Request for cherry-picking konsole: Support for ECMA-48 REP
Maxyuploaded a patched version today. Dak is still with issues, so it might take a while to get it.
Re: Request for cherry-picking konsole: Support for ECMA-48 REP
Martin Steigerwald - 10.04.18, 22:57: > Martin Steigerwald - 10.04.18, 19:07: > > Miguel A. Vallejo - 09.04.18, 17:34: > > > Frank Mehnert wrote: > > > >>> Would it be possible to cherry-pick that change for the > > > >>> current > > > >>> konsole package in Sid? IMHO that would make sense as it fixes > > > >>> a bug which is now > > > >>> triggered with the ncurses update from 20170729. > > > > > > That would be nice. gpsmon and wavemon are also affected. > > > > As well as atop. > > > > I currently use qterminal or export TERM=linux in Konsole as a > > work-around. > > TERM=konsole or TERM=konsole-256color work as well as Maxy pointed out > on IRC. And you can edit / set TERM to konsole-256color in profile settings / environment variables. -- Martin
Re: Request for cherry-picking konsole: Support for ECMA-48 REP
Martin Steigerwald - 10.04.18, 19:07: > Miguel A. Vallejo - 09.04.18, 17:34: > > Frank Mehnert wrote: > > >>> Would it be possible to cherry-pick that change for the current > > >>> konsole package in Sid? IMHO that would make sense as it fixes > > >>> a bug which is now > > >>> triggered with the ncurses update from 20170729. > > > > That would be nice. gpsmon and wavemon are also affected. > > As well as atop. > > I currently use qterminal or export TERM=linux in Konsole as a > work-around. TERM=konsole or TERM=konsole-256color work as well as Maxy pointed out on IRC. -- Martin
Re: Request for cherry-picking konsole: Support for ECMA-48 REP
Miguel A. Vallejo - 09.04.18, 17:34: > Frank Mehnert wrote: > >>> Would it be possible to cherry-pick that change for the current konsole > >>> package in Sid? IMHO that would make sense as it fixes a bug which is > >>> now > >>> triggered with the ncurses update from 20170729. > > That would be nice. gpsmon and wavemon are also affected. As well as atop. I currently use qterminal or export TERM=linux in Konsole as a work-around. Thank you for researching the root cause of that issue, Frank. I did not bother to do it so far. Thanks, -- Martin
Re: Request for cherry-picking konsole: Support for ECMA-48 REP
Frank Mehnert wrote: >>> Would it be possible to cherry-pick that change for the current konsole >>> package in Sid? IMHO that would make sense as it fixes a bug which is now >>> triggered with the ncurses update from 20170729. That would be nice. gpsmon and wavemon are also affected.
Request for cherry-picking konsole: Support for ECMA-48 REP
Dear Debian KDE maintainers, since a few months ncurses screen output is kind of scrambled under certain conditions, for example when configuring the Linux kernel with 'make menuconfig'. The reason is missing support for ECMA-48 REP in konsole. See https://phabricator.kde.org/D10064 and corresponding commit b8a2f0cfd0d0f894687953c3f50f2fb163e8690d in konsole. Would it be possible to cherry-pick that change for the current konsole package in Sid? IMHO that would make sense as it fixes a bug which is now triggered with the ncurses update from 20170729. Thanks for your great work! Frank
Re: tmux and vim in konsole not display correctly
On Friday, 29 September 2017 10:44:30 CEST Sandro Knauß wrote: > Hey, > > i had an annoying issue for some time. If I start a vim inside a tmux inside > a konsole, the lines get corrupted, and i can't read anymore, if I jump > bigger chunks up/down in a document [#876362] > > As I learned from the bugreport the solution is easy: install konsole from > experimental (4:17.08.1-1): > apt install -t experimental konsole > [...] > The following packages will be upgraded: > kde-l10n-de konsole konsole-kpart > [...] > > Be aware, this fix may introduce strange translation bugs (aka more > untransalted strings) in the German desktop for a while... Because now you > have a system mostly 16.12.0 but the translations are 17.08.1. You should have the transaltions for Plasma and Frameworks, and all translations for programs part of KDE Applications >= 17.04, which include the translations in the each tarball (and then package): https://community.kde.org/Applications/17.04_Release_Notes#Translations This will be solved as soon as most programs part of KDE Applications are updated to newer versions. -- Luigi
tmux and vim in konsole not display correctly
Hey, i had an annoying issue for some time. If I start a vim inside a tmux inside a konsole, the lines get corrupted, and i can't read anymore, if I jump bigger chunks up/down in a document [#876362] As I learned from the bugreport the solution is easy: install konsole from experimental (4:17.08.1-1): apt install -t experimental konsole [...] The following packages will be upgraded: kde-l10n-de konsole konsole-kpart [...] Be aware, this fix may introduce strange translation bugs (aka more untransalted strings) in the German desktop for a while... Because now you have a system mostly 16.12.0 but the translations are 17.08.1. Best regards, hefee [#876362] https://bugs.debian.org/876362 signature.asc Description: This is a digitally signed message part.
Re: konsole --version crashes
On Mon, Jan 2, 2017 at 2:55 AM, Dmitry Shachnev wrote: > Hi Kamaraju! > > On Sun, Jan 01, 2017 at 04:15:54PM -0500, kamaraju kusumanchi wrote: >> > Thiago says that integration for these patches is likely to fail, so I want >> > to wait until the integration results first. Either the patches are OK and >> > they are applied upstream, or we get to know which bugs they have. >> >> Thanks Dmitry. What you mean by integration results? When do you >> expect to get it? Assuming that everything checks out with the >> patches, do you think the bug will be fixed in the next stable release >> when stretch is released? > > I mean the continuous integration on Qt Gerrit (which runs the build and > auto tests on different platforms). > > The status of https://codereview.qt-project.org/180231 and 232 is STAGED, > which means the integration is scheduled. I guess it should be run soon > as the EU holidays have ended. > > And yes, I hope we will have this fix in Stretch. Ok. Thanks for the explanation. I am experiencing a crash in korganizer as well. The backtrace looks very similar to the crash in konsole --version. I reported this in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849890 . Please merge it with 849877 if you feel they are one and the same. raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
Hi Kamaraju! On Sun, Jan 01, 2017 at 04:15:54PM -0500, kamaraju kusumanchi wrote: > > Thiago says that integration for these patches is likely to fail, so I want > > to wait until the integration results first. Either the patches are OK and > > they are applied upstream, or we get to know which bugs they have. > > Thanks Dmitry. What you mean by integration results? When do you > expect to get it? Assuming that everything checks out with the > patches, do you think the bug will be fixed in the next stable release > when stretch is released? I mean the continuous integration on Qt Gerrit (which runs the build and auto tests on different platforms). The status of https://codereview.qt-project.org/180231 and 232 is STAGED, which means the integration is scheduled. I guess it should be run soon as the EU holidays have ended. And yes, I hope we will have this fix in Stretch. -- Dmitry Shachnev signature.asc Description: PGP signature
Re: konsole --version crashes
On Sat, Dec 31, 2016 at 7:47 AM, Martin Steigerwald wrote: > Am Freitag, 30. Dezember 2016, 17:39:21 CET schrieb kamaraju kusumanchi: >> On Fri, Dec 30, 2016 at 8:57 AM, Luigi Toscano > wrote: >> > I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few >> > race conditions which requires some (unmerged) patches (unmerged because >> > they cause regression on windows), quoting: >> > "https://codereview.qt-project.org/180231 and 232 at least" >> > >> > They are not apparently applied to the Qt packages in Debian. >> >> Thanks Luigi. >> >> What would be the next steps? Is it possible to include those two >> patches in the Debian then? > > Both Lisandro and Mitya are in Cc of this mail already, so they are aware. You > could create a bug report to ask for the inclusion of these patches in order > to help that it doesn´t get lost. Or ping them on #debian-qt-kde IRC channel. Thanks Martin. I reported the bug at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849877 so it does not get lost. Also, I noticed something since I originally reported the issue here. When konsole crashes, some times it opens up the popup window with the backtrace and some times it does not. The backtrace from the popup window contains more information. You can find both backtraces in the bug report. raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
On Sat, Dec 31, 2016 at 10:45 AM, Dmitry Shachnev wrote: > Hi all, > > On Sat, Dec 31, 2016 at 01:47:04PM +0100, Martin Steigerwald wrote: >> Am Freitag, 30. Dezember 2016, 17:39:21 CET schrieb kamaraju kusumanchi: >> > On Fri, Dec 30, 2016 at 8:57 AM, Luigi Toscano >> > wrote: >> > > I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few >> > > race conditions which requires some (unmerged) patches (unmerged because >> > > they cause regression on windows), quoting: >> > > "https://codereview.qt-project.org/180231 and 232 at least" >> > > >> > > They are not apparently applied to the Qt packages in Debian. >> > >> > Thanks Luigi. >> > >> > What would be the next steps? Is it possible to include those two >> > patches in the Debian then? >> >> Both Lisandro and Mitya are in Cc of this mail already, so they are aware. >> You >> could create a bug report to ask for the inclusion of these patches in order >> to help that it doesn´t get lost. Or ping them on #debian-qt-kde IRC channel. > > Thiago says that integration for these patches is likely to fail, so I want > to wait until the integration results first. Either the patches are OK and > they are applied upstream, or we get to know which bugs they have. Thanks Dmitry. What you mean by integration results? When do you expect to get it? Assuming that everything checks out with the patches, do you think the bug will be fixed in the next stable release when stretch is released? raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
Hi all, On Sat, Dec 31, 2016 at 01:47:04PM +0100, Martin Steigerwald wrote: > Am Freitag, 30. Dezember 2016, 17:39:21 CET schrieb kamaraju kusumanchi: > > On Fri, Dec 30, 2016 at 8:57 AM, Luigi Toscano > > wrote: > > > I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few > > > race conditions which requires some (unmerged) patches (unmerged because > > > they cause regression on windows), quoting: > > > "https://codereview.qt-project.org/180231 and 232 at least" > > > > > > They are not apparently applied to the Qt packages in Debian. > > > > Thanks Luigi. > > > > What would be the next steps? Is it possible to include those two > > patches in the Debian then? > > Both Lisandro and Mitya are in Cc of this mail already, so they are aware. > You > could create a bug report to ask for the inclusion of these patches in order > to help that it doesn´t get lost. Or ping them on #debian-qt-kde IRC channel. Thiago says that integration for these patches is likely to fail, so I want to wait until the integration results first. Either the patches are OK and they are applied upstream, or we get to know which bugs they have. -- Dmitry Shachnev signature.asc Description: PGP signature
Re: konsole --version crashes
Am Freitag, 30. Dezember 2016, 17:39:21 CET schrieb kamaraju kusumanchi: > On Fri, Dec 30, 2016 at 8:57 AM, Luigi Toscano wrote: > > I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few > > race conditions which requires some (unmerged) patches (unmerged because > > they cause regression on windows), quoting: > > "https://codereview.qt-project.org/180231 and 232 at least" > > > > They are not apparently applied to the Qt packages in Debian. > > Thanks Luigi. > > What would be the next steps? Is it possible to include those two > patches in the Debian then? Both Lisandro and Mitya are in Cc of this mail already, so they are aware. You could create a bug report to ask for the inclusion of these patches in order to help that it doesn´t get lost. Or ping them on #debian-qt-kde IRC channel. Thanks, -- Martin
Re: konsole --version crashes
On Fri, Dec 30, 2016 at 8:57 AM, Luigi Toscano wrote: > > I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few race > conditions which requires some (unmerged) patches (unmerged because they cause > regression on windows), quoting: > "https://codereview.qt-project.org/180231 and 232 at least" > > They are not apparently applied to the Qt packages in Debian. Thanks Luigi. What would be the next steps? Is it possible to include those two patches in the Debian then? raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
kamaraju kusumanchi ha scritto: > On Thu, Dec 29, 2016 at 7:25 AM, Luigi Toscano > wrote: >> >> When the backtrace starts, do you get the prompt of (gdb) again? > > Yes. I get the prompt of (gdb) again. > >> Try to type: >> >> (gdb) thread apply all backtrace >> >> and see if it gives you more output. > > The output looks pretty much the same even with this command. > > % gdb konsole > ... > Reading symbols from konsole...Reading symbols from > /usr/lib/debug/.build-id/2b/559c27a0259b9f5254ac6482a73ecd5f0fce6a.debug...done. > done. > (gdb) set args --version > (gdb) thread apply all backtrace > (gdb) r > Starting program: /usr/bin/konsole --version > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffe414b700 (LWP 9523)] > [New Thread 0x7fffe2268700 (LWP 9524)] > konsole 16.08.2 > > Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fffe2268700 (LWP 9524)] > 0x744b03ef in QObject::disconnect (sender=0x557d7d90, > signal=signal@entry=0x0, > receiver=receiver@entry=0x7fffd40030f0, method=method@entry=0x0) > at kernel/qobject.cpp:2956 > 2956kernel/qobject.cpp: No such file or directory. > (gdb) bt > #0 0x744b03ef in QObject::disconnect (sender=0x557d7d90, > signal=signal@entry=0x0, > receiver=receiver@entry=0x7fffd40030f0, method=method@entry=0x0) > at kernel/qobject.cpp:2956 > #1 0x77edfd50 in QObject::disconnect (member=0x0, > receiver=0x7fffd40030f0, this=) > at ../../include/QtCore/../../src/corelib/kernel/qobject.h:336 > #2 QDBusConnectionPrivate::closeConnection > (this=this@entry=0x7fffd40030f0) at qdbusintegrator.cpp:1145 > #3 0x77ecc7e2 in QDBusConnectionManager::run ( > this=0x77f41d60 <(anonymous > namespace)::Q_QGS__q_manager::innerFunction()::holder>) at > qdbusconnection.cpp:188 > #4 0x742b0da8 in QThreadPrivate::start ( > arg=0x77f41d60 <(anonymous > namespace)::Q_QGS__q_manager::innerFunction()::holder>) at > thread/qthread_unix.cpp:368 > #5 0x70b16464 in start_thread (arg=0x7fffe2268700) at > pthread_create.c:333 > #6 0x778dd9df in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few race conditions which requires some (unmerged) patches (unmerged because they cause regression on windows), quoting: "https://codereview.qt-project.org/180231 and 232 at least" They are not apparently applied to the Qt packages in Debian. Ciao -- Luigi > > >> Just to be sure: did you restart after the last updates (not only kernel, >> also >> Qt)? > > I did not do that before. But now I rebooted the computer and the > backtrace above is what I get after the reboot. > > thanks > raju >
Re: konsole --version crashes
On Thu, Dec 29, 2016 at 7:25 AM, Luigi Toscano wrote: > > When the backtrace starts, do you get the prompt of (gdb) again? Yes. I get the prompt of (gdb) again. > Try to type: > > (gdb) thread apply all backtrace > > and see if it gives you more output. The output looks pretty much the same even with this command. % gdb konsole ... Reading symbols from konsole...Reading symbols from /usr/lib/debug/.build-id/2b/559c27a0259b9f5254ac6482a73ecd5f0fce6a.debug...done. done. (gdb) set args --version (gdb) thread apply all backtrace (gdb) r Starting program: /usr/bin/konsole --version [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe414b700 (LWP 9523)] [New Thread 0x7fffe2268700 (LWP 9524)] konsole 16.08.2 Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe2268700 (LWP 9524)] 0x744b03ef in QObject::disconnect (sender=0x557d7d90, signal=signal@entry=0x0, receiver=receiver@entry=0x7fffd40030f0, method=method@entry=0x0) at kernel/qobject.cpp:2956 2956kernel/qobject.cpp: No such file or directory. (gdb) bt #0 0x744b03ef in QObject::disconnect (sender=0x557d7d90, signal=signal@entry=0x0, receiver=receiver@entry=0x7fffd40030f0, method=method@entry=0x0) at kernel/qobject.cpp:2956 #1 0x77edfd50 in QObject::disconnect (member=0x0, receiver=0x7fffd40030f0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:336 #2 QDBusConnectionPrivate::closeConnection (this=this@entry=0x7fffd40030f0) at qdbusintegrator.cpp:1145 #3 0x77ecc7e2 in QDBusConnectionManager::run ( this=0x77f41d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:188 #4 0x742b0da8 in QThreadPrivate::start ( arg=0x77f41d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #5 0x70b16464 in start_thread (arg=0x7fffe2268700) at pthread_create.c:333 #6 0x778dd9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 > Just to be sure: did you restart after the last updates (not only kernel, also > Qt)? I did not do that before. But now I rebooted the computer and the backtrace above is what I get after the reboot. thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
kamaraju kusumanchi ha scritto: > On Thu, Dec 29, 2016 at 2:00 AM, Andrey Rahmatullin wrote: >> On Thu, Dec 29, 2016 at 11:59:07AM +0500, Andrey Rahmatullin wrote: >>> On Thu, Dec 29, 2016 at 01:52:20AM -0500, kamaraju kusumanchi wrote: >>>> Is the above link up to date? I ask because >>>> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian >>>> says that there are -dbg packages that I should install to get >>>> backtrace. But I do not see any packages such as konsole-dbg or >>>> libqt5dbus5-dbg in the archive. >>> They are now konsole-dbgsym and libqt5dbus5-dbgsym. For other packages the >>> names may differ. >> You also need to enable the debug repo, see >> https://wiki.debian.org/AutomaticDebugPackages > > Thanks. Just for the record, I also found > https://wiki.debian.org/HowToGetABacktrace to be useful for this > exercise. Here is the backtrace with all the symbols. > > > % gdb konsole > ... > Reading symbols from konsole...Reading symbols from > /usr/lib/debug/.build-id/2b/559c27a0259b9f5254ac6482a73ecd5f0fce6a.debug...done. > done. > (gdb) set args --version > (gdb) r > Starting program: /usr/bin/konsole --version > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffe414b700 (LWP 23997)] > [New Thread 0x7fffe2268700 (LWP 23998)] > konsole 16.08.2 > When the backtrace starts, do you get the prompt of (gdb) again? Try to type: (gdb) thread apply all backtrace and see if it gives you more output. Just to be sure: did you restart after the last updates (not only kernel, also Qt)? -- Luigi
Re: konsole --version crashes
On Thu, Dec 29, 2016 at 2:00 AM, Andrey Rahmatullin wrote: > On Thu, Dec 29, 2016 at 11:59:07AM +0500, Andrey Rahmatullin wrote: >> On Thu, Dec 29, 2016 at 01:52:20AM -0500, kamaraju kusumanchi wrote: >> > Is the above link up to date? I ask because >> > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian >> > says that there are -dbg packages that I should install to get >> > backtrace. But I do not see any packages such as konsole-dbg or >> > libqt5dbus5-dbg in the archive. >> They are now konsole-dbgsym and libqt5dbus5-dbgsym. For other packages the >> names may differ. > You also need to enable the debug repo, see > https://wiki.debian.org/AutomaticDebugPackages Thanks. Just for the record, I also found https://wiki.debian.org/HowToGetABacktrace to be useful for this exercise. Here is the backtrace with all the symbols. % gdb konsole ... Reading symbols from konsole...Reading symbols from /usr/lib/debug/.build-id/2b/559c27a0259b9f5254ac6482a73ecd5f0fce6a.debug...done. done. (gdb) set args --version (gdb) r Starting program: /usr/bin/konsole --version [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe414b700 (LWP 23997)] [New Thread 0x7fffe2268700 (LWP 23998)] konsole 16.08.2 Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe2268700 (LWP 23998)] 0x744b03ef in QObject::disconnect (sender=0x557d31c0, signal=signal@entry=0x0, receiver=receiver@entry=0x7fffd40030f0, method=method@entry=0x0) at kernel/qobject.cpp:2956 2956kernel/qobject.cpp: No such file or directory. (gdb) bt #0 0x744b03ef in QObject::disconnect (sender=0x557d31c0, signal=signal@entry=0x0, receiver=receiver@entry=0x7fffd40030f0, method=method@entry=0x0) at kernel/qobject.cpp:2956 #1 0x77edfd50 in QObject::disconnect (member=0x0, receiver=0x7fffd40030f0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:336 #2 QDBusConnectionPrivate::closeConnection (this=this@entry=0x7fffd40030f0) at qdbusintegrator.cpp:1145 #3 0x77ecc7e2 in QDBusConnectionManager::run ( this=0x77f41d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:188 #4 0x742b0da8 in QThreadPrivate::start ( arg=0x77f41d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #5 0x70b16464 in start_thread (arg=0x7fffe2268700) at pthread_create.c:333 #6 0x778dd9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
On Thu, Dec 29, 2016 at 11:59:07AM +0500, Andrey Rahmatullin wrote: > On Thu, Dec 29, 2016 at 01:52:20AM -0500, kamaraju kusumanchi wrote: > > Is the above link up to date? I ask because > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian > > says that there are -dbg packages that I should install to get > > backtrace. But I do not see any packages such as konsole-dbg or > > libqt5dbus5-dbg in the archive. > They are now konsole-dbgsym and libqt5dbus5-dbgsym. For other packages the > names may differ. You also need to enable the debug repo, see https://wiki.debian.org/AutomaticDebugPackages -- WBR, wRAR signature.asc Description: PGP signature
Re: konsole --version crashes
On Thu, Dec 29, 2016 at 01:52:20AM -0500, kamaraju kusumanchi wrote: > Is the above link up to date? I ask because > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian > says that there are -dbg packages that I should install to get > backtrace. But I do not see any packages such as konsole-dbg or > libqt5dbus5-dbg in the archive. They are now konsole-dbgsym and libqt5dbus5-dbgsym. For other packages the names may differ. -- WBR, wRAR signature.asc Description: PGP signature
Re: konsole --version crashes
On Wed, Dec 28, 2016 at 3:29 PM, Luigi Toscano wrote: > Do you see drkonqui starting? You should see the windows with the crash > information (including the stack trace); without that information there is no > much that we can do. > > If the window does not appear, you can try to run konsole, dolphin or any > other crashing application using gdb and extract the stacktrace: > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_with_GDB > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Is the above link up to date? I ask because https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian says that there are -dbg packages that I should install to get backtrace. But I do not see any packages such as konsole-dbg or libqt5dbus5-dbg in the archive. % sudo apt-get install libqt5dbus5-dbg Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libqt5dbus5-dbg % sudo apt-get install konsole-dbg Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package konsole-dbg I was able to get the following backtrace from gdb. But because the symbols are missing, I think it is pretty useless % gdb konsole ... Reading symbols from konsole...(no debugging symbols found)...done. (gdb) set args --version (gdb) r Starting program: /usr/bin/konsole --version [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe414b700 (LWP 21689)] [New Thread 0x7fffe2268700 (LWP 21690)] konsole 16.08.2 Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe2268700 (LWP 21690)] 0x744b03ef in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 (gdb) bt #0 0x744b03ef in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x77edfd50 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #2 0x77ecc7e2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #3 0x742b0da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x70b16464 in start_thread (arg=0x7fffe2268700) at pthread_create.c:333 #5 0x778dd9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
On Wed, Dec 28, 2016 at 3:29 PM, Luigi Toscano wrote: > > Do you see drkonqui starting? You should see the windows with the crash > information (including the stack trace); without that information there is no > much that we can do. > > If the window does not appear, you can try to run konsole, dolphin or any > other crashing application using gdb and extract the stacktrace: No, there is no other window that opens up when it crashes. BTW konsole and dolphin run fine. They only crash when I add the --version option. > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_with_GDB > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks. I will go through them and see what I can do. thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
kamaraju kusumanchi ha scritto: > On Wed, Dec 28, 2016 at 2:36 PM, solitone wrote: >> On Wednesday, December 28, 2016 10:09:18 PM CET Andrey Rahmatullin wrote: >>> On Wed, Dec 28, 2016 at 12:05:43PM -0500, kamaraju kusumanchi wrote: >>>> Can someone reproduce the problem in testing and/or know how to fix it? >>> >>> Works for me on testing. >> >> Works also for me: >> >> solitone@alan:~$ konsole --version >> konsole 16.08.2 > > Thanks Andrey and solitone. I guess I am the chosen one ;) Any ideas > how to narrow down the problem? I get this crash with dolphin > --version. But not with konqueror --version. The available version of Konqueror is still kdelibs4 (Qt4) based. > > % dolphin --version > dolphin 16.08.2 > KCrash: crashing... crashRecursionCounter = 2 > KCrash: Application Name = dolphin path = /usr/bin pid = 12741 > KCrash: Arguments: /usr/bin/dolphin --version > KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi > from kdeinit > sock_file=/run/user/1000/kdeinit5__0 > zsh: suspended (signal) dolphin --version Do you see drkonqui starting? You should see the windows with the crash information (including the stack trace); without that information there is no much that we can do. If the window does not appear, you can try to run konsole, dolphin or any other crashing application using gdb and extract the stacktrace: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_with_GDB https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- Luigi
Re: konsole --version crashes
On Wed, Dec 28, 2016 at 03:18:56PM -0500, kamaraju kusumanchi wrote: > Thanks Andrey and solitone. I guess I am the chosen one ;) Any ideas > how to narrow down the problem? Debug the crash. -- WBR, wRAR signature.asc Description: PGP signature
Re: konsole --version crashes
On Wed, Dec 28, 2016 at 2:36 PM, solitone wrote: > On Wednesday, December 28, 2016 10:09:18 PM CET Andrey Rahmatullin wrote: >> On Wed, Dec 28, 2016 at 12:05:43PM -0500, kamaraju kusumanchi wrote: >> > Can someone reproduce the problem in testing and/or know how to fix it? >> >> Works for me on testing. > > Works also for me: > > solitone@alan:~$ konsole --version > konsole 16.08.2 Thanks Andrey and solitone. I guess I am the chosen one ;) Any ideas how to narrow down the problem? I get this crash with dolphin --version. But not with konqueror --version. % dolphin --version dolphin 16.08.2 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = dolphin path = /usr/bin pid = 12741 KCrash: Arguments: /usr/bin/dolphin --version KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 zsh: suspended (signal) dolphin --version % konqueror --version Qt: 4.8.7 KDE Development Platform: 4.14.26 Konqueror: 4.14.25 -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
On Wednesday, December 28, 2016 10:09:18 PM CET Andrey Rahmatullin wrote: > On Wed, Dec 28, 2016 at 12:05:43PM -0500, kamaraju kusumanchi wrote: > > Can someone reproduce the problem in testing and/or know how to fix it? > > Works for me on testing. Works also for me: solitone@alan:~$ konsole --version konsole 16.08.2
Re: konsole --version crashes
On Wed, Dec 28, 2016 at 12:05:43PM -0500, kamaraju kusumanchi wrote: > Can someone reproduce the problem in testing and/or know how to fix it? Works for me on testing. -- WBR, wRAR signature.asc Description: PGP signature
Re: konsole --version crashes
On Wed, Dec 28, 2016 at 9:44 AM, laurent Trinques wrote: > Hello, > > I use and prefer yakuake, but I see no problem with konsole in unstable, > please wait. > > ~$ konsole --version > konsole 16.12.0 Thanks Laurent. That is a good data point to have. I prefer to stick with konsole as I am used to it and do not have time to learn a new emulator. Can someone reproduce the problem in testing and/or know how to fix it? thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: konsole --version crashes
Le mercredi 28 décembre 2016, 00:20:32 CET kamaraju kusumanchi a écrit : > When I run "konsole --version", it crashes with the following errors > > rajulocal@hogwarts ~ % konsole --version > konsole 16.08.2 > KCrash: crashing... crashRecursionCounter = 2 > KCrash: Application Name = konsole path = /usr/bin pid = 30084 > KCrash: Arguments: /usr/bin/konsole --version > KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi > from kdeinit > sock_file=/run/user/1000/kdeinit5__0 > zsh: suspended (signal) konsole --version > > I am running Debian Testing with all packages up to date. > > rajulocal@hogwarts ~ % dpkg -l konsole > Desired=Unknown/Install/Remove/Purge/Hold > > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pe > | nd| > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > | > ||/ Name VersionArchitecture > ||Description > +++-==-==-======-=== > == ii konsole > 4:16.08.2-2amd64 X terminal emulator > rajulocal@hogwarts ~ % uname -a > Linux hogwarts 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) > x86_64 GNU/Linux > > Can anyone reproduce it? Does the problem exist in unstable? Any ideas > on how to fix it? > > thanks > raju Hello, I use and prefer yakuake, but I see no problem with konsole in unstable, please wait. ~$ konsole --version konsole 16.12.0 Laurent
konsole --version crashes
When I run "konsole --version", it crashes with the following errors rajulocal@hogwarts ~ % konsole --version konsole 16.08.2 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = konsole path = /usr/bin pid = 30084 KCrash: Arguments: /usr/bin/konsole --version KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 zsh: suspended (signal) konsole --version I am running Debian Testing with all packages up to date. rajulocal@hogwarts ~ % dpkg -l konsole Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-==-= ii konsole4:16.08.2-2amd64 X terminal emulator rajulocal@hogwarts ~ % uname -a Linux hogwarts 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) x86_64 GNU/Linux Can anyone reproduce it? Does the problem exist in unstable? Any ideas on how to fix it? thanks raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: unicode / utf-8 characters displayed incorrectly in konsole
On Thursday, 30 June 2016 17:40:00 CEST Arthur Marsh wrote: > When I set each tab's encoding to Unicode/utf-8 characters displayed > correctly. > > also the > > output of: > > set | egrep -a '^(LC_|LANG)' > > Could be of use. > That gives me: > LANG=en_AU.UTF-8 Mmh, and that locale is being generated, right? Using: grep -v '^#' /etc/locale.gen Should tell you which locales are being generated. I would suggest to run: dpkg-reconfigure locales as root, just to be sure that the locales are correctly generated. About the default character encoding in konsole, when you edit a profile, in the advanced tab you can change the encoding to use for this profile, Default means "don't change the current value", so if you set it to latin1 and then back to Default it stays as latin1. Happy hacking, -- "Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live." -- John Woods Saludos /\/\ /\ >< `/ signature.asc Description: This is a digitally signed message part.
Re: unicode / utf-8 characters displayed incorrectly in konsole
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 lost the display of unicode/utf-8 characters in konsole, instead seeing the diamond with a question mark in it. If I try to use mozc to input Japanese text, the result displays as plain question marks. Any suggestions on where to look/what to try? Copy and pasting random japanese characters seem to work fine here. Could you please check if konsole is using Unicode? (Right click set encoding), It had been set to "default". I thought that the default encoding inherited from KDE would be Unicode/utf-8? When I set each tab's encoding to Unicode/utf-8 characters displayed correctly. also the output of: set | egrep -a '^(LC_|LANG)' Could be of use. That gives me: LANG=en_AU.UTF-8 Also, it might be worth testing a different font. Dejavu Sans Mono is probably the most complete font available, so start with that one. Other fonts rely on the fontconfig fallbacks to produce the characters that are not defined. Happy hacking, Thanks very much for the help and suggestions. I've also replaced the PS/2 mouse with a USB mouse that identifies itself as: Bus 003 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse having discovered some error messages about loss of synchronisation with the PS/2 mouse. I'll update the bug report in a few minutes.
unicode / utf-8 characters displayed incorrectly in konsole
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 mark in it. If I try to use mozc to input Japanese text, the result displays as plain question marks. If I start an xterm session, that xterm session displays the characters correctly and I can input Japanese text find with mozc. Any suggestions on where to look/what to try? Arthur.
Re: Do you have Konsole session restored?
On Thursday, June 23, 2016 15:19:25 Martin Steigerwald wrote: > Am Donnerstag, 23. Juni 2016, 15:06:32 CEST schrieb inkbottle: > > On Thursday, June 23, 2016 12:13:57 Martin Steigerwald wrote: > > > Am Donnerstag, 23. Juni 2016, 00:31:04 CEST schrieb inkbottle: > > > > Hi, > > > > I have received comments from this bug: > > > > https://bugs.kde.org/show_bug.cgi?id=343518 > > > > As I said there, on my side, Konsole is never restored. > > > > Is it restored to you, was it restored 1 month ago? > > > > My system might be different from yours since I follow stretch and not > > > > sid. > > > > > > Session management has been a mess for me since quite some time. > > > > > > It just doesn´t work consistenly. KMail, konsole, and others all gone > > > when > > > logging out and logging in again. On the other hand a Konqueror window > > > with > > > an opened webpage reappeared every time. > > > > > > I have set it to restore the old windows, but I seriously consider just > > > setting it to start an empty session for now. > > > > > > I never took the time to check for upstream bug reports about this. For > > > me > > > it is not just that some applications are not restored, most of them > > > aren´t. > > > > I've been interested first in this session restoring thing because I > > needed > > to have my Okular documents restored. > > At the present, I have everything restored, systematically, save Konsole, > > so I only have to memorise what directory I was in, which is not too > > hard. Everything is: Okular, Dolphin, Kmail, Konversation, Chromium... > > Hmmm, on todays reboot after lots more updated KF and Plasma packages I > found that Konsole opened again just fine, including the tabs and their > directories. So maybe something fixed… Hopefully I'll have similar results in 5 days or so (lag between unstable and testing, I believe); I'll tell you then. Chris > > > Thanks for your feedback, > > Chris > > (DIY session management for Okular: > > find ~/.kde/share/apps/okular/docdata/ -cmin -100 -type f -print0|xargs -0 > > cat| grep ' > Okular is keeping very good track of what it's doing, and I'm very > > *thankful* for that, and I hope it will keep storing these data in plain > > text format in handy location. > > One can't count on "fuser" to know what documents are used by Okular, > > because I guess that if the document is not in pdf format, it is converted > > to this in some temporary file that I haven't been able to find, and the > > original file is not listed by fuser.) > > Yeah, I like it when I hold a Linux training that on next time opening a PDF > it opens it at the page where I left it. > > Thanks,
Re: Do you have Konsole session restored?
Am Donnerstag, 23. Juni 2016, 15:06:32 CEST schrieb inkbottle: > On Thursday, June 23, 2016 12:13:57 Martin Steigerwald wrote: > > Am Donnerstag, 23. Juni 2016, 00:31:04 CEST schrieb inkbottle: > > > Hi, > > > I have received comments from this bug: > > > https://bugs.kde.org/show_bug.cgi?id=343518 > > > As I said there, on my side, Konsole is never restored. > > > Is it restored to you, was it restored 1 month ago? > > > My system might be different from yours since I follow stretch and not > > > sid. > > > > Session management has been a mess for me since quite some time. > > > > It just doesn´t work consistenly. KMail, konsole, and others all gone when > > logging out and logging in again. On the other hand a Konqueror window > > with > > an opened webpage reappeared every time. > > > > I have set it to restore the old windows, but I seriously consider just > > setting it to start an empty session for now. > > > > I never took the time to check for upstream bug reports about this. For me > > it is not just that some applications are not restored, most of them > > aren´t. > > I've been interested first in this session restoring thing because I needed > to have my Okular documents restored. > At the present, I have everything restored, systematically, save Konsole, so > I only have to memorise what directory I was in, which is not too hard. > Everything is: Okular, Dolphin, Kmail, Konversation, Chromium... Hmmm, on todays reboot after lots more updated KF and Plasma packages I found that Konsole opened again just fine, including the tabs and their directories. So maybe something fixed… > Thanks for your feedback, > Chris > (DIY session management for Okular: > find ~/.kde/share/apps/okular/docdata/ -cmin -100 -type f -print0|xargs -0 > cat| grep ' Okular is keeping very good track of what it's doing, and I'm very > *thankful* for that, and I hope it will keep storing these data in plain > text format in handy location. > One can't count on "fuser" to know what documents are used by Okular, > because I guess that if the document is not in pdf format, it is converted > to this in some temporary file that I haven't been able to find, and the > original file is not listed by fuser.) Yeah, I like it when I hold a Linux training that on next time opening a PDF it opens it at the page where I left it. Thanks, -- Martin
Re: Do you have Konsole session restored?
On Thursday, June 23, 2016 12:13:57 Martin Steigerwald wrote: > Am Donnerstag, 23. Juni 2016, 00:31:04 CEST schrieb inkbottle: > > Hi, > > I have received comments from this bug: > > https://bugs.kde.org/show_bug.cgi?id=343518 > > As I said there, on my side, Konsole is never restored. > > Is it restored to you, was it restored 1 month ago? > > My system might be different from yours since I follow stretch and not > > sid. > > Session management has been a mess for me since quite some time. > > It just doesn´t work consistenly. KMail, konsole, and others all gone when > logging out and logging in again. On the other hand a Konqueror window with > an opened webpage reappeared every time. > > I have set it to restore the old windows, but I seriously consider just > setting it to start an empty session for now. > > I never took the time to check for upstream bug reports about this. For me > it is not just that some applications are not restored, most of them > aren´t. I've been interested first in this session restoring thing because I needed to have my Okular documents restored. At the present, I have everything restored, systematically, save Konsole, so I only have to memorise what directory I was in, which is not too hard. Everything is: Okular, Dolphin, Kmail, Konversation, Chromium... Thanks for your feedback, Chris (DIY session management for Okular: find ~/.kde/share/apps/okular/docdata/ -cmin -100 -type f -print0|xargs -0 cat| grep '
Re: Do you have Konsole session restored?
Am Donnerstag, 23. Juni 2016, 00:31:04 CEST schrieb inkbottle: > Hi, > I have received comments from this bug: > https://bugs.kde.org/show_bug.cgi?id=343518 > As I said there, on my side, Konsole is never restored. > Is it restored to you, was it restored 1 month ago? > My system might be different from yours since I follow stretch and not sid. Session management has been a mess for me since quite some time. It just doesn´t work consistenly. KMail, konsole, and others all gone when logging out and logging in again. On the other hand a Konqueror window with an opened webpage reappeared every time. I have set it to restore the old windows, but I seriously consider just setting it to start an empty session for now. I never took the time to check for upstream bug reports about this. For me it is not just that some applications are not restored, most of them aren´t. Thanks, -- Martin
Do you have Konsole session restored?
Hi, I have received comments from this bug: https://bugs.kde.org/show_bug.cgi?id=343518 As I said there, on my side, Konsole is never restored. Is it restored to you, was it restored 1 month ago? My system might be different from yours since I follow stretch and not sid. Chris
Re: Konsole bug?
Am Donnerstag, 10. September 2015, 12:29:20 CEST schrieb Andreas Bourges:
> Hi,
Hi Andreas,
> ...since KF5 update (sid/experimental), I have observed a small bug in
> konsole:
>
> - open multiple tabs in konsole
> - menu -> copy input to -> select tabs (or CTRL-Shift-. on my system)
> - select or deselect some tabs
> - press ALT-o ("OK") - doesn't "press" ok, but inserts an "o" in the search
> field
>
> ALT-s / ALT-d / Alt-c shortcuts are working as expected...
>
> Can someone please test, if this is reproducable (and not a local problem on
> my system).
Confirmed, *if* input field is selected. If it is not selected nothing
happens.
This is clearly an upstream bug. Please report with bugs.kde.org, but check
for duplicates.
Thank you,
--
Martin
Re: Konsole bug?
On Thursday 10 September 2015 14:45:03 Diederik de Haas wrote: > With me ALT-o doesn't 'press' ok and in fact doesn't seem to do anything, > only actually clicking "OK" makes the dialog go away. > When I then do in the 'original' tab "gcc --version" (for example) it > executes an entirely different command in the other tab! The only link I > was able to find is that it uses a command from the 'original' tab's > history. > The 'original' tab was a root session while the other was a normal user > session. ...hm - this *does* work for me ?! Strange (and risky) behaviour :( > Although the symtoms aren't identical, it sure looks like a bug in Konsole. I'll check the konsole bugs (again) tonight and will open one regarding the ALT-o issue. Thanks for testing! Andy
Re: Konsole bug?
On Thursday 10 September 2015 12:29:20 Andreas Bourges wrote:
> - open multiple tabs in konsole
> - menu -> copy input to -> select tabs (or CTRL-Shift-. on my system)
> - select or deselect some tabs
> - press ALT-o ("OK") - doesn't "press" ok, but inserts an "o" in the search
> field
With me ALT-o doesn't 'press' ok and in fact doesn't seem to do anything, only
actually clicking "OK" makes the dialog go away.
When I then do in the 'original' tab "gcc --version" (for example) it executes
an entirely different command in the other tab! The only link I was able to
find is that it uses a command from the 'original' tab's history.
The 'original' tab was a root session while the other was a normal user
session.
> Can someone please test, if this is reproducable (and not a local problem
> on my system).
Although the symtoms aren't identical, it sure looks like a bug in Konsole.
signature.asc
Description: This is a digitally signed message part.
Konsole bug?
Hi,
...since KF5 update (sid/experimental), I have observed a small bug in konsole:
- open multiple tabs in konsole
- menu -> copy input to -> select tabs (or CTRL-Shift-. on my system)
- select or deselect some tabs
- press ALT-o ("OK") - doesn't "press" ok, but inserts an "o" in the search
field
ALT-s / ALT-d / Alt-c shortcuts are working as expected...
Can someone please test, if this is reproducable (and not a local problem on
my system).
thanks,
Andy
Re: CLI Konsole -p Command query
CORRECTION On 18/02/14 21:10, Scott Ferguson wrote: > the x-y:- > I want to start an ssh screen session in Konsole from a script > (/etc/rc.local) run on the machine I want to connect to. e.g.:- > box A boots and runs rc.local that then uses an ssh command to start a > konsole session, for which there is no previously defined profile, on > box B that connects to box A. > > This works fine when I'm calling a *previously defined* profile on Box > B. e.g.:- > ;the script on box A (/etc/rc.local):- > ssh scott@vbserver 'export DISPLAY=:0 && konsole --profile dev' > ;the konsole profile on box A The previous line should read "the konsole profile on box B" > (/home/scott/.kde/share/apps/konsole/dev.profile):- > [Appearance] > ColorScheme=BlackOnLightYellow > Font=Oxygen Mono,12,-1,5,50,0,0,0,0,0 > [General] > Command=ssh -t dev screen -dR > Directory= > Icon=network-server > LocalTabTitleFormat=%D : %n > MenuIndex=3 > Name=Dev > Parent=FALLBACK/ > RemoteTabTitleFormat=Dev : %u > ShowNewAndCloseTabButtons=false > ShowTerminalSizeHint=false > StartInCurrentSessionDir=false > > > I've tried various CLI options using both the "-p Command=" and "-c > " without success. box A has the SSH key copied to, and is > listed in known_hosts on box B. e.g.:- > /etc/rc.local (box A):- > ssh scott@vbserver 'export DISPLAY=:0 && konsole -p Command='ssh > scott@wheezystripped' -p Icon=network-server --new-tab' > > I've also tried with only the "-p Command=" with and without the > --new-tab, as well as different orders of Konsole parameters. > Everything works fine if I don't try the command (i.e. just use > --new-tab and -p Icon=) > > I really don't want to resort to the -> (use ssh):- > Test for existing profile > If ! Exist create profile > Use profile (with ssh) > > I already have other stuff called from /etc/rc.local box B to box A > (kdialog and festival message) > > > Kind regards > > > > -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/530335fd.3080...@gmail.com
CLI Konsole -p Command query
the x-y:- I want to start an ssh screen session in Konsole from a script (/etc/rc.local) run on the machine I want to connect to. e.g.:- box A boots and runs rc.local that then uses an ssh command to start a konsole session, for which there is no previously defined profile, on box B that connects to box A. This works fine when I'm calling a *previously defined* profile on Box B. e.g.:- ;the script on box A (/etc/rc.local):- ssh scott@vbserver 'export DISPLAY=:0 && konsole --profile dev' ;the konsole profile on box A (/home/scott/.kde/share/apps/konsole/dev.profile):- [Appearance] ColorScheme=BlackOnLightYellow Font=Oxygen Mono,12,-1,5,50,0,0,0,0,0 [General] Command=ssh -t dev screen -dR Directory= Icon=network-server LocalTabTitleFormat=%D : %n MenuIndex=3 Name=Dev Parent=FALLBACK/ RemoteTabTitleFormat=Dev : %u ShowNewAndCloseTabButtons=false ShowTerminalSizeHint=false StartInCurrentSessionDir=false I've tried various CLI options using both the "-p Command=" and "-c " without success. box A has the SSH key copied to, and is listed in known_hosts on box B. e.g.:- /etc/rc.local (box A):- ssh scott@vbserver 'export DISPLAY=:0 && konsole -p Command='ssh scott@wheezystripped' -p Icon=network-server --new-tab' I've also tried with only the "-p Command=" with and without the --new-tab, as well as different orders of Konsole parameters. Everything works fine if I don't try the command (i.e. just use --new-tab and -p Icon=) I really don't want to resort to the -> (use ssh):- Test for existing profile If ! Exist create profile Use profile (with ssh) I already have other stuff called from /etc/rc.local box B to box A (kdialog and festival message) Kind regards -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/530331a8.5070...@gmail.com
konsole: Inappropriate ioctl for device
Hi,
I have a profile set up with the command: su -c /bin/bash
and recently (since KDE 4.7, maybe 4.6, or perhaps kernel 3.2.0) it has
started spitting out:
"""
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
"""
which causes things like pre-configuring to fail when running "apt-get upgrade"
from the session.
It is no big deal ATM ("Command: su -" works fine) but I'm wondering if it is a
KDE/Konsole or kernel thing and if there is a work around.
- Bruce
--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204221742.14510.bms...@shaw.ca
Re: konsole: Inappropriate ioctl for device
On April 22, 2012 05:42:13 PM I wrote: > """ > bash: cannot set terminal process group (-1): Inappropriate ioctl for > device bash: no job control in this shell > """ Forgot to mention... this is an up to date Unstable amd64 system. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201204221749.35930.bms...@shaw.ca
Konsole close tab icon not active when you select show buttons open and close tabs.
Hello, I found a very little bug. When you select show bottoms open and close tabs in konsole setup, close tab icon is not active. Toni Mirabete -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktikk3s8t4rz_gv8eytkjhxngxar...@mail.gmail.com
Re: Konsole window size and new window placement
On Jueves 10 Marzo 2011 22:29:37 Andrej Kacian escribió: > On Thu, 10 Mar 2011 18:16:22 +0100 > > BasaBuru wrote: > >You move the konsole icon to pannel (i'm use terminator, but i think is > >same) > > > >In icon settings->aplication use the --geometry X11 comand > > > >for view the options see man X > > > >I have in the comand -> terminator --geometry 1400x800+300+200 > > Nope, I've tried that already - konsole is happily ignoring --geometry. It's work $ konsole --help-kde Options of kde --geometry $ konsole -v Qt: 4.6.3 Plataforma de desarrollo de KDE: 4.4.5 (KDE 4.4.5) Konsole: 2.4.5 > I'm starting to think that I'll need to upgrade to wheezy to get this > simple feature. Is the best if you working wiht the kde 3.5 Bye BasaBuru -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103112054.13105.basab...@basatu.org
Re: Konsole window size and new window placement
On Thu, 10 Mar 2011 18:16:22 +0100 BasaBuru wrote: >You move the konsole icon to pannel (i'm use terminator, but i think is same) > >In icon settings->aplication use the --geometry X11 comand > >for view the options see man X > >I have in the comand -> terminator --geometry 1400x800+300+200 Nope, I've tried that already - konsole is happily ignoring --geometry. I'm starting to think that I'll need to upgrade to wheezy to get this simple feature. Kind regards, -- Andrej Kacian -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110310222937.79dbfeda@penny
Re: Konsole window size and new window placement
> $ konsole --vt_sz 80x25 > konsole: Unknown option 'vt_sz'. > konsole: Use --help to get a list of available command line options. > > Is this perhaps something added in KDE 4.5 or later? No. It is an old version: $ konsole -v Qt: 3.3.8b KDE: 3.5.10 Konsole: 1.6.6 -- Tomasz Kundera -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimljigx-h8p9mdb++6erurkcldywgi_fv0jh...@mail.gmail.com
Re: Konsole window size and new window placement
On Thu, 10 Mar 2011 17:05:20 +0100 Tomasz Kundera wrote: > On Wed, Mar 9, 2011 at 10:20 PM, Andrej Kacian > wrote: > > Hello all, > > > > is there a way to have new Konsole windows always spawn in certain > > (default) size? I've been hunting around in various settings and window > > behavior dialogs, but I can't seem to find it. > > konsole --vt_sz CCxLL? > $ konsole --vt_sz 80x25 konsole: Unknown option 'vt_sz'. konsole: Use --help to get a list of available command line options. Is this perhaps something added in KDE 4.5 or later? -- Andrej Kacian -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110310193723.540c95f7@penny
Re: Konsole window size and new window placement
On Miércoles 09 Marzo 2011 22:20:20 Andrej Kacian escribió: > Hello all, > > is there a way to have new Konsole windows always spawn in certain > (default) size? I've been hunting around in various settings and window > behavior dialogs, but I can't seem to find it. > I even tried forcing a particular size in "Advanced/Special Window > Settings..." window context menu, but it is not always honored - new > Konsole often (sometimes not, so far it doesn't seem too deterministic to > me) starts with size of last-resized existing Konsole window, even after > such window is closed. > > Also, I would like to know if kwin can be set to place new windows in > "tiled" fashion. There are few choices in kwin config including > "cascading" and "smart", but neither seems to be what I want. > > I'm using KDE 4.4.5 from Squeeze on amd64 arch. > You move the konsole icon to pannel (i'm use terminator, but i think is same) In icon settings->aplication use the --geometry X11 comand for view the options see man X I have in the comand -> terminator --geometry 1400x800+300+200 Bye BasaBuru -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103101816.22547.basab...@basatu.org
Re: Konsole window size and new window placement
On Wed, Mar 9, 2011 at 10:20 PM, Andrej Kacian wrote: > Hello all, > > is there a way to have new Konsole windows always spawn in certain (default) > size? I've been hunting around in various settings and window behavior > dialogs, but I can't seem to find it. konsole --vt_sz CCxLL? -- Tomasz Kundera -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=srlbkuunvnttgw0-jnk1jhcl7+djhfbikz...@mail.gmail.com
Re: Konsole window size and new window placement
On 2011-03-09 15:20:20 Andrej Kacian wrote: >Also, I would like to know if kwin can be set to place new windows in >"tiled" fashion. There are few choices in kwin config including "cascading" >and "smart", but neither seems to be what I want. Not that I know of. You can use XMonad or another tiling window manager instead of KWin and still get all the other parts of KDE SC 4, including Plamsa and KRunner (though, you will probably need to tell your WM what key should start KRunner). -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Konsole window size and new window placement
Hello all, is there a way to have new Konsole windows always spawn in certain (default) size? I've been hunting around in various settings and window behavior dialogs, but I can't seem to find it. I even tried forcing a particular size in "Advanced/Special Window Settings..." window context menu, but it is not always honored - new Konsole often (sometimes not, so far it doesn't seem too deterministic to me) starts with size of last-resized existing Konsole window, even after such window is closed. Also, I would like to know if kwin can be set to place new windows in "tiled" fashion. There are few choices in kwin config including "cascading" and "smart", but neither seems to be what I want. I'm using KDE 4.4.5 from Squeeze on amd64 arch. Thanks in advance, -- Andrej Kacian -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110309222020.2494089f@penny
Re: kde 4.2.1 konsole shortcut
On Thursday 11 June 2009 12:12:19 Peter Palm wrote: > see http://watdoejefout.nl/linux/settings-shortcuts.png Off-topic: What an awesome domain name :-D (trans: what you're doing wrong) -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: kde 4.2.1 konsole shortcut
> Yes there is! > see http://watdoejefout.nl/linux/settings-shortcuts.png thanks! (!) Pol -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: kde 4.2.1 konsole shortcut
Op woensdag 10 juni 2009 19:24:15 schreef Pol Hallen: > > You can change it from Settings->Configure Shortcuts. The default is > > ctrl+shift+n. > > there isn't "configure shortcuts" in settings(!) Yes there is! see http://watdoejefout.nl/linux/settings-shortcuts.png Peter -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: kde 4.2.1 konsole shortcut
> You can change it from Settings->Configure Shortcuts. The default is > ctrl+shift+n. there isn't "configure shortcuts" in settings(!) Pol -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: kde 4.2.1 konsole shortcut
2009/6/10 Pol Hallen : > Hi folks! > > Can I set the shortcut for open new session into konsole? > (in kde3.x I used ctrl+alt+n) > thanks > > Pol You can change it from Settings->Configure Shortcuts. The default is ctrl+shift+n. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
kde 4.2.1 konsole shortcut
Hi folks! Can I set the shortcut for open new session into konsole? (in kde3.x I used ctrl+alt+n) thanks Pol -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: KDE 4.2 minor issues: Konqueror & YouTube, Konqueror & mouse pointer, Plasma menu, Konsole
Hello These are coding issues we can't do much about. You should report these to http://bugs.kde.org > Konqueror & Youtube: > It just doesn't work. Neither on x86, nor on x86_64. > Konqueror & mouse pointer: > Most of the time the mouse pointer in Konqueror stays in a hour glass > state (e.g. try www.spiegel.de). These are bugs to assign to konqueror/khtml > Plasma menu: > The Plasma menu should appear on top of every other window when clicking > on the Plasma "cashew". This is a wish (new feature, not bug fix) for plasma Regards -- Xavier Vello -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
KDE 4.2 minor issues: Konqueror & YouTube, Konqueror & mouse pointer, Plasma menu, Konsole
Hi there, first, I'd like to state that I'm very comfortable with KDE 4.2. It feels ready now for daily usage. Thanks to the packagers!!! Nevertheless, for me some issues remain: Konqueror & Youtube: It just doesn't work. Neither on x86, nor on x86_64. Konqueror & mouse pointer: Most of the time the mouse pointer in Konqueror stays in a hour glass state (e.g. try www.spiegel.de). Plasma menu: The Plasma menu should appear on top of every other window when clicking on the Plasma "cashew". Kind regards, Felix -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Konsole issues
Hi, I just resurrected my desktop box after it's been languishing in a corner for months and decided to bring it up to date and also put KDE4 on it in a single swoop. Whilst it eventually worked (I'm not sure if I did something odd or if my apt-get has gone funny as I had to manually specify a large number of the dependencies on the command line rather than just kde4 itself, which meant I somehow missed out on systemsettings...), I don't think hugely of it's looks at the moment and am trying to make it a bit more comparable to my old KDE3 setup. The only major issue I've had thus far (that I've found) is that on konsole the cursor seems to be pretending to be several spaces over to the right. The text appears in the correct place, but the cursor is mispositioned... I've fiddled with the font settings but that doesn't seem to change. And oh yes, this is on a completely fresh account, no user settings at all. I'm probably missing something obvious TBH... -- ZoeP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: multiple konsole windows
On Friday 12 September 2008, Dominik Schulz wrote: > Am Freitag, 12. September 2008 06:03:22 schrieb John Schmidt: > > I just installed kde 4.1 from experimental and have observed the > > following. If I open up various applications and then log out and log > > back in, some of the applications that were open previously are not > > automatically started back up. Specifically, if I open an instance of > > iceweasel, it does not start back up. In addition, if I have multiple > > konsole windows opened, only one of the windows is remembered when > > logging back in. > > > > Have others observed this same behavior and are there any work arounds? > > I have observed the same behaviour on my system (KDE 4.1 from lenny- > backports). To follow up after looking at some bug reports on konsole in KDE 4.1, I understand that session saving/restoration is being worked on but is not at the same state it was in the KDE 3.5.x series. Evidently there is a new session state saving/restoration in 4.x that is integrated into various components at various levels of completeness (at least as compared to 3.5.x behavior). John Schmidt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: multiple konsole windows
Am Freitag, 12. September 2008 06:03:22 schrieb John Schmidt: > I just installed kde 4.1 from experimental and have observed the following. > If I open up various applications and then log out and log back in, some of > the applications that were open previously are not automatically started > back up. Specifically, if I open an instance of iceweasel, it does not > start back up. In addition, if I have multiple konsole windows opened, > only one of the windows is remembered when logging back in. > > Have others observed this same behavior and are there any work arounds? I have observed the same behaviour on my system (KDE 4.1 from lenny- backports). -- Best Regards, Dominik signature.asc Description: This is a digitally signed message part.
multiple konsole windows
Hi, I just installed kde 4.1 from experimental and have observed the following. If I open up various applications and then log out and log back in, some of the applications that were open previously are not automatically started back up. Specifically, if I open an instance of iceweasel, it does not start back up. In addition, if I have multiple konsole windows opened, only one of the windows is remembered when logging back in. Have others observed this same behavior and are there any work arounds? Note: I created a test user and tried the above experiments and had the same problems. Thanks, John Schmidt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Missing DBus interfaces file in konsole package
On Tuesday 05 August 2008, Florian Jauernig wrote: > Searching in the web a little I assume that > > org.kde.konsole.*.xml > > files are missing under: > > /usr/share/dbus-1/interfaces/ > > I also browsed kde svn under > > http://websvn.kde.org/trunk/KDE/kdebase/apps/konsole/src/ > > and there these files can be found. > > Can you confirm that my problems using DBus with konsole are based on these > missing files, and if yes could you please add these files to konsole > package? The D-Bus viewer and other similar tools like qdbus do not use these files to determine a target application's capabilities, but rather ask the application to provide the data at runtime, so called introspection. For whatever reason it seems that Konsole's D-Bus objects do not do this properly. You can of course still use these files to determine the methods and their arguments manually, though some of the tools attempt to verify arguments based on the introspection and will then fail an actually valid call. If you could check with qdbus if the objects are not introspectable for it as well, you could file a bug report against Konsole. Cheers, Kevin signature.asc Description: This is a digitally signed message part.
Missing DBus interfaces file in konsole package
Hi, hopefully this list is the correct place for reporting missing files - if not please point me to the appropriate place. I am using KDE 4.1 from experimental. I tried to interoperate with konsole using DBus. For finding supported methods I used qdbusviewer, but for konsole I could not find any methods. For i.e. kmail, and kmix qdbusviewer showed me the needed methods and object paths and I was able to interoperate with kmail and kmix using dbus-send. Searching in the web a little I assume that org.kde.konsole.*.xml files are missing under: /usr/share/dbus-1/interfaces/ I also browsed kde svn under http://websvn.kde.org/trunk/KDE/kdebase/apps/konsole/src/ and there these files can be found. Can you confirm that my problems using DBus with konsole are based on these missing files, and if yes could you please add these files to konsole package? Thanks in advance Florian signature.asc Description: This is a digitally signed message part.
