[filelight] [Bug 370932] File light scans into "do not scan" folders that end with a /

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370932

Eric S  changed:

   What|Removed |Added

Summary|File light scans into "do   |File light scans into "do
   |not scan" folders   |not scan" folders that end
   ||with a /

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

[filelight] [Bug 370932] File light scans into "do not scan" folders

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370932

--- Comment #1 from Eric S  ---
Actually I just discovered the problem. All the folders listed in my Do not
scan list ended with a /. E.g. /home/ericjs/stuff/. I tried deleting and
re-adding a folder, and it was added without a terminating /, like
"/home/ericjs/stuff". Rescanning resulted in this directory properly being
ignored. I'm pretty sure these folders had a terminating / because that is how
a previous version of Filelight created them (I certainly wouldn't have added
such a slash myself). So this would seem to be a backwards compatibility issue.

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

[filelight] [Bug 370932] New: File light scans into "do not scan" folders

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370932

Bug ID: 370932
   Summary: File light scans into "do not scan" folders
   Product: filelight
   Version: 1.21
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: subscri...@blackbrook.org

Folders that I have listed in "Do not scan these folders:" in the configuration
show up in my scan. 

Reproducible: Always




I'm pretty sure this used to work. I can't tell you what version as I haven't
run it in a while.

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

[frameworks-ktexteditor] [Bug 335079] Text rendering broken for unicode characters

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=335079

--- Comment #24 from Eric S  ---
Isn't the underlying problem here the painting of text using an opaque
background? Wouldn't it be better painting it with a transparent background
(mask or such)?

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

[kate] [Bug 353404] My kate version is not listed in the possible versions.

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353404

--- Comment #3 from Eric S  ---
Forgive me if I'm reading too much into that replybut is there an implied
"...therefore we don't / won't do it?" 

Isn't updating the bug tracking system with the new version simply a standard
part of the release process?  Isn't it among the most basic things developers
should do to maintain the most basic level of professionalism? Or is this bug
system deprecated and some other one meant to be used for Kate? Or is Kate
essentially an unmaintained project? I'm really struggling to make sense of
this...

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

[kate] [Bug 353404] My kate version is not listed in the possible versions.

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353404

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #1 from Eric S  ---
I just noticed the same thing. This seems to be very much a WTF kind of thing
and was reported 6 months ago. Is it too much to expect someone to reply to
this?

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

[kate] [Bug 362271] New: Font Horizontal space rendering is incorrect

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362271

Bug ID: 362271
   Summary: Font Horizontal space rendering is incorrect
   Product: kate
   Version: 3.14.3
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: subscri...@blackbrook.org

If I change the font preference to use a compressed font (like Open Sans
Condensed) and compare vs the regular version of the font (like Open Sans), the
compressed version appears spaced out WIDER than the normal. The little font
preview window does it correctly, but when you actually apply it to the editing
window you get this inverse-compression effect. You can see this most
dramatically with a set of fonts like Input Mono (http://input.fontbureau.com/)
which has several different levels of compression, and Kate renders them all in
inverse proportion to how they should be.

I know this sounds bizarre, but I get this happening consistently for several
fonts, and only Kate does this wrong, other applications do it correctly.

BTW the version my Kate reports bear no resemblance to anything I'm offered in
the version dropdown here. It reports:

Version 15.12.3
Using:
KDE Frameworks 5.21.0
Qt 5.6.0 (built against 5.6.0)
The xcb windowing system

Reproducible: Always

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

[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361567

--- Comment #7 from Eric S  ---
I should note that this is a laptop with a 1600 x 900 screen, and I often use
it with an external 1920x1200 monitor. It looks similar on either screen.

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

[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361567

--- Comment #5 from Eric S  ---
Created attachment 98379
  --> https://bugs.kde.org/attachment.cgi?id=98379=edit
Here is what my screen looks like; 1920 x 1200 screen

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

[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361567

--- Comment #4 from Eric S  ---
Also I disagree that the "Huh, where did my window go?"  use case is one that
justifies something that will be in the screen at all times (and certainly not
as something you cannot disable and is on by default). If you have icon
grouping enabled, having multiple windows grouped (not hidden) under the icon
is routine...no one is going to have much more than a fleeting single "Huh,
where did my window go?"  experience when they are a completely new to it. It
adds unnecessary clutter for the majority of cases for a single edge case.

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

[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361567

--- Comment #3 from Eric S  ---
My panel is not that tiny. And believe me, my eyes are not that great, I'm not
someone who has his screen with everything set really fine.  I suspect there is
some additional element of screen geometry or something at play. I'll see if
there are any specific numbers I can report about my configuration. If you have
any suggestions where to get some useful numbers, please let me know.

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

[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361567

--- Comment #1 from Eric S  ---
It would be wonderful if there were some way to simply turn off this feature.
This is a new feature that, in my opinion, is really not in any way useful,
even if it worked properly. One only looks at the Task bar if one is about to
use it, and by using it immediately finds out how many windows the icon is
grouping. Knowing ahead of that click is not really of any benefit that I can
see.

I really cannot imagine a case where I would glance at the bar to find out how
many windows an application has open. And if there is such a use case it is
rare enough that it does not warrant having this icon present all the time. So
actually a good fix for this would be to simply remove this feature entirely.

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

[kio] [Bug 269370] ftp network folder in dolphin does not honor codepage for filenames

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=269370

--- Comment #11 from Eric S  ---
(In reply to Eric S from comment #10)
> I'm going to open(In reply to Jan Dosoudil from comment #9)
> > (In reply to Eric S from comment #7)
> > > I find there are other problems with beyond-ASCII characters in dolphin 
> > > over
> > > fish. I have a file with the registered trademark symbol in the name (®). 
> > > It
> > > appears correctly in dolphin over fish, however I cannot open in Dolphin,
> > > nor can I copy it from dolphin. It does not matter if I explicitly Select
> > > UTF-8 as the remote charset. 
> > > 
> > > Note that this worked fine with the version of Dolphin under plasma 4.
> > 
> > I have exactly same problem -- files with Czech characters (UTF-8 encoding)
> > doesn't open in Dolphin 5.x over fish.
> 
> I'm going to open another issue for this. I'm guessing this is not being
> seen because it is v4.9.4 issue.

Actually, there are no 5.x version offered for kio when reporting a bug here.
WTF? Is the system just out of date or kio considered part of some other
component now in Plasma 5?

Also I'm not sure this issue (at least going by the title) is the right one for
my and Jan Dosoudil's problem, that fish: cannot open, copy, rename, etc files
with non-latin characters in their name. Searching in the bug system for
characters under kio there are a whole host of problems with characters beyond
ascii but the bugs all seem to be specific in ways that don't necessarily
encompass this problem. So I still suspect we need to file another bug, but
it's not entirely clear where.

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

[Breeze] [Bug 361567] New: task bar icon for multiple window grouping obscures application icons

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361567

Bug ID: 361567
   Summary: task bar icon for multiple window grouping obscures
application icons
   Product: Breeze
   Version: 5.6.1
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: subscri...@blackbrook.org
CC: kain...@gmail.com

Task bar Icon indicating more than one window is being groups almost entirely
obscures the application icon. With the current version I find only a tiny
sliver of the app icon is visible, which is a big impediment to useabilty. 

See also this discussion:
https://forum.kde.org/viewtopic.php?f=17=130682

Reproducible: Always

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

[plasmashell] [Bug 348514] Device Notifier missing KDE 4 actions

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348514

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #1 from Eric S  ---
Maybe this is distro-specific but all my actions from kde4 are in
/usr/share/apps/solid/actions.

It seems to me one solution or workaround might be distros handled this. KDE
ought to highlight the need for this to the distros in some info prominently
provided to them when they get the Plasma 5 sources.

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

[KScreen] [Bug 355528] Multiple monitor support is erratic

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355528

--- Comment #9 from Eric S  ---
Also, it's frustrating not to be able to vote for this.

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

[plasma4] [Bug 310156] Windows go below when "Always visible" is set and using multihead

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=310156

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #9 from Eric S  ---
Still happening in Plasma 5.5.3. Btw this seems to have been fixed in Plasma
4...it worked properly in the last several versions I'd used. 

Could someone update the product and version fields to reflect that? Or does
this need to be refiled for Plamsa 5?

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

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348043

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #14 from Eric S  ---
This is still the case in Plasma 5.5.3. Shouldn't someone update the version?

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

[plasma4] [Bug 310156] Windows go below when "Always visible" is set and using multihead

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=310156

--- Comment #10 from Eric S  ---
Oops, nevermind, there already is a Plasma 5 version of this: 348043

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

[Breeze] [Bug 357726] volume indicator and wifi quality are too hard to read

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357726

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #1 from Eric S  ---
I second this! And it is still the case with 5.5.3.

This flaw does falls out of the decision to make such icons monochrome in
breeze. I'm not fond of that at all.

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

[kde] [Bug 349266] System hang when put to sleep

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349266

--- Comment #7 from Eric S  ---
Having "Component: general, Version: unspecified" isn't a great way to get
anyone's attention.

I know you're not using Arch, but have a look at this thread where someone had
similar symptoms. It might give you some ideas on how to diagnose the problem. 

https://bbs.archlinux.org/viewtopic.php?id=185731

This may not even be a KDE issue, you might have better luck starting in your
distro's forums.

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

[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #41 from Eric S  ---
I'd like to suggest that as far as the Application Launcher window goes, it
seems to me it would make the most sense if this window just expanded
vertically until it either did not need a scrollbar or has reached the height
of the desktop. This would be better than making it resizeable.

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

[dolphin] [Bug 356762] New: crash while selecting files using mouse drag

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356762

Bug ID: 356762
   Summary: crash while selecting files using mouse drag
   Product: dolphin
   Version: 15.08.3
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: subscri...@blackbrook.org

Application: dolphin (15.08.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.6-1-CHAKRA x86_64
Distribution: "Chakra"

-- Information about the crash:
It crashes when I select file with a mouse drag. In this case the file are not
in the top level folder of the view (i.e. it shows a tree, and these files a
few levels down) and in the course of the drag I cause the window to scroll.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5f08a47800 (LWP 18156))]

Thread 3 (Thread 0x7f5ef33e5700 (LWP 18157)):
#0  0x7f5f0845b18d in poll () from /usr/lib/libc.so.6
#1  0x7f5efd1bbae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f5efd1bd757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f5ef4b04329 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f5f03250b7e in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f5f0130a464 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f5f0846412d in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f5eebf53700 (LWP 18158)):
#0  0x7f5f084706af in __libc_enable_asynccancel () from /usr/lib/libc.so.6
#1  0x7f5f0845b182 in poll () from /usr/lib/libc.so.6
#2  0x7f5efd6a9ca4 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7f5efd6a9dbc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f5f034885ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7f5f0342f5ba in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7f5f0324bbd4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7f5f03250b7e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f5f0130a464 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f5f0846412d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f5f08a47800 (LWP 18156)):
[KCrash Handler]
#6  0x7f5efab4c2b9 in mdb_txn_abort () from /usr/lib/liblmdb.so
#7  0x7f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so
#8  0x7f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so
#9  0x7f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so
#10 0x7f5eff5bca37 in Baloo::Database::open(Baloo::Database::OpenMode) ()
from /usr/lib/libKF5BalooEngine.so.5
#11 0x7f5f05ace576 in Baloo::File::load() () from /usr/lib/libKF5Baloo.so.5
#12 0x7f5f06069e96 in ?? () from /usr/lib/libKF5BalooWidgets.so.5
#13 0x7f5f03461231 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#14 0x7f5f03d2298c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#15 0x7f5f03d27e66 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#16 0x7f5f03431beb in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#17 0x7f5f03433fe6 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#18 0x7f5f03488183 in ?? () from /usr/lib/libQt5Core.so.5
#19 0x7f5efd6a9a1d in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#20 0x7f5efd6a9d08 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x7f5efd6a9dbc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#22 0x7f5f0348858f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#23 0x7f5f0342f5ba in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#24 0x7f5f0343757c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#25 0x7f5f0877d0c4 in kdemain () from /usr/lib/libkdeinit5_dolphin.so
#26 0x7f5f0839b610 in __libc_start_main () from /usr/lib/libc.so.6
#27 0x00400789 in _start ()

Reported using DrKonqi

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

[plasmashell] [Bug 334923] Kicker menu not correctly resizing

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=334923

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #11 from Eric S  ---
I'd just like to suggest that talking about this stuff in terms of kickoff,
kicker, etc isn't friendly to general users of Plasma. Plasma does not present
these names to the user. Plasma presents them as "Application Launcher" etc. I
have enough history with KDE to have some idea of what is being talked about
but frankly I can never remember the difference between the similarly named
kickoff and kicker. A new user would no idea. I'd like to suggest that the
names used in the issue system and discussions be harmonized with the
terminology used by the user interface.

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

[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #32 from Eric S  ---
I'd just like to comment that while many of Blackpaw's bitter comments are very
unconstructive, they do reflect the fact that a certain amount of community
good will does gets burned away when a "reboot" like Plasma 5 or KDE 4 happen,
and it's probably worth thinking about ways to ameliorate that (much bigger
discussion than belongs here). 

Personally I only have tinges of irritation about the backward steps taken in
Plasma 5, but Eike's comments actually make me feel better, as showing that the
KDE devs really do care. Thanks, Eike, for your calm and well considered
responses here.

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

[konsole] [Bug 356482] New: crash on closing help window

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356482

Bug ID: 356482
   Summary: crash on closing help window
   Product: konsole
   Version: 15.08.0
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: subscri...@blackbrook.org

Application: konsole (15.08.0)

Qt Version: 5.5.1
Operating System: Linux 4.2.6-1-CHAKRA x86_64
Distribution: "Chakra"

-- Information about the crash:
closed help window I'd opened from Konsole and Konsole crashed. Tried to
suggest this a possibly tied to 352099 but "Suggest this crash is related"
button that Ui apparently doesn't work either.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#6  0x7fc032c3846f in
QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*) () from
/usr/lib/libQt5XcbQpa.so.5
#7  0x7fc032c235fb in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /usr/lib/libQt5XcbQpa.so.5
#8  0x7fc032c23b23 in QXcbConnection::processXcbEvents() () from
/usr/lib/libQt5XcbQpa.so.5
#9  0x7fc0425c5231 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#10 0x7fc042e8698c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#11 0x7fc042e8be66 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#12 0x7fc042595beb in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#13 0x7fc042597fe6 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#14 0x7fc0425ec183 in ?? () from /usr/lib/libQt5Core.so.5
#15 0x7fc03c473a1d in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#16 0x7fc03c473d08 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x7fc03c473dbc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#18 0x7fc0425ec58f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#19 0x7fc0425935ba in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#20 0x7fc04259b57c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#21 0x7fc045cd929b in kdemain () from /usr/lib/libkdeinit5_konsole.so
#22 0x7fc045934610 in __libc_start_main () from /usr/lib/libc.so.6
#23 0x00400789 in _start ()

Possible duplicates by query: bug 356252, bug 355764, bug 355612, bug 355221,
bug 353605.

Reported using DrKonqi

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

[kio] [Bug 269370] ftp network folder in dolphin does not honor codepage for filenames

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=269370

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #7 from Eric S  ---
I find there are other problems with beyond-ASCII characters in dolphin over
fish. I have a file with the registered trademark symbol in the name (®). It
appears correctly in dolphin over fish, however I cannot open in Dolphin, nor
can I copy it from dolphin. It does not matter if I explicitly Select UTF-8 as
the remote charset. 

Note that this worked fine with the version of Dolphin under plasma 4.

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

[kde] [Bug 349266] System hang when put to sleep

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349266

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #4 from Eric S  ---
I see something like this sometimes. It may have something to do with processes
running in a console (Konsole). With Plasma4 I could sleep the system with
processes running in console windows with no problem. Now, I think it prompts
me to kills them. I've believe I've have this happen in conjunction with
multi-monitor issues such that I never see the prompt issues.

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

[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=323230

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #30 from Eric S  ---
> I have the same exact problem with kde5 with manjaro, dual monitor. Never had 
> something 
> similar while using kde4...

Ditto here, with Chakra. Wasn't a problem with Plasma 4.

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

[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup

[Eric S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=323230

--- Comment #31 from Eric S  ---
Could someone please change the Product to plasmashell on this issue since
people are confirming this as existing (or even worse) in Plasma 5? Or do we
need to open a new issue?

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