[kontact] [Bug 484775] Kontact Does Not Start After Upgrade to Plasma 6.0.3

2024-04-13 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=484775

--- Comment #4 from Pedro Rosado  ---
Nope. After the latest snapshot (20240412) upgrade (which brought Qt 6.7),
Kontack, Falkon, and any Chromium-based web browser fail to start.

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

[kontact] [Bug 484775] Kontact Does Not Start After Upgrade to Plasma 6.0.3

2024-04-11 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=484775

--- Comment #3 from Pedro Rosado  ---
According to bug #1222178 in bugzilla.opensuse.org, this issue was resolved in
the Tumbleweed snapshot 20240409. Once I upgrade to this snapshot, I will
report back with the result.

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

[kontact] [Bug 484775] Kontact Does Not Start After Upgrade to Plasma 6.0.3

2024-03-30 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=484775

--- Comment #2 from Pedro Rosado  ---
My apologies. I'm still getting the new mail notifications.

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

[kontact] [Bug 484775] Kontact Does Not Start After Upgrade to Plasma 6.0.3

2024-03-30 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=484775

--- Comment #1 from Pedro Rosado  ---
When to Dr. Konqui and this is what I got:
Hint: You are currently not seeing messages from other users and the system.
  Users in the 'systemd-journal' group can see all messages. Pass -q to
  turn off this notice.
   PID: 21681 (kontact)
   UID: 1000 (pedro)
   GID: 0 (root)
Signal: 11 (SEGV)
 Timestamp: Sat 2024-03-30 00:08:46 EDT (15h ago)
  Command Line: /usr/bin/kontact
Executable: /usr/bin/kontact
 Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kontact-a4bdb5ac41514e8fb51c2a1a23411e1d.scope
  Unit: user@1000.service
 User Unit: app-org.kde.kontact-a4bdb5ac41514e8fb51c2a1a23411e1d.scope
 Slice: user-1000.slice
 Owner UID: 1000 (pedro)
   Boot ID: d41297dae5794aae8bbb5c60c6f072c9
Machine ID: d5b0a1173265414caab9d70458ec02b9
  Hostname: localhost.localdomain
   Storage:
/var/lib/systemd/coredump/core.kontact.1000.d41297dae5794aae8bbb5c60c6f072c9.21681.171177172600.zst
(present)
  Size on Disk: 7.2M
   Message: Process 21681 (kontact) of user 1000 dumped core.

Stack trace of thread 21709:
#0  0x7ff8ab8949ec __pthread_kill_implementation (libc.so.6
+ 0x949ec)
#1  0x7ff8ab841176 raise (libc.so.6 + 0x41176)
#2  0x7ff8adc60b93 _ZN6KCrash19defaultCrashHandlerEi
(libKF6Crash.so.6 + 0x6b93)
#3  0x7ff8ab841240 __restore_rt (libc.so.6 + 0x41240)
#4  0x7ff88cf2b98d n/a (crocus_dri.so + 0x72b98d)
#5  0x7ff88cf2bb49 n/a (crocus_dri.so + 0x72bb49)
#6  0x7ff88d390686 n/a (crocus_dri.so + 0xb90686)
#7  0x7ff88d390819 n/a (crocus_dri.so + 0xb90819)
#8  0x7ff88cf3957b n/a (crocus_dri.so + 0x73957b)
#9  0x7ff84d2e39ef n/a (r600_drv_video.so + 0x2e39ef)
#10 0x7ff84d2e3ce8 n/a (r600_drv_video.so + 0x2e3ce8)
#11 0x7ff84d284461 n/a (r600_drv_video.so + 0x284461)
#12 0x7ff84d23eac5 n/a (r600_drv_video.so + 0x23eac5)
#13 0x7ff84d06a49b n/a (r600_drv_video.so + 0x6a49b)
#14 0x7ff899a9f26b vaTerminate (libva.so.2 + 0x726b)
#15 0x7ff8a3f34dee n/a (libQt6WebEngineCore.so.6 +
0x2f34dee)
#16 0x7ff8a3f3fc6e n/a (libQt6WebEngineCore.so.6 +
0x2f3fc6e)
#17 0x7ff8a3f4341c n/a (libQt6WebEngineCore.so.6 +
0x2f4341c)
#18 0x7ff8a7557248 n/a (libQt6WebEngineCore.so.6 +
0x6557248)
#19 0x7ff8a5741ac5 n/a (libQt6WebEngineCore.so.6 +
0x4741ac5)
#20 0x7ff8a5755d6a n/a (libQt6WebEngineCore.so.6 +
0x4755d6a)
#21 0x7ff8ab892bb2 start_thread (libc.so.6 + 0x92bb2)
#22 0x7ff8ab91400c __clone3 (libc.so.6 + 0x11400c)

Stack trace of thread 21700:
#0  0x7ff8ab914486 epoll_wait (libc.so.6 + 0x114486)
#1  0x7ff89ed33c74 n/a (libevent-2.1.so.7 + 0x2cc74)
#2  0x7ff89ed2c051 event_base_loop (libevent-2.1.so.7 +
0x25051)
#3  0x7ff8a5775f51 n/a (libQt6WebEngineCore.so.6 +
0x4775f51)
#4  0x7ff8a572055c n/a (libQt6WebEngineCore.so.6 +
0x472055c)
#5  0x7ff8a56e8890 n/a (libQt6WebEngineCore.so.6 +
0x46e8890)
#6  0x7ff8a57409dc n/a (libQt6WebEngineCore.so.6 +
0x47409dc)
#7  0x7ff8a573024d n/a (libQt6WebEngineCore.so.6 +
0x473024d)
#8  0x7ff8a5741ab8 n/a (libQt6WebEngineCore.so.6 +
0x4741ab8)
#9  0x7ff8a5755d6a n/a (libQt6WebEngineCore.so.6 +
0x4755d6a)
#10 0x7ff8ab892bb2 start_thread (libc.so.6 + 0x92bb2)
#11 0x7ff8ab91400c __clone3 (libc.so.6 + 0x11400c)

Stack trace of thread 21689:
#0  0x7ff8ab88effe __futex_abstimed_wait_common (libc.so.6
+ 0x8effe)
#1  0x7ff8ab891d40 pthread_cond_wait@@GLIBC_2.3.2
(libc.so.6 + 0x91d40)
#2  0x7ff88c9111bb n/a (crocus_dri.so + 0xbb)
#3  0x7ff88c9071c7 n/a (crocus_dri.so + 0x1071c7)
#4  0x7ff8ab892bb2 start_thread (libc.so.6 + 0x92bb2)
#5  0x7ff8ab91400c __clone3 (libc.so.6 + 0x11400c)

Stack trace of thread 21705:
#0  0x7ff8ab88effe __futex_abstimed_wait_common (libc.so.6
+ 0x8effe)
#1  0x7ff8ab892065 pthread_cond_timedwait@@GLIBC_2.3.2
(libc.so.6 + 0x92065)
#2  0x7ff8a57551dc n/a (libQt6WebEngineCore.so.6 +
0x47551dc)
#3  0x7ff8a577c091 n/a (libQt6WebEngineCore.so.6 +
0x477c091)
#4  0x7ff8a570030f n/a (libQt6WebEngineCore.so.6 +
0x470030f

[kontact] [Bug 484775] New: Kontact Does Not Start After Upgrade to Plasma 6.0.3

2024-03-30 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=484775

Bug ID: 484775
   Summary: Kontact Does Not Start After Upgrade to Plasma 6.0.3
Classification: Applications
   Product: kontact
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: rosad...@yahoo.com
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
After upgrading to Plasma 6.0.3, Kontact fails to start. It was working fine in
6.0.2. In the command line, after typing "Kontact," the following message
appears:

Path override failed for key base::DIR_APP_DICTIONARIES and path
'/usr/bin/qtwebengine_dictionaries'
Path override failed for key base::DIR_APP_DICTIONARIES and path
'/usr/libexec/qt6/qtwebengine_dictionaries'
Path override failed for key base::DIR_APP_DICTIONARIES and path
'/usr/libexec/qt6/qtwebengine_dictionaries'
KCrash: Application 'kontact' crashing... crashRecursionCounter = 2
Segmentation fault (core dumped)

Also, I am not getting the "new mail" notifications that I used to get, even
with Kontact closed.

STEPS TO REPRODUCE
1. Click on Kontact icon in panel
2. Nothing happens
3. 

OBSERVED RESULT
Kontact does not start

EXPECTED RESULT
Kontact starts

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: opensuse Tumbleweed 
(available in About System)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

ADDITIONAL INFORMATION
Stopped getting the "new mail" notifications.

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

[kwin] [Bug 458446] Menus Start Showing behind Windows

2023-06-06 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=458446

--- Comment #13 from Pedro Rosado  ---
I think it would be a good idea to add the other desktop effects that are still
running that might have conflicted with the "Slide Back" effect:
Zoom
Background Contrast
Blur
Desaturate Unresponsive Applications
Fading Pop-Ups
Full Screen
Login
Logout
Maximize
Morphing Pop-ups
Screen Edge
Sliding Pop-ups
Wobbly Windows
Magic Lamp
Dialog Parent
Dim Screen for Administration Mode
Window Aperture
Slide
Desktop Grid
Overview
Present Windows
Tiling Editor
Scale

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

[kwin] [Bug 458446] Menus Start Showing behind Windows

2023-06-06 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=458446

--- Comment #12 from Pedro Rosado  ---
(In reply to Pedro Rosado from comment #10)
> Nate, 
> 
> Your suggestion to run that command got me thinking it might be a problem of
> conflicting desktop effects. I ticked off the "Slide Back" desktop effect.
> For two days in a row, the issue has not appeared. I think this might have
> solved the problem. 
> 
> Thank you!

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

[kwin] [Bug 458446] Menus Start Showing behind Windows

2023-06-05 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=458446

--- Comment #10 from Pedro Rosado  ---
Nate, 

Your suggestion to run that command got me thinking it might be a problem of
conflicting desktop effects. I ticked off the "Slide Back" desktop effect. For
two days in a row, the issue has not appeared. I think this might have solved
the problem. 

Thank you!

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

[kwin] [Bug 458446] Menus Start Showing behind Windows

2023-06-03 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=458446

--- Comment #9 from Pedro Rosado  ---
(In reply to Nate Graham from comment #7)
> See Comment 3

Please find below the result from running the command - 'qdbus-qt5 org.kde.KWin
/KWin supportInformation"
Version
===
KWin version: 5.27.5
Qt Version: 5.15.9
Qt compile version: 5.15.9
XCB compile version: 1.15

Operation Mode: Xwayland

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: SUSE LINUX
Vendor Release: 12301001
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.breeze
Theme: 
Plugin recommends border size: None
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==
Name: DRM
Active: true
Atomic Mode Setting on GPU 0: true

Cursor
==
themeName: breeze_cursors
themeSize: 24

Options
===
focusPolicy: 0
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 28
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: false
glStrictBindingFollowsDriver: true
glPreferBufferSwap: 101
glPlatformInterface: 2
windowsBlockCompositing: true
latencyPolicy: 
renderTimeEstimator: 
allowTearing: true

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 225
reActivateThreshold: 400
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
-
Name: eDP-1
Enabled: 1
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 60006
Adaptive Sync: incapable
Screen 1:
-
Name: VGA-1
Enabled: 1
Geometry: 1920,0,1440x900
Scale: 1
Refresh Rate: 59887
Adaptive Sync: incapable

Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
OpenGL version string: 4.6 (Core Profile) Mesa 23.0.3
OpenGL platform interface: EGL
OpenGL shading language version string: 4.60
Driver: Intel
GPU class: Haswell
OpenGL version: 4.6
GLSL version: 4.60
Mesa version: 23.0.3
Linux kernel version: 6.3.4
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---
colorpicker
outputlocator
screenshot
screenedge
zoom
blur
contrast
kwin4_effect_sessionquit
kwin4_effect_logout
kwin4_effect_login
slidingpopups
kwin4_effect_windowaperture
magiclamp
slide
slideback
kwin4_effect_fullscreen
kwin4_effect_scale
kwin4_effect_morphingpopups
kwin4_effect_maximize
kwin4_effect_frozenapp
kwin4_effect_fadingpopups
kwin4_effect_dimscreen
kwin4_effect_dialogparent
desktopgrid
highlightwindow
overview
tileseditor
windowview
wobblywindows
blendchanges
startupfeedback
kscreen
screentransform

Currently Active Effects:
-
blur
contrast

Effect Settings:

colorpicker:

outputlocator:

screenshot:

screenedge:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
focusTrackingEnabled: false
textCaretTrackingEnabled: false
focusDelay: 350
moveFactor: 20
targetZoom: 1

blur:

contrast:

kwin4_effect_sessionquit:
pluginId: kwin4_effect_sessionquit
isActiveFullScreenEffect: false

kwin4_effect_logout:
pluginId: kwin4_effect_logout
isActiveFullScreenEffect: false

kwin4_effect_login:
pluginId: kwin4_effe

[kwin] [Bug 458446] Menus Start Showing behind Windows

2023-06-02 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=458446

--- Comment #8 from Pedro Rosado  ---
Thank you, I will do so.
Regards, 

Sent from Yahoo Mail on Android 

  On Fri, Jun 2, 2023 at 13:52, Nate Graham wrote:  
https://bugs.kde.org/show_bug.cgi?id=458446

Nate Graham  changed:

          What    |Removed                    |Added

            Status|REOPENED                    |NEEDSINFO
        Resolution|---                        |WAITINGFORINFO

--- Comment #7 from Nate Graham  ---
See Comment 3

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

[kwin] [Bug 458446] Menus Start Showing behind Windows

2023-05-31 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=458446

Pedro Rosado  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
   Target Milestone|--- |5
 Resolution|WORKSFORME  |---
Version|5.25.4  |5.27.5
   Platform|Other   |openSUSE

--- Comment #6 from Pedro Rosado  ---
My apologies, I didn't receive the email asking for additional information.
What information is needed? 

Please advise.

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

[kwin] [Bug 458446] New: Menus Start Showing behind Windows

2022-08-28 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=458446

Bug ID: 458446
   Summary: Menus Start Showing behind Windows
   Product: kwin
   Version: 5.25.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rosad...@yahoo.com
  Target Milestone: ---

Created attachment 151672
  --> https://bugs.kde.org/attachment.cgi?id=151672=edit
Menu Behind Windows

SUMMARY
After 5.25, the windows behave oddly. Menus are appearing behind windows and
some windows keep themselves above, regardless of being selected or not. The
kickoff menu will appear behind the window if a window is open. 

It happens in both Wayland and X11 sessions. 

I thought for a moment that Latte Dock was causing the problem. But after
closing it, it kept happening.


***


STEPS TO REPRODUCE
1. Star session (Wayland or X11)
2. Open a program (for example, Firefox)

OBSERVED RESULT
After a while, the weird behavior will start. 

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.

[Skanpage] [Bug 457097] New: Scanning letter sized pages adds a blank area to scanned image

2022-07-24 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=457097

Bug ID: 457097
   Summary: Scanning letter sized pages adds a blank area to
scanned image
   Product: Skanpage
   Version: 22.04.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: a.stipp...@gmx.net
  Reporter: rosad...@yahoo.com
  Target Milestone: ---

Created attachment 150885
  --> https://bugs.kde.org/attachment.cgi?id=150885=edit
Screenshot of Skanpage showing scanned image

SUMMARY
***
Every time I try to scan a letter-sized page on my HP Envy 7855, the scanned
image has an additional blank area almost the same size as the scanned page.
***


STEPS TO REPRODUCE
1. Start Skanpage
2. Place page on either the document feeder or the flatbed
3. Scan the page

OBSERVED RESULT
Image wit an additional black area

EXPECTED RESULT
Image of only the scanned page

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION

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

[Akonadi] [Bug 453753] Akonadi crashes when opening KMail

2022-06-18 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=453753

--- Comment #3 from Pedro Rosado  ---
(In reply to Pedro Rosado from comment #2)
> I'm having the same issue. I get a crash notification that Akonadi stopped
> unexpectedly. When I open Kmail, a dialog appears with the message that
> Akonadi is starting. However, it doesn't. Then another window opens with a
> "Fatal error message, the Kmail closes.

I'm getting this message:
The Email program encountered a fatal error and will terminate now.
The error was:
Unable to retrieve collection for listing

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

[Akonadi] [Bug 453753] Akonadi crashes when opening KMail

2022-06-15 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=453753

Pedro Rosado  changed:

   What|Removed |Added

 CC||rosad...@yahoo.com

--- Comment #2 from Pedro Rosado  ---
I'm having the same issue. I get a crash notification that Akonadi stopped
unexpectedly. When I open Kmail, a dialog appears with the message that Akonadi
is starting. However, it doesn't. Then another window opens with a "Fatal error
message, the Kmail closes.

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

[kdeconnect] [Bug 439228] PC and phone cannot see each other - previously working

2021-07-03 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=439228

--- Comment #7 from Pedro Rosado  ---
Yeah, I deleted the KDE Connect config folder, and is working again.

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

[kdeconnect] [Bug 439228] PC and phone cannot see each other - previously working

2021-06-27 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=439228

Pedro Rosado  changed:

   What|Removed |Added

 CC||rosad...@yahoo.com

--- Comment #1 from Pedro Rosado  ---
Same issue here. Using openSUSE Tumbleweed. Everything worked fine before. I
will add that I have another Android phone and both phones can see each other
but neither can see the PC. Nor the PC can see neither phone. 

System Info: 
openSUSE Tumbleweed
Plasma 5.22.1
KDE Frameworks 5.83.0
Qt Version 5.15.2
Kernel 5.12.12-1

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

[Akonadi] [Bug 436254] Akonadi Server not Operational

2021-04-30 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=436254

Pedro Rosado  changed:

   What|Removed |Added

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

--- Comment #2 from Pedro Rosado  ---
(In reply to guiand from comment #1)
> I had the same issue.
> Solved by deleting the akonadi database.
> 
> rm -r ~/.local/share/akonadi
> 
> This only deletes a cache and does not affect any email or data stored
> locally or on the server itself.
> 
> This bug is also reffered to on:
> https://bugs.archlinux.org/task/
> 68681?string=akonadi=1_name=%5B0%5D=%5B0%5D=%5B0%
> 5D=%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=open%5B0%5
> D
> dfrom


It worked! 

Thank you!

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

[Akonadi] [Bug 436254] New: Akonadi Server not Operational

2021-04-26 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=436254

Bug ID: 436254
   Summary: Akonadi Server not Operational
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: rosad...@yahoo.com
  Target Milestone: ---

SUMMARY
After update to version 21.04 cannot retrieve my emails

STEPS TO REPRODUCE
1. Start Kontact
2. Program start 
3.  Get Message "The Akonadi personal information management service is not
operational"  

OBSERVED RESULT
Cannot see my emails (Gmail)

EXPECTED RESULT
Open and use Kmail

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

When running "akonadictl start" in Konsole I get this:
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
pedro@localhost:~> org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/pedro/.local/share/akonadi/mysql.conf",
"--datadir=/home/pedro/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2021-04-27  0:36:14 0 [Note]
/usr/sbin/mysqld (mysqld 10.5.9-MariaDB) starting as process 9039 ...\n"
org.kde.pim.akonadiserver: exit code: 6
org.kde.pim.akonadiserver: process error: "Process crashed"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...


Before the update application ran fine.

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

[kdeconnect] [Bug 423340] Cannot Send Files from PC to Mobile Device using KDE Connect

2020-06-25 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=423340

Pedro Rosado  changed:

   What|Removed |Added

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

--- Comment #1 from Pedro Rosado  ---
Solved it by going to the plugin settings and defining again the destination
folder in the Android device. Now I can send files to my device again. 

Steps:
Open KDE Connect
Go to plugin settings
Select "Share and Receive"
Select "Destination Directory"
Select the folder you want the files to be saved.

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

[kdeconnect] [Bug 423340] Cannot Send Files from PC to Mobile Device using KDE Connect

2020-06-21 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=423340

Pedro Rosado  changed:

   What|Removed |Added

Summary|Sending File from PC to |Cannot Send Files from PC
   |Mobile Device using  KDE|to Mobile Device using  KDE
   |Connect |Connect

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

[kdeconnect] [Bug 423340] New: Sending File from PC to Mobile Device using KDE Connect

2020-06-21 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=423340

Bug ID: 423340
   Summary: Sending File from PC to Mobile Device using  KDE
Connect
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: rosad...@yahoo.com
  Target Milestone: ---

Files cannot be sent to a mobile device from the PC. Sending files result in a
failed notification on the phone.


STEPS TO REPRODUCE
1. Choose a file in the PC 
2. Select "share to device"
3. Select the paired mobile device
4. Send 

OBSERVED RESULT
File fails to be sent to mobile device

EXPECTED RESULT
For the file to be sent to the device

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:openSUSE Tumbleweed 
(available in About System)
KDE Plasma Version: 5.19
KDE Frameworks Version: 5.71
Qt Version: 5.15

ADDITIONAL INFORMATION -

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

[amarok] [Bug 190543] Button Pause restart music, not pause

2019-07-07 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=190543

Pedro Rosado  changed:

   What|Removed |Added

 CC||rosad...@yahoo.com

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

[kwin] [Bug 376380] Plasma crashes while switching activities since upgrading to 5.9

2017-02-12 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=376380

--- Comment #2 from Pedro Rosado <rosad...@yahoo.com> ---
(In reply to Martin Gräßlin from comment #1)
> If KWin crashes please provide a backtrace. Otherwise we cannot do much 
> to investigate the problem.

Thanks, Martin, sadly I'm not that versed in the command line to run a proper
backtrace. I used gdb but I could not produce a proper backtrace. I willing to
learn so, if you or anyone can point me to a good source I can give it another
try.

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

[kwin] [Bug 376380] New: Plasma crashes while switching activities since upgrading to 5.9

2017-02-11 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=376380

Bug ID: 376380
   Summary: Plasma crashes while switching activities since
upgrading to 5.9
   Product: kwin
   Version: 5.9.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: activities
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rosad...@yahoo.com
  Target Milestone: ---

Since upgrading to Plasma 5.9 in openSUSE Tumbleweed workspace crashes while
switching activities. Pinning launcher to panel makes that this happens faster.

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