Closed Bug 1783961 Opened 2 years ago Closed 1 year ago

unified folders inbox shows no messages since update to 102.1.0 on openSuse Tumbleweed

Categories

(Thunderbird :: Folder and Message Lists, defect)

Product:
Thunderbird
Component:
Folder and Message Lists
Version:
Thunderbird 102
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: dieter, Unassigned)

Details

(Keywords: dupeme)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0

Steps to reproduce:

Yesterday the automatic update agent of Tumbleweed installed Thunderbird 102.1.0

My System:
Operating System: openSUSE Tumbleweed 20220808
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.18.15-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series

Actual results:

The inbox of grouped folders shows no messages. If I drop down to see the individual inboxes of all accounts, all messages are there and I can work with them.
In grouped folders Send, Junk and Trash only a part of all messages is shown.

Do you mean the Unified folders view?

Keywords: dupeme

Yes I think so. I am using the german translation of Thunderbird. It's the view, where all messages of all inboxes are in one window. "Gruppierte Ordner" in german.

Summary: Grouped folders inbox shows no messages since update to 102.1.0 on openSuse Tumbleweed → unified folders inbox shows no messages since update to 102.1.0 on openSuse Tumbleweed

wfm on 102.1.1 (64-bit), Win10 (but reported against Linux)

Dieter, can you try to install the original version from thunderbird.net and see if the problem occurs there, too?

Severity: -- → S3
Component: Untriaged → Folder and Message Lists
Flags: needinfo?(dieter)

I have tried now version 102.1.2 but the problem occurs there too. To be sure, I took an other PC with openSuse Leap 15.4 - with the same result.

Flags: needinfo?(dieter)

Reporter,

If you have resolved your issue, please update the bug report describing what you did to resolve it.
Also, do you see the same issue when updating to version 115?

If your original problem happened when updating to version 102, then bug 1773822 is a possible cause, but I don't think we will ever know for sure. Bug 1777606 comment 13 has a workaround for that case.

(apologies if this sounds like generic message - it is)

Whiteboard: [closeme 2023-10-01]

Resolved per whiteboard

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2023-10-01]
You need to log in before you can comment on or make changes to this bug.