Hi
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Hi
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
Your following your signature seems to have :
Qt: 5.7.1 KDE Frameworks: 5.30.0 KDE Plasma: 5.8.95 kwin5-5.8.95-174.1.x86_64
I've not hanging desktop, no panel freeze, and akonadi is working.
On Tuesday, 17 January 2017 13:50:10 GMT Bruno Friedmann wrote:
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Hi
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
Your following your signature seems to have :
Qt: 5.7.1 KDE Frameworks: 5.30.0 KDE Plasma: 5.8.95 kwin5-5.8.95-174.1.x86_64
I've not hanging desktop, no panel freeze, and akonadi is working.
Mmmm i'll check that, thanks
On 17 January 2017 at 13:50, Bruno Friedmann bruno@ioda-net.ch wrote:
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
I don't think it is because I have the exact same package versions as those and the exact same symptoms described above.
Cheers, JFL
On Tuesday, 17 January 2017 14:09:33 GMT J. F. Lemaire wrote:
On 17 January 2017 at 13:50, Bruno Friedmann bruno@ioda-net.ch wrote:
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
I don't think it is because I have the exact same package versions as those and the exact same symptoms described above.
Cheers, JFL
I forgot to add --no-allow-vendor-change and its downgraded everything to the correct levels and the hanging panel/desktop seems to have stopped although i'm still occasionally having it hang during a log in.
On mardi, 17 janvier 2017 16.14:50 h CET ianseeks wrote:
On Tuesday, 17 January 2017 14:09:33 GMT J. F. Lemaire wrote:
On 17 January 2017 at 13:50, Bruno Friedmann bruno@ioda-net.ch wrote:
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
I don't think it is because I have the exact same package versions as those and the exact same symptoms described above.
Cheers, JFL
I forgot to add --no-allow-vendor-change and its downgraded everything to the correct levels and the hanging panel/desktop seems to have stopped although i'm still occasionally having it hang during a log in.
then the hang is probably (but I've no science clue here) due to nouveau. I'm using the proprietary blob (my quadro being not that known to nouveau yet) and I don't see any hang during a working session.
On Tuesday, 17 January 2017 17:39:20 GMT Bruno Friedmann wrote:
On mardi, 17 janvier 2017 16.14:50 h CET ianseeks wrote:
On Tuesday, 17 January 2017 14:09:33 GMT J. F. Lemaire wrote:
On 17 January 2017 at 13:50, Bruno Friedmann bruno@ioda-net.ch wrote:
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
I don't think it is because I have the exact same package versions as those and the exact same symptoms described above.
Cheers, JFL
I forgot to add --no-allow-vendor-change and its downgraded everything to the correct levels and the hanging panel/desktop seems to have stopped although i'm still occasionally having it hang during a log in.
then the hang is probably (but I've no science clue here) due to nouveau. I'm using the proprietary blob (my quadro being not that known to nouveau yet) and I don't see any hang during a working session.
I suspected that as well as my graphics card starts beeping like mad at times, i think i should start looking at buying a radeon or similar
On Tuesday, 17 January 2017 17:39:20 GMT Bruno Friedmann wrote:
On mardi, 17 janvier 2017 16.14:50 h CET ianseeks wrote:
On Tuesday, 17 January 2017 14:09:33 GMT J. F. Lemaire wrote:
On 17 January 2017 at 13:50, Bruno Friedmann bruno@ioda-net.ch wrote:
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
I don't think it is because I have the exact same package versions as those and the exact same symptoms described above.
Cheers, JFL
I forgot to add --no-allow-vendor-change and its downgraded everything to the correct levels and the hanging panel/desktop seems to have stopped although i'm still occasionally having it hang during a log in.
then the hang is probably (but I've no science clue here) due to nouveau. I'm using the proprietary blob (my quadro being not that known to nouveau yet) and I don't see any hang during a working session.
I tell a lie, my panel has just hung again........
Bruno Friedmann wrote:
On mardi, 17 janvier 2017 16.14:50 h CET ianseeks wrote:
On Tuesday, 17 January 2017 14:09:33 GMT J. F. Lemaire wrote:
On 17 January 2017 at 13:50, Bruno Friedmann bruno@ioda-net.ch wrote:
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
I don't think it is because I have the exact same package versions as those and the exact same symptoms described above.
Cheers, JFL
I forgot to add --no-allow-vendor-change and its downgraded everything to the correct levels and the hanging panel/desktop seems to have stopped although i'm still occasionally having it hang during a log in.
then the hang is probably (but I've no science clue here) due to nouveau.
I was also using nouveau for a while, with both 421 and 422, always had hangs.
I'm using the proprietary blob (my quadro being not that known to nouveau yet) and I don't see any hang during a working session.
For the time being, I've blacklisted nouveau - graphics are slooooow, so I'll switch to the nvidia supplied driver soon.
On mardi, 17 janvier 2017 16.14:50 h CET ianseeks wrote: then the hang is probably (but I've no science clue here) due to nouveau.
I'm on intel graphics and I experience the random freezes too.
Cheers, JFL
On Wed, Jan 18, 2017 at 10:15 AM, J. F. Lemaire jflemaire@skynet.be wrote:
On mardi, 17 janvier 2017 16.14:50 h CET ianseeks wrote: then the hang is probably (but I've no science clue here) due to nouveau.
I'm on intel graphics and I experience the random freezes too.
Cheers, JFL -- Jean-François Lemaire
No issue with AMD radeon here so probably it is not consistent.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Per Jessen composed on 2017-01-18 08:36 (UTC+0100):
I was also using nouveau for a while, with both 421 and 422, always had hangs.
For the time being, I've blacklisted nouveau - graphics are slooooow, so I'll switch to the nvidia supplied driver soon.
Slow using which Xorg driver?
nouveau(0)?
vesa(0)?
fbdev(0)?
modeset(0)?
Felix Miata wrote:
Per Jessen composed on 2017-01-18 08:36 (UTC+0100):
I was also using nouveau for a while, with both 421 and 422, always had hangs.
For the time being, I've blacklisted nouveau - graphics are slooooow, so I'll switch to the nvidia supplied driver soon.
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
Per Jessen composed on 2017-01-18 12:34 (UTC+0100):
Felix Miata wrote:
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
Whichever one you see abundant repeats of in Xorg.0.log, especially if it's on any lines that contain the string "onnected".
Felix Miata wrote:
Per Jessen composed on 2017-01-18 12:34 (UTC+0100):
Felix Miata wrote:
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
Whichever one you see abundant repeats of in Xorg.0.log, especially if it's on any lines that contain the string "onnected".
No such line, but plenty with VESA listed.
Per Jessen composed on 2017-01-18 17:32 (UTC+0100):
Felix Miata wrote:
Per Jessen composed on 2017-01-18 12:34 (UTC+0100):
Felix Miata wrote:
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
Whichever one you see abundant repeats of in Xorg.0.log, especially if it's on any lines that contain the string "onnected".
No such line, but plenty with VESA listed.
VESA is creepy crawly slow. Could it be that you're running 13.2 and xf86-video-modesetting needs to be installed.
If TW, 42.1 or 42.2, what is the output from 'lspci -nnk | grep -A5 VGA'?
If TW, what is the output from 'rpm -qa | grep x11-server'?
Felix Miata wrote:
Per Jessen composed on 2017-01-18 17:32 (UTC+0100):
Felix Miata wrote:
Per Jessen composed on 2017-01-18 12:34 (UTC+0100):
Felix Miata wrote:
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
Whichever one you see abundant repeats of in Xorg.0.log, especially if it's on any lines that contain the string "onnected".
No such line, but plenty with VESA listed.
VESA is creepy crawly slow.
Sounds like what I'm seeing.
Could it be that you're running 13.2 and xf86-video-modesetting needs to be installed.
Nope, this is leap422.
If TW, 42.1 or 42.2, what is the output from 'lspci -nnk | grep -A5 VGA'?
# lspci -nnk | grep -A5 VGA 60:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84GL [Quadro FX 1700] [10de:040f] (rev a1) Subsystem: NVIDIA Corporation Device [10de:049a] Kernel modules: nouveau
Per Jessen composed on 2017-01-18 18:33 (UTC+0100):
Felix Miata wrote:
Per Jessen composed on 2017-01-18 17:32 (UTC+0100):
Felix Miata wrote:
Per Jessen composed on 2017-01-18 12:34 (UTC+0100):
Felix Miata wrote:
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
Whichever one you see abundant repeats of in Xorg.0.log, especially if it's on any lines that contain the string "onnected".
No such line, but plenty with VESA listed.
VESA is creepy crawly slow.
Sounds like what I'm seeing.
Could it be that you're running 13.2 and xf86-video-modesetting needs to be installed.
Nope, this is leap422.
If TW, 42.1 or 42.2, what is the output from 'lspci -nnk | grep -A5 VGA'?
# lspci -nnk | grep -A5 VGA 60:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84GL [Quadro FX 1700] [10de:040f] (rev a1) Subsystem: NVIDIA Corporation Device [10de:049a] Kernel modules: nouveau
Looks like it may be just a wee bit too ancient, at 9 years of age[1], for modeset(0) support, leaving you stuck with what you have unless you install the non-free driver or un-blacklist nouveau, which is disappointing, as my 8 month older G84 (GeForce 8600GT[2]) _is_ supported by modeset(0).
[1] http://en.wikipedia.org/wiki/Nvidia_Quadro [2] http://en.wikipedia.org/wiki/GeForce_8_series
Felix Miata wrote:
# lspci -nnk | grep -A5 VGA 60:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84GL [Quadro FX 1700] [10de:040f] (rev a1) Subsystem: NVIDIA Corporation Device [10de:049a] Kernel modules: nouveau
Looks like it may be just a wee bit too ancient, at 9 years of age[1], for modeset(0) support, leaving you stuck with what you have unless you install the non-free driver or un-blacklist nouveau,
nouveau isn't workable, keeps crashing sddm. I'll most likely just use the nvidia driver. It's mostly a test system. Thanks for your input.
Per Jessen composed on 2017-01-19 09:42 (UTC+0100):
nouveau isn't workable, keeps crashing sddm. I'll most likely just use the nvidia driver. It's mostly a test system. Thanks for your input.
It might be worth waiting to see if the soon upgrade to server 1.19.1 stops the crashing. Another option is switching to a different dm, maybe lightdm or kdm. I use only KDM, KDM3 or TDM, according to which primary DE I have installed.
Per Jessen [18.01.2017 12:34]:
Felix Miata wrote:
Per Jessen composed on 2017-01-18 08:36 (UTC+0100):
I was also using nouveau for a while, with both 421 and 422, always had hangs.
For the time being, I've blacklisted nouveau - graphics are slooooow, so I'll switch to the nvidia supplied driver soon.
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
For this purpose I most often use "hwinfo --gfxcard", it shows the current driver and some hardware details. The hwinfo binary ist installed on openSUSE by default, AFAIK.
Werner
Werner Flamme wrote:
hwinfo --gfxcard
# hwinfo --gfxcard 10: PCI 6000.0: 0300 VGA compatible controller (VGA) [Created at pci.378] Unique ID: aN6P.rptl+piHXt5 Parent ID: 3hqH.Kq_ZpDse9qC SysFS ID: /devices/pci0000:00/0000:00:03.0/0000:60:00.0 SysFS BusID: 0000:60:00.0 Hardware Class: graphics card Model: "nVidia Quadro FX 1700" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x040f "Quadro FX 1700" SubVendor: pci 0x10de "nVidia Corporation" SubDevice: pci 0x049a Revision: 0xa1 Memory Range: 0xf2000000-0xf2ffffff (rw,non-prefetchable) Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable) Memory Range: 0xf0000000-0xf1ffffff (rw,non-prefetchable) I/O Ports: 0x1000-0x1fff (rw) IRQ: 3 (no events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v000010DEd0000040Fsv000010DEsd0000049Abc03sc00i00" Driver Info #0: XFree86 v4 Server Module: nv Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #13 (PCI bridge)
Primary display adapter: #10
Werner Flamme composed on 2017-01-18 18:11 (UTC+0100):
Per Jessen composed:
Felix Miata wrote:
Per Jessen composed on 2017-01-18 08:36 (UTC+0100):
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
For this purpose I most often use "hwinfo --gfxcard", it shows the current driver and some hardware details. The hwinfo binary ist installed on openSUSE by default, AFAIK.
That only reports the kernel driver in use, not the Xorg driver, as it works from any terminal even when neither Xorg nor Wayland are running.
On Wed, 2017-01-18 at 12:38 -0500, Felix Miata wrote:
That only reports the kernel driver in use, not the Xorg driver, as it works from any terminal even when neither Xorg nor Wayland are running.
The most reliable way I know of:
grep -P "(L|Unl)oading" /var/log/Xorg.0.log
then compare which driver gets loaded vs the unloaded once. The one the remains loaded is the one in use.
Per Jessen a következőt írta ekkor: 2017. január 18., szerda 12:34:49 CET
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
# inxi -G Graphics: Card: Intel Crystal Well Integrated Graphics Controller Display Server: X.org 1.19.1 drivers: intel (unloaded: modesetting,fbdev,vesa) tty size: 151x41 Advanced Data: N/A for root out of X
Have found only in the utilties repo.
Kapcsándi István composed on 2017-01-18 19:44 (UTC+0100):
# inxi -G
How does one get output from that redirected to a file that isn't littered with ANSI strings? I find no man page for it, and don't see any way in --help to get simple text output. Color schemes don't seem to be defeatable. :-(
On Wed, 18 Jan 2017, Felix Miata wrote:
... Color schemes don't seem to be defeatable.
:-(
In .bashrc I added
# Remove colour codes from ascii # See http://misc.flogisoft.com/bash/tip_colors_and_formatting for codes # See https://unix.stackexchange.com/questions/55546/removing-color-codes-from-out... for sed alias no-color='sed "s/\x1B[[0-9;]*[JKmsu]//g"' alias no-colour='sed "s/\x1B[[0-9;]*[JKmsu]//g"'
I pipe the inxi outup through no-colo(u)r to remove the colo(u)rs.
Roger
Felix Miata a következőt írta ekkor: 2017. január 18., szerda 14:12:51 CET
Kapcsándi István composed on 2017-01-18 19:44 (UTC+0100):
# inxi -G
How does one get output from that redirected to a file that isn't littered with ANSI strings? I find no man page for it, and don't see any way in --help to get simple text output. Color schemes don't seem to be defeatable. :-(
Found in the -h(elp): -c Color schemes. Scheme number is required. Color selectors run a color selector option prior to inxi
Try w/ -c 0: # inxi -G -c 0
On Wed, 18 Jan 2017 19:44:35 +0100, Kapcsándi István istvan.kapcsandi@gmail.com wrote:
Per Jessen a következőt írta ekkor: 2017. január 18., szerda 12:34:49 CET
Slow using which Xorg driver?
nouveau(0)?
Blacklisted.
vesa(0)? fbdev(0)? modeset(0)?
How do I determine which one is in use?
# inxi -G Graphics: Card: Intel Crystal Well Integrated Graphics Controller Display Server: X.org 1.19.1 drivers: intel (unloaded: modesetting,fbdev,vesa) tty size: 151x41 Advanced Data: N/A for root out of X
Have found only in the utilties repo.
Nice! though it produces illegible output on xterm with black on light-gray
Graphics: Card: Advanced Micro Devices [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] Display Server: X.Org 1.16.1 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa) Resolution: 1920x1200@59.95hz GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) GLX Version: 3.0 Mesa 13.0.3
Likely to up tomorrow to the new 4.9.3 kernel
On Wed, 18 Jan 2017 22:07:10 +0100, "H.Merijn Brand" h.m.brand@xs4all.nl wrote:
Likely to up tomorrow to the new 4.9.3 kernel
Linux 4.9.3-1-default [openSUSE Tumbleweed 20170117] HP EliteBook 8560p/1618 Core(TM) i7-2620M CPU @ 2.70GHz/3307(4) x86_64 7933 Mb
Graphics: Card: Advanced Micro Devices [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] Display Server: X.Org 1.19.0 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa) Resolution: 1600x900@60.00hz GLX Renderer: Gallium 0.4 on AMD CAICOS (DRM 2.48.0 / 4.9.3-1-default, LLVM 3.9.1) GLX Version: 3.0 Mesa 13.0.3
All working as expected!
kwin5-5.8.5-1.1.x86_64 plasma5-desktop-5.8.5-2.1.x86_64 xf86-video-ati-7.8.0-1.2.x86_64 xorg-x11-7.6_1-16.2.noarch xorg-x11-server-1.19.0-1.1.x86_64
On 01/18/17 09:36, Per Jessen wrote:
Bruno Friedmann wrote:
On mardi, 17 janvier 2017 16.14:50 h CET ianseeks wrote:
On Tuesday, 17 January 2017 14:09:33 GMT J. F. Lemaire wrote:
On 17 January 2017 at 13:50, Bruno Friedmann bruno@ioda-net.ch wrote:
On mardi, 17 janvier 2017 11.35:14 h CET ianseeks wrote:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Aren't your that's not the mixed repositories you have ?
A TW of the day has Qt: 5.7.1, KDE Frameworks: 5.29.0, Plasma: 5.8.5, kwin5: 5.8.5
I don't think it is because I have the exact same package versions as those and the exact same symptoms described above.
Cheers, JFL
I forgot to add --no-allow-vendor-change and its downgraded everything to the correct levels and the hanging panel/desktop seems to have stopped although i'm still occasionally having it hang during a log in.
then the hang is probably (but I've no science clue here) due to nouveau.
I was also using nouveau for a while, with both 421 and 422, always had hangs.
I'm using the proprietary blob (my quadro being not that known to nouveau yet) and I don't see any hang during a working session.
For the time being, I've blacklisted nouveau - graphics are slooooow, so I'll switch to the nvidia supplied driver soon.
TW latest release: using XFCE , and running Ktorrent
the fonts of Ktorrent have gone tiny and am unable to find method to increase font size .
........
Il giorno Tue, 17 Jan 2017 11:35:14 +0000 ianseeks bingmybong@btinternet.com ha scritto:
Hi
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
As stated in the other thread (not only for you, but all those who follow up): the freeze only occurs with DRI2 and is caused by an Xorg bug: https://bugs.freedesktop.org/show_bug.cgi?id=99333
It doesn't occur on all systems (on my TW install at work, always; here at home, never).
It has been already fixed, and packages are in the queue for TW, so it will arrive sooner or later.
As a workaround, you may want to try enabling DRI3 (beware, that may cause other issues) for your driver.
On Tuesday, 17 January 2017 20:15:13 GMT Luca Beltrame wrote:
Il giorno Tue, 17 Jan 2017 11:35:14 +0000
ianseeks bingmybong@btinternet.com ha scritto:
Hi
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
As stated in the other thread (not only for you, but all those who follow up): the freeze only occurs with DRI2 and is caused by an Xorg bug: https://bugs.freedesktop.org/show_bug.cgi?id=99333
It doesn't occur on all systems (on my TW install at work, always; here at home, never).
It has been already fixed, and packages are in the queue for TW, so it will arrive sooner or later.
As a workaround, you may want to try enabling DRI3 (beware, that may cause other issues) for your driver.
Thanks . Found that when it fails to log in, kwin_x11 is running at 100% (and more) so it looks like a hang I'll be patient, it took me 4 times to get to a desktop this morning
ianseeks writes:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start...
It's been posted before, the reason for your troubles is probably this: https://bugzilla.opensuse.org/show_bug.cgi?id=1020146
Ctrl Backspace Backspace is your friend at the moment :)
Restarting plasmashell and akonadi worked for me.
Regards, Achim.
On Tuesday, 17 January 2017 20:15:19 GMT Achim Gratz wrote:
ianseeks writes:
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start...
It's been posted before, the reason for your troubles is probably this: https://bugzilla.opensuse.org/show_bug.cgi?id=1020146
Ctrl Backspace Backspace is your friend at the moment :)
Restarting plasmashell and akonadi worked for me.
Regards, Achim.
Thanks.
Am Dienstag, 17. Januar 2017, 11:35:14 CET schrieb ianseeks:
Hi
Panel hanging then desktop hanging, sometimes hangs on login, akonadi doesn't always start... Ctrl Backspace Backspace is your friend at the moment :)
Panel freezes,
killall plasmashell kstart plasmashell
helps.
Starting Emacs _always_ crashes the panel. However, Emacs starts.
BTW, to avoid a translation error: panel is »Kontrollleiste« in German, isn't it?
Regards,
Alexander
-
Achim Gratz -
AW -
Bruno Friedmann -
Dominique Leuenberger / DimStar -
ellanios82 -
Felix Miata -
H.Merijn Brand -
ianseeks -
J. F. Lemaire -
Kapcsándi István -
Luca Beltrame -
Per Jessen -
Roger Price -
Stratos Zolotas -
Werner Flamme