Bug#762182: qtcreator: freezes on start

2014-09-19 Thread Stefan Schwarzer
Package: qtcreator
Version: 3.2.0+dfsg-2
Severity: important

When I start qtcreator with or without project file arguments, the interface 
freezes completely.
'strace qtcreator' in some window shows that events (crossing buttons with the 
mouse) create 
some messages on Qt level, example

poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, 
msg_iov(1)=[{\34\0\26\2Q\2\0\0\220\1\0\0\240\247\17\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0,
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
futex(0x1c224d4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x1c224d0, {FUTEX_OP_SET, 0, 
FUTEX_OP_CMP_GT, 1}) = 1
futex(0x1c224a8, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, 
msg_iov(1)=[{\34\0\26\2Q\2\0\0\220\1\0\0\241\247\17\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0,
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
futex(0x1c224d4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x1c224d0, {FUTEX_OP_SET, 0, 
FUTEX_OP_CMP_GT, 1}) = 1
futex(0x1c224a8, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, 
msg_iov(1)=[{U\2\26\2\333\247\17\1\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0 
\1\5\0\0, 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
futex(0x1c224d4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x1c224d0, {FUTEX_OP_SET, 0, 
FUTEX_OP_CMP_GT, 1}) = 1
futex(0x1c224a8, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, 
msg_iov(1)=[{U\2\26\2\213\273\17\1\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0 
\1\4\0\0, 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
futex(0x1c224d4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x1c224d0, {FUTEX_OP_SET, 0, 
FUTEX_OP_CMP_GT, 1}) = 1
poll([{fd=3, events=POLLIN}], 1, 4294967295
 
but these seem to go unnoticed. I suspect an issue with configuration files 
'*pro.user...', 
but I cannot pinpoint the issue yet. 

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages qtcreator depends on:
ii  libbotan-1.10-0  1.10.8-2
ii  libc62.19-11
ii  libgcc1  1:4.9.1-14
ii  libqt5concurrent55.3.1+dfsg-3
ii  libqt5core5a [qtbase-abi-5-3-1]  5.3.1+dfsg-3
ii  libqt5declarative5 [qtquick1-abi-5-2-1]  5.3.1-1
ii  libqt5designer5  5.3.1-3
ii  libqt5designercomponents55.3.1-3
ii  libqt5gui5   5.3.1+dfsg-3
ii  libqt5help5  5.3.1-3
ii  libqt5network5   5.3.1+dfsg-3
ii  libqt5printsupport5  5.3.1+dfsg-3
ii  libqt5qml5 [qtdeclarative-abi-5-3-0] 5.3.1-6
ii  libqt5quick5 5.3.1-6
ii  libqt5script55.3.1+dfsg-3
ii  libqt5sql5   5.3.1+dfsg-3
ii  libqt5sql5-sqlite5.3.1+dfsg-3
ii  libqt5webkit55.3.1+dfsg-3
ii  libqt5widgets5   5.3.1+dfsg-3
ii  libqt5x11extras5 5.3.1-1
ii  libqt5xml5   5.3.1+dfsg-3
ii  libstdc++6   4.9.1-14
ii  libx11-6 2:1.6.2-3
ii  qml-module-qtquick-controls  5.3.1-1
ii  qml-module-qtquick2  5.3.1-6
ii  qtchooser47-gd2b7997-1
ii  qtcreator-data   3.2.0+dfsg-2

Versions of packages qtcreator recommends:
ii  gdb7.7.1+dfsg-3
ii  konsole [x-terminal-emulator]  4:4.14.0-1
ii  make   4.0-8
ii  qt5-doc5.3.0-2
ii  qtbase5-dev-tools  5.3.1+dfsg-3
ii  qtcreator-doc  3.2.0+dfsg-2
ii  qtdeclarative5-dev-tools   5.3.1-6
ii  qtquick1-5-dev-tools   5.3.1-1
ii  qttools5-dev-tools 5.3.1-3
ii  qttranslations5-l10n   5.3.1-1
ii  qtxmlpatterns5-dev-tools   5.3.1-4
ii  xterm [x-terminal-emulator]310-1

Versions of packages qtcreator suggests:
ii  cmake  2.8.12.2-2
ii  g++4:4.9.1-1
ii  git1:2.1.0-1
ii  kdelibs5-data  4:4.14.0-1
ii  subversion 1.8.10-1+b1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140919100438.26501.60635.reportbug@localhost.localdomain



Bug#762182: close

2014-09-19 Thread Stefan Schwarzer

It seems that there is another qt/kde component involved. Logout/login fixes 
the issue.

Sorry for the noise


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2992415.I7Pr7Qb0Wq@nbofm020



Bug#762182: close

2014-09-19 Thread Stefan Schwarzer

It seems that there is another qt/kde component involved. Logout/login fixes 
the issue.
Sorry for the noise


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/trinity-838f5283-e291-4add-9464-9f1eab99def1-1411127115286@3capp-gmx-bs03



Bug#886186: akonadi-server: akonadi server fails to start mysqld due to apparmor intervention

2018-01-02 Thread Stefan Schwarzer
Package: akonadi-server
Version: 4:17.08.3-1
Severity: important

Dear Maintainer,

I am following debian testing and in the course of the last months have
twice run into the following issue: 

after aptitude update/full-upgrade, akonadi-server will not start. 
Running akonadictl start from the command line I spotted the failing command
as being the  invocation of mysqld. 

I cannot provide the text of the failing command here because I upgraded 
akonadi-server
and apparmor to unstable to see if the problem goes away (no it
doesn't) and now akonadictl keeps crashing on me
(and if I would downgrade the data base format does not match any longer).
apparmor and  libapparmor are at 2.11.1-4.

However, the state of my analysis is

1. When starting kontact, akonadi fails to invoke mysqld because the
daemon cannot open its configuration file in my home directory
(strace). The file exists and is world-readable. The mysqld command line looks
unsuspicious and specifies a socket (which exists), the configuration file
and something else which I do not remember.

2. The problem disappears after disabling apparmor (which I did not
explicitly install, thus the bug classification as important). A
reboot is necessary, though - probably systemctl stop apparmor is not
sufficient to 'really' stop it.

3. There is a configuration file for myslqd and akonadis invocation of
mysqld in /etc/apparmor.d 

 usr.sbin.mysqld
 usr.sbin.myslqd-akonadi

which I did not touch, but whose correctness I cannot judge either.
The relevant line seems to come from usr.sbin.mysqld-akonadi

 @{HOME}/.local/share/akonadi/** rwk,

which feels correct, as this describes the path to my configuration file:

root@nbof16:/home/sts# ls -l .local/share/akonadi/mysql.conf 
-rw-r--r-- 1 sts sts 3531 Jan  2 21:19 .local/share/akonadi/mysql.conf

OK - this is as far as I feel able to go. Maybe some akonadi or
apparmor specialist can take over from here?


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages akonadi-server depends on:
ii  akonadi-backend-mysql  4:17.08.3-1
ii  libc6  2.25-5
ii  libgcc11:7.2.0-18
ii  libkf5akonadiprivate5  4:17.08.3-1
ii  libkf5akonadiwidgets5  4:17.08.3-1
ii  libkf5configcore5  5.37.0-2
ii  libkf5coreaddons5  5.37.0-2
ii  libkf5crash5   5.37.0-2
ii  libkf5i18n55.37.0-2
ii  libqt5core5a   5.9.2+dfsg-6
ii  libqt5dbus55.9.2+dfsg-6
ii  libqt5gui5 5.9.2+dfsg-6
ii  libqt5network5 5.9.2+dfsg-6
ii  libqt5sql5 5.9.2+dfsg-6
ii  libqt5widgets5 5.9.2+dfsg-6
ii  libqt5xml5 5.9.2+dfsg-6
ii  libstdc++6 7.2.0-18

akonadi-server recommends no packages.

Versions of packages akonadi-server suggests:
ii  akonadi-backend-mysql   4:17.08.3-1
pn  akonadi-backend-postgresql  
pn  akonadi-backend-sqlite  

-- no debconf information



Bug#943585: kwin-x11: kwin (?) causes extreme flickering and tear on login

2019-10-26 Thread Stefan Schwarzer
Package: kwin-x11
Version: 4:5.14.5-1+b1
Severity: important

Dear Maintainer,

I am following debian unstable, desktop X11/sddm/kde on a Lenovo laptop T460p.
The nvidia graphics on the laptop is disabled in favor of the chipset graphics
(Intel).

After the last upgrade (which was from testing to stable on the 25th October),
I am experiencing a mostly unusable desktop. The login screen (sddm) comes up
as expected,
but right after login I get flickering black rectangles on the screen, which
may
cover up to 90% of its area. Windows mostly remain black or their content
suddenly
becomes visible he task bar remains black and I see other residuals of the kde
splash
screen where windows should be drawn or the background wallpaper be
restored. Swithing to a VT; all seems ok, kwin, the desktop and applications
are
running.

So far, my only clue as to what may be going on is a workaroud: if I start a
terminal
via keyboard shortcut and issue blindly
DRI_PRIME=1 kwin_x11 --replace
then afterwards things behave mostly normally (Sometimes window contaent is
still
not correctly updated). I just picked this line up from older bug reports
against kwin on the net without understanding what it does.

This is the output of kwin following this command in the hope that it helps

OpenGL vendor string:   Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530
(Skylake GT2)
OpenGL version string:  4.5 (Core Profile) Mesa 19.2.1
OpenGL shading language version string: 4.50
Driver: Intel
GPU class:  Unknown
OpenGL version: 4.5
GLSL version:   4.50
Mesa version:   19.2.1
X server version:   1.20.4
Linux kernel version:   5.3
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kwin-x11 depends on:
ii  kwin-common4:5.14.5-1+b1
ii  libc6  2.29-2
ii  libepoxy0  1.5.3-0.1
ii  libgcc11:9.2.1-12
ii  libkf5configcore5  5.62.0-1
ii  libkf5coreaddons5  5.62.0-1
ii  libkf5crash5   5.62.0-1
ii  libkf5i18n55.62.0-1
ii  libkf5quickaddons5 5.62.0-1
ii  libkf5waylandserver5   4:5.62.0-2
ii  libkf5windowsystem55.62.0-2
ii  libkwineffects11   4:5.14.5-1+b1
ii  libkwinglutils11   4:5.14.5-1+b1
ii  libkwinxrenderutils11  4:5.14.5-1+b1
ii  libqt5core5a   5.12.5+dfsg-2
ii  libqt5gui5 5.12.5+dfsg-2
ii  libqt5widgets5 5.12.5+dfsg-2
ii  libqt5x11extras5   5.12.5-1
ii  libstdc++6 9.2.1-12
ii  libx11-6   2:1.6.8-1
ii  libxcb-composite0  1.13.1-2
ii  libxcb-cursor0 0.1.1-4
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb-randr0  1.13.1-2
ii  libxcb-render0 1.13.1-2
ii  libxcb-shape0  1.13.1-2
ii  libxcb-xfixes0 1.13.1-2
ii  libxcb11.13.1-2
ii  libxi6 2:1.7.9-1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- no debconf information



Bug#943585: Acknowledgement (kwin-x11: kwin (?) causes extreme flickering and tear on login)

2019-12-20 Thread Stefan Schwarzer
Hi Brendon,

I was working on gnome in the meantime, so I only noticed your remark today.

I checked my /etc/X11/xorg.conf.d as you suggested, but there is absolutely
nothing in there. Long time ago I remember having tried to set up a second X
server to get bumblebee working, but I gave up on that. My attempt to fix the
kwin_x11 behavior basically had me remove the entire kde-stuff and everything
remotely related to intel graphics as well. In the meantime I am also back at
testing rather than unstable.

The kwin_x11 issue is still unchanged. Currently, I am in the process to
disobey the debian rules for bug reporting and to cross-post at kde.

Thanks for your update,

Happy Christmas/change of the year/may reason be with all of us...

Stefan



Bug#943585: bug gone with kwin-x11 version 5.17 from experimental

2020-02-11 Thread Stefan Schwarzer
Hi, 

I updated kwin-x11 yesterday from experimental from version 5.14 to 5.17. For 
me, the erratic behavior of the window manager is gone.

Thanks to all.