[Powerdevil] [Bug 482947] Screen turns off automatically with Plasma 6 despite being configured not to
https://bugs.kde.org/show_bug.cgi?id=482947 Hugues Morisset changed: What|Removed |Added CC||morisset.hug...@gmail.com --- Comment #11 from Hugues Morisset --- I have a similar problem, Weather on AC or Battery the screen dim to complete black after one minute, event when I watching a video (in this case power and battery indicator correctly reports that an application is blocking sleep). I tried to change settings in energy saving and waiting a minute and it happens each time. As said above it is hard to find what is dimming the screen, as there is no logs event in with dbus-monitor Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-25-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20QDCTO1WW System Version: ThinkPad X1 Carbon 7th -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402857] Touchpad gestures should be configurable
https://bugs.kde.org/show_bug.cgi?id=402857 Hugues Morisset changed: What|Removed |Added CC||morisset.hug...@gmail.com --- Comment #9 from Hugues Morisset --- I want 3 fingers gestures for grid aswell, until there is a configuration switch, as a workaround I successfully patched the kwin_wayland binary to change 4 fingers to 3 fingers. I describes the steps here https://blog.izissise.net/posts/kwin-gesture-patch/ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475252] LSP tooltip doesn't display correctly sometimes
https://bugs.kde.org/show_bug.cgi?id=475252 --- Comment #7 from Hugues Morisset --- Maybe something to do with locales? ``` $ rust-analyzer --version && kate --version && env | grep 'LC_*' rust-analyzer 1.74.0-nightly (65ea825 2023-09-18) QSocketNotifier: Can only be used with threads started with QThread kate 23.08.1 LC_ADDRESS=fr_FR.UTF-8 LC_NAME=fr_FR.UTF-8 LC_MONETARY=fr_FR.UTF-8 LC_PAPER=fr_FR.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LC_RESPONSE=POSIX LC_TELEPHONE=fr_FR.UTF-8 LC_MESSAGES=POSIX LC_MEASUREMENT=fr_FR.UTF-8 LC_CTYPE=en_US.UTF-8 LC_TIME=fr_FR.UTF-8 LC_COLLATE=en_US.UTF-8 LC_NUMERIC=fr_FR.UTF-8 ``` I changed LSP to be script that does the following ``` tee /tmp/lsp/rustin | rustup run nightly rust-analyzer "$@" | tee /tmp/lsp/rustout ``` loaded the file containing the example code and displayed the tooltip (which displayed incorrectly). rustin and rustout are provided in attachments -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475252] LSP tooltip doesn't display correctly sometimes
https://bugs.kde.org/show_bug.cgi?id=475252 --- Comment #6 from Hugues Morisset --- Created attachment 162125 --> https://bugs.kde.org/attachment.cgi?id=162125=edit rustout -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475252] LSP tooltip doesn't display correctly sometimes
https://bugs.kde.org/show_bug.cgi?id=475252 --- Comment #5 from Hugues Morisset --- Created attachment 162124 --> https://bugs.kde.org/attachment.cgi?id=162124=edit rustin -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475252] LSP tooltip doesn't display correctly sometimes
https://bugs.kde.org/show_bug.cgi?id=475252
--- Comment #2 from Hugues Morisset ---
Sorry, here a simple example
```
async fn main() -> Result<(), dyn std::error::Error> {
std::thread::sleep(std::time::Duration::from_secs(2))
}
```
I get
```
[rustc] (E0308) mismatched types
expected enum Result(), (dyn std::error::Error + 'static)
found unit type ()
[main.rs:1] expected Result(), (dyn std::error::Error + 'static)
because of return type
[main.rs:2] try adding an expression at the end of the block: ; Ok(())
```
I tried removing the async keyword, and the tooltip displays correctly then.
```
[rust-analyzer] (E0308) expected Result<(), dyn Error>, found ()
```
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 475252] LSP tooltip doesn't display correctly sometimes
https://bugs.kde.org/show_bug.cgi?id=475252 Hugues Morisset changed: What|Removed |Added CC||morisset.hug...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475252] New: LSP tooltip doesn't display correctly sometimes
https://bugs.kde.org/show_bug.cgi?id=475252 Bug ID: 475252 Summary: LSP tooltip doesn't display correctly sometimes Classification: Applications Product: kate Version: 23.08.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: morisset.hug...@gmail.com Target Milestone: --- Created attachment 162102 --> https://bugs.kde.org/attachment.cgi?id=162102=edit Working and non working tooltip SUMMARY When using kate with rust LSP, I sometime get miss displayed tooltips when hovering on variables or types, It looks like html is leaking as plain text (see screenshot). It seem to mainly occur when the corresponding rust code doesn't not compile. STEPS TO REPRODUCE 1. Write non compiling rust code 2. Turn on rust LSP OBSERVED RESULT Error tooltip shows HTML markers EXPECTED RESULT Error tooltip should display correctly SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kde neon KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474887] Incorrect LSP Server Selection in Kate for added languages
https://bugs.kde.org/show_bug.cgi?id=474887 Hugues Morisset changed: What|Removed |Added CC||morisset.hug...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474887] New: Incorrect LSP Server Selection in Kate for added languages
https://bugs.kde.org/show_bug.cgi?id=474887 Bug ID: 474887 Summary: Incorrect LSP Server Selection in Kate for added languages Classification: Applications Product: kate Version: 23.08.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: morisset.hug...@gmail.com Target Milestone: --- Created attachment 161877 --> https://bugs.kde.org/attachment.cgi?id=161877=edit settings SUMMARY I encountered an issue when configuring an LSP server for a Python-like language named "Please" in the Kate text editor. I added a new filetype with correct file extensions with python syntax highlighting. And then added a corresponding LSP server with `"highlightingModeRegex": "^Please$"`. Despite adding a new filetype for syntax highlighting and configuring the LSP client with the "highlightingModeRegex": "^Please$" entry, Kate continues to launch the Python LSP server instead of the one I configured. A good solution would be to allow LSP Client to match against file extensions directly. STEPS TO REPRODUCE 1. Add a new filetype mode with python syntax highlighting 2. Add an LSP server matching the filetype OBSERVED RESULT Python's LSP (pylsp) is launched EXPECTED RESULT Filetype's configured LSP should be launched (please_lsp_helper.sh in the screenshot) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kde neon KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION (This is similar to Bug 447185, however this one is about kate running the wrong lsp) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 456968] KDE Wallet Manager window is blank
https://bugs.kde.org/show_bug.cgi?id=456968 Hugues Morisset changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #10 from Hugues Morisset --- Same here, the problem reappeared ``` Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) libkf5wallet-bin:amd64 < 5.97.0+p20.04+tunstable+git20220907.0317-0 @ii mK Nb Ib > Broken libkf5wallet-bin:amd64 Depends on libqca-qt5-2:amd64 < 2.3.4+p20.04+tunstable+git20220806.0051-0 @ii mK > (>= 2.3.4+p20.04+tunstable+git20220830.0119) Removing libkf5wallet-bin:amd64 because I can't find libqca-qt5-2:amd64 Investigating (0) kwalletcli:amd64 < 3.02-1build1 @ii mK Ib > Broken kwalletcli:amd64 Depends on libkf5wallet-bin:amd64 < 5.97.0+p20.04+tunstable+git20220907.0317-0 @ii mR Nb > Considering libkf5wallet-bin:amd64 3 as a solution to kwalletcli:amd64 0 Removing kwalletcli:amd64 rather than change libkf5wallet-bin:amd64 Done Done ``` -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 458454] New: Ability to cancel a ticket
https://bugs.kde.org/show_bug.cgi?id=458454 Bug ID: 458454 Summary: Ability to cancel a ticket Product: KDE Itinerary Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: morisset.hug...@gmail.com Target Milestone: --- SUMMARY Hello, After missing my train once again by at thin margin and paying a full fare for the next one, I though it would be nice if Itinerary would be able to cancel a ticket (or open a link to the procedure). Maybe even an interactive notification that asks the user if they are already on the train/plane some minutes before departure and cancel automatically if they are not. For example SNCF will almost always sell annullable tickets that will give you some money back if you cancel before departure. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 456968] KDE Wallet Manager window is blank
https://bugs.kde.org/show_bug.cgi?id=456968 Hugues Morisset changed: What|Removed |Added CC||morisset.hug...@gmail.com --- Comment #2 from Hugues Morisset --- Hello, I go the same issue after updating on kde neon testing. The problem is kwalletcli got uninstalled because of a dependency problem on `libqca-qt5-2` I got it temporarily working with this dirty hack: ``` - Download libkf5wallet-bin -> https://origin.archive.neon.kde.org/testing/pool/main/k/kwallet-kf5/libkf5wallet-bin_5.96.0+p20.04+tunstable+git20220716.0119-0_amd64.deb - Use this https://unix.stackexchange.com/questions/138188/easily-unpack-deb-edit-postinst-and-repack-deb to unpack the deb - Open DEBIAN/control and change the version for libqca-qt5-2 to 2.3.4+p20.04+tstable+git20220713.0040-0 - Repack the deb - sudo dpkg -i fixed.deb - sudo apt install kwalletcli - pkill gpg-agent - It now works ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434051] Plasma freezes when opening applets' pop-ups while any app windows are open
https://bugs.kde.org/show_bug.cgi?id=434051 Hugues Morisset changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #10 from Hugues Morisset --- Hello, I've been able to fix the issues, it was actually caused by https://github.com/psifidotos/applet-window-buttons There is a similar issue on the project https://github.com/psifidotos/applet-window-buttons/issues/123 which describe the problems I have By disabling `Draw buttons inactive state when needed` option is instantly fixed the performance issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434051] Plasma freezes when opening applets' pop-ups while any app windows are open
https://bugs.kde.org/show_bug.cgi?id=434051 Hugues Morisset changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434051] Plasma freezes when opening applets' pop-ups while any app windows are open
https://bugs.kde.org/show_bug.cgi?id=434051 --- Comment #8 from Hugues Morisset --- Yep the second video as krohnkite disabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434051] Plasma freezes when opening applets' pop-ups while any app windows are open
https://bugs.kde.org/show_bug.cgi?id=434051 --- Comment #6 from Hugues Morisset --- Thanks a lot for your interest on this issue Here another screen recording where I try suggestions you made https://streamable.com/xopt4f Indeed, it doesn't happen if there is no window under the pop-up. I don't really see any window type pattern :/ Also, I failed to mention that I made the previous video with krohnkite enable which I disabled for this one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434051] Plasma freezes when opening applets' pop-ups
https://bugs.kde.org/show_bug.cgi?id=434051 Hugues Morisset changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Hugues Morisset --- In testing with desktop applet, it seems that it happens only when there is a window in the background, when opening an applet from the panel with only desktop image in the background no freeze happen. I made a short screen record so it's clearer, you can see when plasmashell freezes with the clock at the top https://streamable.com/ey1tug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434051] Panel freeze multiple seconds on actions
https://bugs.kde.org/show_bug.cgi?id=434051 --- Comment #2 from Hugues Morisset --- Plasmashell process is using 100% of one core. It sometimes also happens that it freeze on some notification pop-up, particularly file copy making dolphin also freeze until the pop-up appears. But kdeconnect or spotify notifications are fine. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 434012] switching off monitor switches off sound from monitor's built-in speakers too
https://bugs.kde.org/show_bug.cgi?id=434012 Hugues Morisset changed: What|Removed |Added CC||morisset.hug...@gmail.com --- Comment #1 from Hugues Morisset --- It seems like it's an intended behavior, if the audio output disappear the audio should not be outputed on it anymore. If you want the screen to stay on, you can disable automatic sleep in the battery widget. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434051] New: Panel freeze multiple seconds on actions
https://bugs.kde.org/show_bug.cgi?id=434051 Bug ID: 434051 Summary: Panel freeze multiple seconds on actions Product: plasmashell Version: 5.21.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: morisset.hug...@gmail.com Target Milestone: 1.0 Created attachment 136429 --> https://bugs.kde.org/attachment.cgi?id=136429=edit glxinfo SUMMARY Panel freeze multiple seconds on actions STEPS TO REPRODUCE 1. Click any widgets on the panel 2. widget popup opens 3. panel and widget is freeze for multiple seconds 4. The freeze also happens on widget closing OBSERVED RESULT I have the panel's clock configured to display seconds, and can clearly see the freeze happening. I used perf (`perf record -o /tmp/perf --call-graph dwarf --sample-cpu --pid $(pidof plasmashell`) ) to see the flamegraph: https://ibb.co/BgyB7ft So the problem seems to be with transparency and maybe a regression in libQt? EXPECTED RESULT Smooth usage SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: /Kde Neon (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Same freeze also happens with compositor disable One CPU gets 100% usage during freeze I've not been able to test with transparency/blur deactivated I didn't find where the option is, if someone got this information, I'm willing to test -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415522] New: Disconnect from a wifi network crashed plasma
https://bugs.kde.org/show_bug.cgi?id=415522 Bug ID: 415522 Summary: Disconnect from a wifi network crashed plasma Product: plasmashell Version: 5.17.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: morisset.hug...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.3) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 4.15.0-70-generic x86_64 Distribution: KDE neon Testing Edition -- Information about the crash: - What I was doing when the application crashed: Disconnected from a wifi network from the network manager widget The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f18e466f800 (LWP 5266))] Thread 18 (Thread 0x7f1866291700 (LWP 19353)): #0 0x7f18db3d59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x561d12025df4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f18db3d59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x561d12025da0, cond=0x561d12025dc8) at pthread_cond_wait.c:502 #2 0x7f18db3d59f3 in __pthread_cond_wait (cond=0x561d12025dc8, mutex=0x561d12025da0) at pthread_cond_wait.c:655 #3 0x7f18de4a4aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f18de4a4df9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f18e24cdec8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f18e24ce2fa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f18de49db52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f18db3cf6db in start_thread (arg=0x7f1866291700) at pthread_create.c:463 #9 0x7f18ddd9a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f183389c700 (LWP 16475)): #0 0x7f18db3d59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x561d19bc9e14) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f18db3d59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x561d19bc9dc0, cond=0x561d19bc9de8) at pthread_cond_wait.c:502 #2 0x7f18db3d59f3 in __pthread_cond_wait (cond=0x561d19bc9de8, mutex=0x561d19bc9dc0) at pthread_cond_wait.c:655 #3 0x7f18de4a4aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f18de4a4df9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f18e24cdec8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f18e24ce2fa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f18de49db52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f18db3cf6db in start_thread (arg=0x7f183389c700) at pthread_create.c:463 #9 0x7f18ddd9a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f182b8a7700 (LWP 14083)): #0 0x7f18db3d59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x561d192db334) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f18db3d59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x561d192db2e0, cond=0x561d192db308) at pthread_cond_wait.c:502 #2 0x7f18db3d59f3 in __pthread_cond_wait (cond=0x561d192db308, mutex=0x561d192db2e0) at pthread_cond_wait.c:655 #3 0x7f18de4a4aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f18de4a4df9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f18e24cdec8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f18e24ce2fa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f18de49db52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f18db3cf6db in start_thread (arg=0x7f182b8a7700) at pthread_create.c:463 #9 0x7f18ddd9a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f183309b700 (LWP 4816)): #0 0x7f18db3d59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x561d1646ceb4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f18db3d59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x561d1646ce60, cond=0x561d1646ce88) at pthread_cond_wait.c:502 #2 0x7f18db3d59f3 in __pthread_cond_wait (cond=0x561d1646ce88, mutex=0x561d1646ce60) at pthread_cond_wait.c:655 #3 0x7f18de4a4aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f18de4a4df9 in QWaitCondition::wait(QMutex*, unsigned
[kdevelop] [Bug 387733] kdevelop crashes on deactivating the activity containing it
https://bugs.kde.org/show_bug.cgi?id=387733 --- Comment #1 from Hugues Morisset <morisset.hug...@gmail.com> --- Created attachment 110565 --> https://bugs.kde.org/attachment.cgi?id=110565=edit New crash information added by DrKonqi kdevelop (5.2.40) using Qt 5.9.2 Closing the activity where a kdevelop instance crash it -- Backtrace (Reduced): #6 0x7fc0983c288f in QWidget::~QWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fc0983c2c99 in QWidget::~QWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fc09769b8e0 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc0983c7453 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fc09838863c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387733] kdevelop crashes on deactivating the activity containing it
https://bugs.kde.org/show_bug.cgi?id=387733 Hugues Morisset <morisset.hug...@gmail.com> changed: What|Removed |Added CC||morisset.hug...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
