[systemsettings] [Bug 457899] System Settign crashes when changing system setting

2022-08-15 Thread Mohan Dash
https://bugs.kde.org/show_bug.cgi?id=457899

--- Comment #4 from Mohan Dash  ---
Today also the system setting closed unexpectedly. While accessing the Input
Devices in system settings.

The backtrace content are as below

Application: System Settings (systemsettings), signal: Aborted

[KCrash Handler]
#4  0x7f12386e84dc in ?? () from /usr/lib/libc.so.6
#5  0x7f1238698998 in raise () from /usr/lib/libc.so.6
#6  0x7f123868253d in abort () from /usr/lib/libc.so.6
#7  0x7f12386dc67e in ?? () from /usr/lib/libc.so.6
#8  0x7f12387775da in __fortify_fail () from /usr/lib/libc.so.6
#9  0x7f12387775a6 in __stack_chk_fail () from /usr/lib/libc.so.6
#10 0x7f1236ade92b in ?? () from /usr/lib/libQt5Qml.so.5
#11 0x7f1236ae5e8b in
QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*,
QV4::ExecutionEngine*, QV4::Lookup*) () from /usr/lib/libQt5Qml.so.5
#12 0x7f1236afabea in ?? () from /usr/lib/libQt5Qml.so.5
#13 0x7f1236b04e34 in ?? () from /usr/lib/libQt5Qml.so.5
#14 0x7f1236aa87f6 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5
#15 0x7f1236bfce6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () from /usr/lib/libQt5Qml.so.5
#16 0x7f1236bc0121 in QQmlBoundSignalExpression::evaluate(void**) () from
/usr/lib/libQt5Qml.so.5
#17 0x7f1236bc109c in ?? () from /usr/lib/libQt5Qml.so.5
#18 0x7f1236be38cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () from /usr/lib/libQt5Qml.so.5
#19 0x7f1238d3ce6d in ?? () from /usr/lib/libQt5Core.so.5
#20 0x7f12370666d9 in ?? () from /usr/lib/libQt5Quick.so.5
#21 0x7f1237067eb9 in QQuickItemView::setCurrentIndex(int) () from
/usr/lib/libQt5Quick.so.5
#22 0x7f1236ba90c2 in ?? () from /usr/lib/libQt5Qml.so.5
#23 0x7f1236bfe915 in ?? () from /usr/lib/libQt5Qml.so.5
#24 0x7f1236c0608e in ?? () from /usr/lib/libQt5Qml.so.5
#25 0x7f1236c05b73 in
QQmlBinding::update(QFlags) () from
/usr/lib/libQt5Qml.so.5
#26 0x7f1236be38cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () from /usr/lib/libQt5Qml.so.5
#27 0x7f1238d3ce6d in ?? () from /usr/lib/libQt5Core.so.5
#28 0x7f121c0411ed in ?? () from
/usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so
#29 0x7f121c041e43 in ?? () from
/usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so
#30 0x7f1236be3994 in ?? () from /usr/lib/libQt5Qml.so.5
#31 0x7f1236ae796c in ?? () from /usr/lib/libQt5Qml.so.5
#32 0x7f1236ae8f6d in QV4::QObjectMethod::callInternal(QV4::Value const*,
QV4::Value const*, int) const () from /usr/lib/libQt5Qml.so.5
#33 0x7f1236afb033 in ?? () from /usr/lib/libQt5Qml.so.5
#34 0x7f1236b04e34 in ?? () from /usr/lib/libQt5Qml.so.5
#35 0x7f1236aa87f6 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5
#36 0x7f1236bfce6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () from /usr/lib/libQt5Qml.so.5
#37 0x7f1236bc0121 in QQmlBoundSignalExpression::evaluate(void**) () from
/usr/lib/libQt5Qml.so.5
#38 0x7f1236bc109c in ?? () from /usr/lib/libQt5Qml.so.5
#39 0x7f1236be38cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () from /usr/lib/libQt5Qml.so.5
#40 0x7f1238d3ce6d in ?? () from /usr/lib/libQt5Core.so.5
#41 0x7f1232457a5a in QQuickAbstractButtonPrivate::handleRelease(QPointF
const&) () from /usr/lib/libQt5QuickTemplates2.so.5
#42 0x7f1232472ab9 in QQuickControl::mouseReleaseEvent(QMouseEvent*) ()
from /usr/lib/libQt5QuickTemplates2.so.5
#43 0x7f1236fad1c9 in QQuickItem::event(QEvent*) () from
/usr/lib/libQt5Quick.so.5
#44 0x7f1239894b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#45 0x7f1238d0cad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#46 0x7f1236fbdd93 in
QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from
/usr/lib/libQt5Quick.so.5
#47 0x7f1236fbe7f2 in
QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from
/usr/lib/libQt5Quick.so.5
#48 0x7f1239209b45 in QWindow::event(QEvent*) () from
/usr/lib/libQt5Gui.so.5
#49 0x7f1239894b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#50 0x7f1238d0cad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#51 0x7f12372f6cae in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () from
/usr/lib/libQt5QuickWidgets.so.5
#52 0x7f12398cb707 in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#53 0x7f1239894b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#54 0x7f123989a359 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#55 0x7f1238d0

[systemsettings] [Bug 457899] System Settign crashes when changing system setting

2022-08-15 Thread Mohan Dash
https://bugs.kde.org/show_bug.cgi?id=457899

--- Comment #3 from Mohan Dash  ---
(In reply to Nicolas Fella from comment #1)
> The crash originates in the "Camera" section. Did you do anything in there?

I was just checking the Removable device section.
Nothing changed or edited.

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

[systemsettings] [Bug 457899] New: System Settign crashes when changing system setting

2022-08-15 Thread Mohan Dash
https://bugs.kde.org/show_bug.cgi?id=457899

Bug ID: 457899
   Summary: System Settign crashes when changing system setting
   Product: systemsettings
   Version: 5.25.4
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mohandash...@outlook.com
  Target Milestone: ---

Application: systemsettings (5.25.4)
 (Compiled from sources)
Qt Version: 5.15.5
Frameworks Version: 5.96.0
Operating System: Linux 5.19.1-zen1-1-zen x86_64
Windowing System: X11
Distribution: Garuda Linux
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
I was just checking my system settings while in Hardware settings system
settings crashed unexpectedly.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault

[KCrash Handler]
#4  0x7f0519f53e1a in  () at /usr/lib/libQt5Core.so.5
#5  0x7f0519eddde2 in
QAbstractItemModel::modelAboutToBeReset(QAbstractItemModel::QPrivateSignal) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f051a76f64f in QStandardItemModel::clear() () at
/usr/lib/libQt5Gui.so.5
#7  0x7f04ee06d810 in  () at
/usr/lib/qt/plugins/plasma/kcms/systemsettings_qwidgets/kamera.so
#8  0x7f04ee074b42 in  () at
/usr/lib/qt/plugins/plasma/kcms/systemsettings_qwidgets/kamera.so
#9  0x7f0519f47440 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#10 0x7f051b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#11 0x7f0519f23ad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#12 0x7f0519f245e3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#13 0x7f0519f6a548 in  () at /usr/lib/libQt5Core.so.5
#14 0x7f0518564c6b in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#15 0x7f05185bb001 in  () at /usr/lib/libglib-2.0.so.0
#16 0x7f0518562392 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#17 0x7f0519f6e32c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#18 0x7f0519f1c27c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#19 0x7f0519f26da9 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#20 0x5559944a3b7a in  ()
#21 0x7f051989a2d0 in  () at /usr/lib/libc.so.6
#22 0x7f051989a38a in __libc_start_main () at /usr/lib/libc.so.6
#23 0x5559944a44d5 in  ()
[Inferior 1 (process 10436) detached]

The reporter indicates this bug may be a duplicate of or related to bug 455932.

Reported using DrKonqi

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

[kmail2] [Bug 456616] New: Kmail crashes while writing a new mail

2022-07-12 Thread Mohan Dash
https://bugs.kde.org/show_bug.cgi?id=456616

Bug ID: 456616
   Summary: Kmail crashes while writing a new mail
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: mohandash...@outlook.com
  Target Milestone: ---

Application: kmail (5.20.3 (22.04.3))

Qt Version: 5.15.5
Frameworks Version: 5.96.0
Operating System: Linux 5.18.10-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: Garuda Linux
DrKonqi: 5.25.2 [KCrashBackend]

-- Information about the crash:
I was writing a new mail while kmail crashed automatically

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x7f3bfa81ef2e in QMapDataBase::freeNodeAndRebalance(QMapNodeBase*) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f3bf93af3d5 in  () at /usr/lib/libqgpgme.so.15
#6  0x7f3bf93a66ec in
QGpgME::QGpgMEKeyForMailboxJob::~QGpgMEKeyForMailboxJob() () at
/usr/lib/libqgpgme.so.15
#7  0x7f3bf93a681e in
QGpgME::QGpgMEKeyForMailboxJob::~QGpgMEKeyForMailboxJob() () at
/usr/lib/libqgpgme.so.15
#8  0x7f3bfa9b026a in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#9  0x7f3bfb402b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#10 0x7f3bfa98cad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#11 0x7f3bfa98d5e3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#12 0x7f3bfa9d3548 in  () at /usr/lib/libQt5Core.so.5
#13 0x7f3bf31acc6b in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#14 0x7f3bf3203001 in  () at /usr/lib/libglib-2.0.so.0
#15 0x7f3bf31aa392 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#16 0x7f3bfa9d732c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#17 0x7f3bfa98527c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#18 0x7f3bfa98fda9 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#19 0x555a9b1d330f in  ()
#20 0x7f3bfa2c4290 in  () at /usr/lib/libc.so.6
#21 0x7f3bfa2c434a in __libc_start_main () at /usr/lib/libc.so.6
#22 0x555a9b1d3eb5 in  ()
[Inferior 1 (process 3466) detached]

The reporter indicates this bug may be a duplicate of or related to bug 446679,
bug 451502, bug 456580, bug 454605.

Reported using DrKonqi

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

[Breeze] [Bug 448044] GTK apps do not change when switching between Dark and Light Breeze

2022-01-10 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=448044

--- Comment #6 from Mohan  ---
(In reply to Nate Graham from comment #5)
> Thanks for the info. Does it work when you explicitly change the Global
> Theme scheme to Breeze Dark in System Settings > Appearance > Global Themes
> and then restart the app?
> 
> Basically I'm trying to find if it's broken anywhere we set global themes,
> or just on the Quick Settings page.

No it does not work in System Settings > Appearance > Global Themes, same issue
as with Quick Settings page.

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

[frameworks-kwayland] [Bug 448086] New: Under wayland minimized window get restored on all desktop not just in the desktop is resides in

2022-01-07 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=448086

Bug ID: 448086
   Summary: Under wayland minimized window get restored on all
desktop not just in the desktop is resides in
   Product: frameworks-kwayland
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: client
  Assignee: mgraess...@kde.org
  Reporter: thedefective...@gmail.com
CC: kwin-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
In Wayland if a application is minimized in another desktop clicking on its
icon in the task bar brings into focus not only in its virtual desktop but also
in current active desktop. In Xorg the desktop is changed to where the
application is. In the same note, when an application is launched in desktop 1
and you are in desktop 2 it launches in desktop 2 and not in the desktop it was
launched like it does in Xorg.  
Thanks.

STEPS TO REPRODUCE
1. Launch Dolphin in desktop 2, change to desktop 1
2. Click on Dolphin icon in desktop 1 
3. It will be restored in both desktop 1 and 2

OBSERVED RESULT
Window gets restored in both desktop 1 and desktop 2

EXPECTED RESULT
Should be restored in desktop 2 while the desktop 2 becomes active

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-23-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3770S CPU @ 3.10GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000


ADDITIONAL INFORMATION

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

[Breeze] [Bug 448044] GTK apps do not change when switching between Dark and Light Breeze

2022-01-07 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=448044

--- Comment #4 from Mohan  ---
(In reply to Nate Graham from comment #3)
> Thanks. Does it work when you explicitly change the color scheme to Breeze
> Dark in System Settings > Appearance > Colors and then restart the app?
> 
> Are you positive that these apps are using the Breeze GTK theme?

Yes that works. To confirm going into  System Settings > Appearance > Colors
changing it there and closing out of the app and opening back up works. For
both snap and deb version.

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

[Breeze] [Bug 448044] GTK apps do not change when switching between Dark and Light Breeze

2022-01-06 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=448044

--- Comment #2 from Mohan  ---
Hello Nate,
No quitting the app and relaunching it won't do anything. Initially I thought
it was because I was using a snap version (I use LibreOffice, Firefox, and
Thunderbird that are snap), but deb version also suffer from the same fate.

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

[Breeze] [Bug 448044] New: GTK apps do not change when switching between Dark and Light Breeze

2022-01-06 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=448044

Bug ID: 448044
   Summary: GTK apps do not change when switching between Dark and
Light Breeze
   Product: Breeze
   Version: 5.23.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: uhh...@gmail.com
  Reporter: thedefective...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
In Wayland if you have dark breeze theme then all GTK app are also dark (which
is what it supposed to do) but when you switch to light then they won’t switch
back until you log out and log back in. I have this issue with both .deb and
snap gtk apps. Not sure if this issue has been brought up yet. If not I would
be happy to submit a bug if pointed at the right direction. Thanks.

STEPS TO REPRODUCE
1. Launch Setting, choose Dark Theme
2. Launch a GTK application
3. In Setting switch to Light Theme, GTK application will stay in dark while Qt
based apps switch to Light them.

OBSERVED RESULT
GTk based application staying in dark/light when you switch to dark/light
breeze theme

EXPECTED RESULT
Should change the to the appropriate theme without having to log off and log
back on.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-23-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3770S CPU @ 3.10GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000

ADDITIONAL INFORMATION

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

[Discover] [Bug 418207] New: Cannot choose snap channels

2020-02-25 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=418207

Bug ID: 418207
   Summary: Cannot choose snap channels
   Product: Discover
   Version: 5.18.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Snap Backend
  Assignee: lei...@leinir.dk
  Reporter: thedefective...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
Not able to view snap channels. For example Firefox has 3 snap channels,
Stable, ESR, and Beta. I am not able to see choose these in KDE Discover. I
have test this on Kubuntu 19.10 with KDE 5.18.1 (via backport ppa) as well
latest build of KDE Neon stable edition.

STEPS TO REPRODUCE
1. Open Discover
2. Search and find Firefox Snap application
3. See if you can view different channels (Beta, ESR, Stable)

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.10
(available in About System)
KDE Plasma Version: 5.18.2
KDE Frameworks Version: 5.67.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION

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

[kwin] [Bug 417746] No shadows for Chromium based browsers in CSD

2020-02-16 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=417746

Mohan  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|NOT A BUG   |---

--- Comment #4 from Mohan  ---
Submitted.
https://bugs.chromium.org/p/chromium/issues/detail?id=1052697=2=No%20drop%20shadow%20GTK

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

[kwin] [Bug 417746] No shadows for Chromium based browsers in CSD

2020-02-16 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=417746

Mohan  changed:

   What|Removed |Added

Summary|No shows for Chromium based |No shadows for Chromium
   |browsers in CSD |based browsers in CSD

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

[kwin] [Bug 417746] New: No shows for Chromium based browsers in CSD

2020-02-16 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=417746

Bug ID: 417746
   Summary: No shows for Chromium based browsers in CSD
   Product: kwin
   Version: 5.18.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: thedefective...@gmail.com
  Target Milestone: ---

Created attachment 126076
  --> https://bugs.kde.org/attachment.cgi?id=126076=edit
Vivaldi browswer with CSD.

When turning off native window title bar, the shadow is not present in all
Chromium based browsers (Vivaldi, Chromium, Brave, etc.)

STEPS TO REPRODUCE
1. Launch the browser (in my case Vivaldi)
2. Remove native window decoration, use CSD

OBSERVED RESULT
No shadow around the active window.

EXPECTED RESULT
Shadow around the active window.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.10
(available in About System)
KDE Plasma Version: 5.18
KDE Frameworks Version: 5.67
Qt Version: 5.12.4

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

[kded-appmenu] [Bug 416275] Activating Application Menu Bar Removes Windows Controls in Firefox

2020-02-03 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=416275

--- Comment #6 from Mohan  ---
I am still having that on my test install. Maybe I haven't gotten the update
yet.

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

[kded-appmenu] [Bug 416275] Activating Application Menu Bar Removes Windows Controls in Firefox

2020-01-15 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=416275

--- Comment #2 from Mohan  ---
Plasma 5.17.80, I am running KDE Neon Unstable for testing.
Here is my Gtk3 settings.ini file.

[Settings]
gtk-application-prefer-dark-theme=0
gtk-button-images=1
gtk-cursor-theme-name=breeze_cursors
gtk-decoration-layout=icon:minimize,maximize,close
gtk-fallback-icon-theme=breeze
gtk-font-name=Noto Sans  10
gtk-icon-theme-name=breeze
gtk-menu-images=1
gtk-primary-button-warps-slider=0
gtk-theme-name=Breeze
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ

If I remove the applications menu bar the buttons reappear.

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

[kded-appmenu] [Bug 416275] Activating Application Menu Bar Removes Windows Controls in Firefox

2020-01-14 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=416275

Mohan  changed:

   What|Removed |Added

Summary|Activating Application Menu |Activating Application Menu
   |Bar Remove Windows Controls |Bar Removes Windows
   |in Firefox  |Controls in Firefox

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

[kded-appmenu] [Bug 416275] New: Activating Application Menu Bar Remove Windows Controls in Firefox

2020-01-14 Thread Mohan
https://bugs.kde.org/show_bug.cgi?id=416275

Bug ID: 416275
   Summary: Activating Application Menu Bar Remove Windows
Controls in Firefox
   Product: kded-appmenu
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: top menubar
  Assignee: plasma-b...@kde.org
  Reporter: thedefective...@gmail.com
  Target Milestone: ---

Created attachment 125132
  --> https://bugs.kde.org/attachment.cgi?id=125132=edit
No controls with Application Menu Bar

When application menu bar is added, the window controls disappear in Firefox
when using it without titlebar.

STEPS TO REPRODUCE
1. Launch Firefox, Click on Menu and choose Customize, Uncheck Titlebar
2. Right click on Desktop, Add Panel, Application Menu Bar


OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[muon] [Bug 359120] Muon update removed Kubuntu desktop

2016-02-08 Thread mohan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359120

--- Comment #2 from mohan <mohan3...@gmail.com> ---
(In reply to EllisIsPfroh from comment #1)
> hi!
> Can't see no logs?

It's in the URL field.
http://paste.ubuntu.com/14991431/

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


[muon] [Bug 359120] Muon update removed Kubuntu desktop

2016-02-07 Thread mohan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359120

mohan <mohan3...@gmail.com> changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages
 CC||mohan3...@gmail.com

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


[muon] [Bug 359120] New: Muon update removed Kubuntu desktop

2016-02-07 Thread mohan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359120

Bug ID: 359120
   Summary: Muon update removed Kubuntu desktop
   Product: muon
   Version: 5.4.2
  Platform: Other
   URL: http://paste.ubuntu.com/14991431/
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: updater
  Assignee: echidna...@kubuntu.org
  Reporter: mohan3...@gmail.com
CC: aleix...@kde.org, sit...@kde.org

On February 2nd, 2016, I did a fresh install of Kubuntu 15.10 64 bit on my
laptop (Core 2 Duo, 2GB ram). Install was fine, restarted the system and
Kubuntu loaded fine. On logging in, I was prompted by Muon to update the
system. To my bad, I did not check the exact packages that it was proposing to
change. Importantly, Muon did not inform me that packages were going to be
removed. The update, on finishing, prompted a system restart. After that, the
system hung during the boot.

After some troubleshooting, and booting into recovery mode, I was able to check
the apt logs, and I saw that the last entry removed a whole bunch of packages,
including all Kubuntu desktop packages. On the advice of a user on the Kubuntu
irc, I reinstalled Kubuntu desktop, and now, I'm my Kubuntu desktop is back. I
have not run Muon update since.

I'm attaching (check the url for paste)  my log/apt/history.log . The last
entry (Start-Date: 2016-02-05  15:32:18) is my Kubuntu desktop reinstall, and
the one prior to that (Start-Date: 2016-02-05  11:20:07) is, I'm assuming, what
Muon update did on restart. 

Reproducible: Didn't try

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