[kwin] [Bug 428897] Kwin consistently crashes

2020-11-09 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=428897

Pierce  changed:

   What|Removed |Added

 CC||gripw...@gmail.com

--- Comment #1 from Pierce  ---
The bug appears to be caused by libkdecorations2-5v5, libkf5screen-bin, and/or
libkf5screen7 when they are upgraded to versions 4:5.19.5-3, 4:5.19.5-3, and
4:5.19.5-3, respectively. Downgrading libkdecorations2-5v5 to 4:5.17.5-2,
libkf5screen-bin to 4:5.17.5-3, and libkf5screen7 to 4:5.17.5-3 fixed it for
me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 428897] Kwin consistently crashes

2020-11-10 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=428897

--- Comment #5 from Pierce  ---
(In reply to Vlad Zahorodnii from comment #4)
> (In reply to Pierce from comment #1)
> > The bug appears to be caused by libkdecorations2-5v5, libkf5screen-bin,
> > and/or libkf5screen7 when they are upgraded to versions 4:5.19.5-3,
> > 4:5.19.5-3, and 4:5.19.5-3, respectively. Downgrading libkdecorations2-5v5
> > to 4:5.17.5-2, libkf5screen-bin to 4:5.17.5-3, and libkf5screen7 to
> > 4:5.17.5-3 fixed it for me.
> 
> You cannot use kwin 5.17 with kdecorations 5.19. Both must have the same
> version.

Nice catch! As of right now, Debian Testing has kwin-x11 at version 5.17, but
the three kdecorations packages were bumped to version 5.19. Unstable has
kwin-x11 at 5.19.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 431440] New: Plasma fails to start

2021-01-11 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=431440

Bug ID: 431440
   Summary: Plasma fails to start
   Product: plasmashell
   Version: 5.20.4
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: gripw...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Plasma fails to start following recent update

STEPS TO REPRODUCE
1. Boot system and wait for SDDM to appear
2. Select "Plasma" as the desktop environment
3. Enter password and hit enter

OBSERVED RESULT
With a splash screen selected, the splash screen appears but the desktop never
starts up. With the splash screen set to "none", you are stuck at SDDM.

EXPECTED RESULT
Successful login to Plasma

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Testing
(available in About System)
KDE Plasma Version: 5.20.4/5.20.5 (see additional information)
KDE Frameworks Version: 5.77.0-2 
Qt Version: 5.15.2

ADDITIONAL INFORMATION
plasma-desktop is on version 4:5.20.4-2, while plasma-workspace is on
4:5.20.5-1 in the Debian Testing repositories. I've included the
installed/removed packages list from /var/log/apt/history.log below:
Install: libgps28:amd64 (3.21.99~rc1-2, automatic),
linux-image-5.10.0-1-amd64:amd64 (5.10.4-1, automatic)
Upgrade: libkdecorations2-5v5:amd64 (4:5.20.4-2, 4:5.20.5-1),
libkf5wallet-data:amd64 (5.77.0-2, 5.77.0-3), libcups2:amd64 (2.3.3op1-4,
2.3.3op1-5), liblibreoffice-java:amd64 (1:7.0.4~rc2-1, 1:7.0.4-3),
libreoffice-calc:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3), libpulse0:amd64 (13.0-5,
14.0-2), libkwinglutils12:amd64 (4:5.20.4-4+b1, 4:5.20.5-1),
uno-libs-private:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3),
libreoffice-base-core:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3),
firmware-iwlwifi:amd64 (20200918-1, 20201022-1), libglx-mesa0:amd64 (20.2.6-1,
20.3.2-1), libksysguardsensorfaces1:amd64 (4:5.20.4-2, 4:5.20.5-1),
libctf-nobfd0:amd64 (2.35.1-6, 2.35.1-7), bubblewrap:amd64 (0.4.1-1, 0.4.1-3),
libreoffice-core:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3), plasma-workspace:amd64
(4:5.20.4-6, 4:5.20.5-1), libraptor2-0:amd64 (2.0.14-1.1, 2.0.14-1.2),
libjurt-java:amd64 (1:7.0.4~rc2-1, 1:7.0.4-3), cups-bsd:amd64 (2.3.3op1-4,
2.3.3op1-5), cups-common:amd64 (2.3.3op1-4, 2.3.3op1-5),
libtaskmanager6abi1:amd64 (4:5.20.4-6, 4:5.20.5-1), libridl-java:amd64
(1:7.0.4~rc2-1, 1:7.0.4-3), libpulsedsp:amd64 (13.0-5, 14.0-2),
libreoffice-common:amd64 (1:7.0.4~rc2-1, 1:7.0.4-3), libkf5configwidgets5:amd64
(5.77.0-2, 5.77.0-3), pulseaudio:amd64 (13.0-5, 14.0-2),
libreoffice-report-builder-bin:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3), ure:amd64
(1:7.0.4~rc2-1+b1, 1:7.0.4-3), libkf5notifications-data:amd64 (5.77.0-2,
5.77.0-3), libgbm1:amd64 (20.2.6-1, 20.3.2-1), libbinutils:amd64 (2.35.1-6,
2.35.1-7), pulseaudio-utils:amd64 (13.0-5, 14.0-2), libweather-ion7:amd64
(4:5.20.4-6, 4:5.20.5-1), libkf5sysguard-bin:amd64 (4:5.20.4-2, 4:5.20.5-1),
cups-client:amd64 (2.3.3op1-4, 2.3.3op1-5), cups-ppdc:amd64 (2.3.3op1-4,
2.3.3op1-5), cups-daemon:amd64 (2.3.3op1-4, 2.3.3op1-5), gvfs-bin:amd64
(1.46.1-1, 1.46.1-2), krdc:amd64 (4:20.08.0-1, 4:20.12.0-1),
libkf5screen7:amd64 (4:5.20.4-2, 4:5.20.5-1), qalc:amd64 (2.8.2-1+b2,
2.8.2-1.1), libreoffice-draw:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3),
libtcl8.6:amd64 (8.6.10+dfsg-1, 8.6.11+dfsg-1), binutils-x86-64-linux-gnu:amd64
(2.35.1-6, 2.35.1-7), libqalculate20-data:amd64 (2.8.2-1, 2.8.2-1.1),
libkwineffects12a:amd64 (4:5.20.4-4+b1, 4:5.20.5-1),
libuno-purpenvhelpergcc3-3:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3),
libuno-cppu3:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3), libxatracker2:amd64
(20.2.6-1, 20.3.2-1), libbpf0:amd64 (1:0.2-1, 1:0.3-1),
libreoffice-impress:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3), gvfs-common:amd64
(1.46.1-1, 1.46.1-2), python3-pyqt5:amd64 (5.15.2+dfsg-1+b1, 5.15.2+dfsg-2),
plasma-workspace-data:amd64 (4:5.20.4-6, 4:5.20.5-1),
libuno-cppuhelpergcc3-3:amd64 (1:7.0.4~rc2-1+b1, 1:7.0.4-3), libtk8.6:amd64
(8.6.10-1, 8.6.11-1), fonts-opensymbol:amd64 (2:102.11+LibO7.0.4~rc2-1,
2:102.11+LibO7.0.4-3), wget:amd64 (1.20.3-1+b3, 1.21-1+b1),
mesa-va-drivers:amd64 (20.2.6-1, 20.3.2-1), dolphin:amd64 (4:20.12.0-2,
4:20.12.1-1), qml-module-qtwebkit:amd64 (5.212.0~alpha4-10, 5.212.0~alpha4-11),
libgl1-mesa-dri:amd64 (20.2.6-1, 20.3.2-1), cups-ipp-utils:amd64 (2.3.3op1-4,
2.3.3op1-5), libprocessui9:amd64 (4:5.20.4-2, 4:5.20.5-1),
libgl1-mesa-glx:amd64 (20.2.6-1, 20.3.2-1), libunoloader-java:amd64
(1:7.0.4~rc2-1, 1:7.0.4-3), kwin-x11:amd64 (4:5.20.4-4+b1, 4:5.20.5-1),
libhttp-cookies-perl:amd64 (6.09-1, 6.10-1), libkf5screen-bin:amd64
(4:5.20.4-2, 4:5.20.5-1), libpulse-mainloop-glib0:amd64 (13.0-5, 14.0-2),
libc6:amd64 (2.31-6, 2.31-9), locales:amd64 (2.31-6, 2.31-9), libpcap0.8:amd64
(1.9.1-4, 1.10.0-2), libreoffice-style-colibre:amd64 (1:7.0.4~rc2-1,
1:7.0.4-3), linux-image-amd64:amd64 (5.9.15-1, 5.10.4-1),
libreoffice-writer:amd64 (1:7

[plasmashell] [Bug 431440] Plasma fails to start

2021-01-11 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=431440

--- Comment #1 from Pierce  ---
I'm able to start plasmashell and kwin from within XFCE, but for whatever
reason they do not work if I try to log in to a Plasma session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 431440] Plasma fails to start

2021-01-11 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=431440

--- Comment #3 from Pierce  ---
(In reply to Nicolas Fella from comment #2)
> Can you please attach your .local/share/sddm/xorg-session.log file?

It's completely empty. Trying to log in to Plasma didn't populate it with
anything, either.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 431440] Plasma fails to start

2021-01-11 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=431440

--- Comment #5 from Pierce  ---
(In reply to Nicolas Fella from comment #4)
> Are you trying to log into a X11 or Wayland session?

X11

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 431440] Plasma fails to start

2021-01-12 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=431440

--- Comment #7 from Pierce  ---
Created attachment 134790
  --> https://bugs.kde.org/attachment.cgi?id=134790&action=edit
excerpt from .xsession-errors

I'm dumb and forgot to check ~/.xsession-errors, so here's what happens when I
tried to start a Plasma session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 431440] Plasma fails to start

2021-01-16 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=431440

Pierce  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #9 from Pierce  ---
I just installed the following upgrades:
Upgrade: dpkg:amd64 (1.20.5, 1.20.7.1), libxapian30:amd64 (1.4.17-1, 1.4.18-1),
apt:amd64 (2.1.17, 2.1.18), plasma-workspace:amd64 (4:5.20.5-1, 4:5.20.5-2),
libsensors-config:amd64 (1:3.6.0-2, 1:3.6.0-3), libx11-xcb1:amd64 (2:1.7.0-1,
2:1.7.0-2), libtaskmanager6abi1:amd64 (4:5.20.5-1, 4:5.20.5-2), tcl:amd64
(8.6.10, 8.6.11), libgps28:amd64 (3.22-1, 3.22-2), libapt-pkg6.0:amd64 (2.1.17,
2.1.18), libweather-ion7:amd64 (4:5.20.5-1, 4:5.20.5-2), ibritish:amd64
(3.4.00-8, 3.4.02-1), libavdevice58:amd64 (7:4.3.1-5, 7:4.3.1-6), ffmpeg:amd64
(7:4.3.1-5, 7:4.3.1-6), iamerican:amd64 (3.4.00-8, 3.4.02-1), libbpf0:amd64
(1:0.3-1, 1:0.3-2), python3-pyqt5:amd64 (5.15.2+dfsg-2, 5.15.2+dfsg-3),
plasma-workspace-data:amd64 (4:5.20.5-1, 4:5.20.5-2), gcc-9-base:amd64
(9.3.0-19, 9.3.0-20), libmodplug1:amd64 (1:0.8.9.0-2, 1:0.8.9.0-3),
libpostproc55:amd64 (7:4.3.1-5, 7:4.3.1-6), libx11-data:amd64 (2:1.6.12-1,
2:1.7.0-2), dpkg-dev:amd64 (1.20.5, 1.20.7.1), libasan5:amd64 (9.3.0-19,
9.3.0-20), libavcodec58:amd64 (7:4.3.1-5, 7:4.3.1-6), sddm-theme-breeze:amd64
(4:5.20.5-1, 4:5.20.5-2), ienglish-common:amd64 (3.4.00-8, 3.4.02-1),
libstdc++-9-dev:amd64 (9.3.0-19, 9.3.0-20), ispell:amd64 (3.4.00-8, 3.4.02-1),
libavutil56:amd64 (7:4.3.1-5, 7:4.3.1-6), sddm-theme-debian-breeze:amd64
(4:5.20.5-1, 4:5.20.5-2), libcolorcorrect5:amd64 (4:5.20.5-1, 4:5.20.5-2),
libimage-exiftool-perl:amd64 (12.13+dfsg-1, 12.14+dfsg-1), libswscale5:amd64
(7:4.3.1-5, 7:4.3.1-6), libxxhash0:amd64 (0.8.0-1, 0.8.0-2), libx11-dev:amd64
(2:1.6.12-1, 2:1.7.0-2), libdpkg-perl:amd64 (1.20.5, 1.20.7.1),
libgcc-9-dev:amd64 (9.3.0-19, 9.3.0-20), libsensors5:amd64 (1:3.6.0-2,
1:3.6.0-3), libswresample3:amd64 (7:4.3.1-5, 7:4.3.1-6),
plasma-desktop-data:amd64 (4:5.20.4-2, 4:5.20.5-2), socat:amd64 (1.7.3.4-1,
1.7.4.1-2), tk:amd64 (8.6.10, 8.6.11), apt-utils:amd64 (2.1.17, 2.1.18),
lm-sensors:amd64 (1:3.6.0-2, 1:3.6.0-3), unzip:amd64 (6.0-25, 6.0-26),
ruby-rubygems:amd64 (3.2.4-1, 3.2.5-2), libavformat58:amd64 (7:4.3.1-5,
7:4.3.1-6), libnotificationmanager1:amd64 (4:5.20.5-1, 4:5.20.5-2),
libkfontinstui5:amd64 (4:5.20.5-1, 4:5.20.5-2), libkfontinst5:amd64
(4:5.20.5-1, 4:5.20.5-2), libx11-6:amd64 (2:1.6.12-1, 2:1.7.0-2),
libavresample4:amd64 (7:4.3.1-5, 7:4.3.1-6),
libplasma-geolocation-interface5:amd64 (4:5.20.5-1, 4:5.20.5-2),
qml-module-org-kde-quickcharts:amd64 (5.77.0-3, 5.77.0-4),
libkworkspace5-5:amd64 (4:5.20.5-1, 4:5.20.5-2), plasma-desktop:amd64
(4:5.20.4-2, 4:5.20.5-2), libavfilter7:amd64 (7:4.3.1-5, 7:4.3.1-6)

Plasma is now working without issue. If you're missing effects like window
transparency and shadows, open up the compositor section of System Settings and
re-enable OpenGL detection, then restart kwin.

-- 
You are receiving this mail because:
You are watching all bug changes.

[QtCurve] [Bug 397686] New: Using menubar in Qt programs causes them to freeze

2018-08-20 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=397686

Bug ID: 397686
   Summary: Using menubar in Qt programs causes them to freeze
   Product: QtCurve
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: qt5
  Assignee: yyc1...@gmail.com
  Reporter: gripw...@gmail.com
CC: h...@kde.org
  Target Milestone: ---

Using the menubar in a Qt application will cause the entire application to
freeze, and has sometimes prevented me from switching to my terminal emulator
(or any other application) to kill it (killing from a TTY unfreezes
everything). I have encountered this issue with Okular, Dolphin, Kpatience, and
KolourPaint. It only occurs in Qt based applications, as I have not encountered
the problem when using Firefox, XFCEterm, or LibreOffice writer.

Steps to reproduce:
1. Open a Qt program such as Dolphin or Okular
2. Click on a menubar category (e.g. File, Edit, View, etc.)
3. Mouse over items within the category/switch to other categories in the
menubar

Actual results: the program freezes and sometimes can only be killed by
switching to a TTY

Expected results: programs should not crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[QtCurve] [Bug 397686] Using menubar in Qt programs causes them to freeze

2018-08-20 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=397686

Pierce  changed:

   What|Removed |Added

  Component|qt5 |general

-- 
You are receiving this mail because:
You are watching all bug changes.

[QtCurve] [Bug 397686] Using menubar in Qt programs causes them to freeze

2018-08-21 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=397686

--- Comment #1 from Pierce  ---
(In reply to Pierce from comment #0)
> Using the menubar in a Qt application will cause the entire application to
> freeze, and has sometimes prevented me from switching to my terminal
> emulator (or any other application) to kill it (killing from a TTY unfreezes
> everything). I have encountered this issue with Okular, Dolphin, Kpatience,
> and KolourPaint. It only occurs in Qt based applications, as I have not
> encountered the problem when using Firefox, XFCEterm, or LibreOffice writer.
> 
> Steps to reproduce:
> 1. Open a Qt program such as Dolphin or Okular
> 2. Click on a menubar category (e.g. File, Edit, View, etc.)
> 3. Mouse over items within the category/switch to other categories in the
> menubar
> 
> Actual results: the program freezes and sometimes can only be killed by
> switching to a TTY
> 
> Expected results: programs should not crash

I forgot to put this in the description, but the bug only occurs while QtCurve
is set as the current widget style in the Application Style section of the
System Preferences. I have not experienced any crashes since switching to the
Breeze widget style.

-- 
You are receiving this mail because:
You are watching all bug changes.

[QtCurve] [Bug 397686] Using menubar in Qt programs causes them to freeze

2018-08-21 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=397686

Pierce  changed:

   What|Removed |Added

  Component|general |qt5

-- 
You are receiving this mail because:
You are watching all bug changes.

[QtCurve] [Bug 397686] Using QtCurve menubar in Qt programs causes them to freeze

2018-08-21 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=397686

Pierce  changed:

   What|Removed |Added

Summary|Using menubar in Qt |Using QtCurve menubar in Qt
   |programs causes them to |programs causes them to
   |freeze  |freeze

-- 
You are receiving this mail because:
You are watching all bug changes.

[QtCurve] [Bug 397686] Using QtCurve menubar in Qt programs causes them to freeze

2018-08-22 Thread Pierce
https://bugs.kde.org/show_bug.cgi?id=397686

Pierce  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Pierce  ---
I have been unable to reproduce the bug after installing today's (22 August
2018) updates to qtcurve packages.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 440397] Plasma fails to launch with Wayland and NVidia (kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface failed")

2023-05-21 Thread Marshall Pierce
https://bugs.kde.org/show_bug.cgi?id=440397

Marshall Pierce  changed:

   What|Removed |Added

 CC||k...@contact.mpierce.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login

2022-10-06 Thread Tyler Pierce
https://bugs.kde.org/show_bug.cgi?id=427861

Tyler Pierce  changed:

   What|Removed |Added

 CC||tyl...@praxisnine.com

--- Comment #117 from Tyler Pierce  ---
Have been experiencing (I think) this same bug every re-boot since receiving
pinephone pro completely updated I think:

KDE Plasma Version: 5.25.5
KDE Framework Version: 5.98.0
QT Version: 5.15.6
Kernel Version: 5.19.11-1-MANJARO-ARM

The behavior is sometimes after returning from a locked screen all icons have
moved to the upper left of the desktop over top of each other and sometimes
widgets resize slightly. But the main thing is on every re-boot it resets to
the original factory desktop wallpaper/icons/widgets(none).

Happy to add any info that may help investigation

-- 
You are receiving this mail because:
You are watching all bug changes.