Hi Danial,
Some more investigation ...
I reverted to Kernel to 5.3.18 ... also installed xserver-xorg-video-intel.
strace for gnome-shell shows no more errors on mouse / touchpad activity
and load remains low ..
rahul@desktophp:~$ sudo strace -c -p 11997
[sudo] password for rahul:
strace:
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
On Sun, Nov 08, 2020 at 03:03:03AM -, Mike Boruta wrote:
>Hello again, I manually applied both the patches present in #239 and in
>#171 to kernel 5.4.0-52 without success (touch pad still does not work),
>however I applied the patch listed on #109 with success. My device is a
>MSFT0001:00
On Wed, Nov 04, 2020 at 12:12:24PM -, Von wrote:
>@Coiby Xu (coiby)
>
>> Will decreasing
>polling_interval_active_us to 1ms fix the problem?
>> $echo 1000 > /sys/module/i2c_hid/parameters/polling_interval_active_us
>
>Yes, I installed the latest version from Github, and decreasing
linux:~$ time nautilus
Failed to register: Timeout was reached
real0m25.127s
user0m0.101s
sys 0m0.004s
linux:~$ time nautilus
Failed to register: Timeout was reached
real0m25.166s
user0m0.076s
sys 0m0.035s
linux:~$ time nautilus
Failed to register: Timeout was reached
Hello again, I manually applied both the patches present in #239 and in
#171 to kernel 5.4.0-52 without success (touch pad still does not work),
however I applied the patch listed on #109 with success. My device is a
MSFT0001:00 04F3:3186, unlike the 3140 most users have. Have any other
users with
Okay, so here is the new work-around. You put this file in
/usr/lib/systemd/system-sleep/
I called it 20_map-to-display. Call it what you like. It needs to be
executable.
#!/bin/sh
export HOME=/home/frohro/
export DISPLAY=:0
case $1/$2 in
post/*)
/usr/bin/su
Unfortunately the above work-around only works when I suspend using pm-
suspend. The system is using systems. I'm working on figuring that out
now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
I have to same error with Ubuntu 20.10
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Package changed: linux (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
This extra cursor frozen on screen issue exists in 20.10 Groovy Gorilla.
(Just installed 20.10 on Lenovo T14 AMD and have a few issues to
research.)
Actual behavior:
- Fractional scaling is on (actually needed to make laptop screen readable).
- Extra cursor frozen on screen.
Expected:
-
You have been subscribed to a public bug:
dmesg
Bluetooth: hci0: command 0x0c24 tx timeout
rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: hci1: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: yes
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in
** Changed in: ibus
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1901789
Title:
Release upgrade 20.04 -> 20.10 removed input method from ibus
Status in
Yes I could get it back; It works as expected now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1901789
Title:
Release upgrade 20.04 -> 20.10 removed input method from ibus
Status in
This kept bothering me so I came up with a work-around. I put the
following file (with chmod 755 so it could be executed) in
/etc/pm/sleep.d/ and called it 20_map-to-display. You have to use the
xinput and xrandr commands to determine what your display is called
(where I have LVDS-1) and which
** Bug watch added: github.com/ibus/ibus/issues #2274
https://github.com/ibus/ibus/issues/2274
** Also affects: ibus via
https://github.com/ibus/ibus/issues/2274
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
For anyone who might be interested, since in my case this problem is
caused by fractional scaling, in my Ubuntu 20.04 (and then also 20.10)
installation I was able to "automatically fix" it every login by using
this very small program I developed: https://github.com/mind-overflow
I would guess that this happened since
/usr/share/ibus/component/simple.xml underwent extensive changes and now
offers a lot more XKB layouts than previously.
Were you able to add back German via ibus-setup, and does it work as
expected after that?
** Package changed: ubuntu-release-upgrader
*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052
I don't think there is an official solution to this yet, however, in my
Ubuntu 20.04 (and then also 20.10) installation I was able to
automatically fix it every login by using this very small program I
You have been subscribed to a public bug:
What happened:
===
I'm using iBus as input "method" with
- Japanese (Anthy) // primary
- German
set up.
I upgraded from ubuntu 20.04 to 20.10.
EXPECTED: No changes regarding input.
ACTUAL: German input method was removed
lsb_release -rd
** Changed in: firefox
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1835024
Title:
firefox fails to use the default profile from classic snaps
Hi Oliver,
Thank you for your report.
I was unable to reproduce this issue on Firefox Release version 81.0
(64-bit) Mozilla Firefox for Ubuntu canonical 1.0 , but I did reproduce
the issue by downloading Firefox Nightly 84.0a1 (2020-11-14) (64-bit)
and installing it on a different location (for
Public bug reported:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"
$ arch
x86_64
Getting a link error when trying to build Wireshark from source on
Ubuntu Focal. I need to build Wireshark for plugin development.
You have been subscribed to a public bug:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"
$ arch
x86_64
Getting a link error when trying to build Wireshark from source on
Ubuntu Focal. I need to build Wireshark for
Getting: 'bash: /sys/bus/usb/devices/1-3/power/control: Permission
denied', as output. Checked the control settings and it's already on by
default, I think.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
Same problem here, after upgrade from Ubuntu 20.04 to 20.10, nexcloud app
indicator in top bar disappeared.
I "killall nexcloud" and restart as per comment #3 above and icon reappear,
until next reboot!
--
You received this bug notification because you are a member of Desktop
Packages, which
I did just use:
driver = webdriver.Chrome()
However, I just tried the same code again and could not reproduce the
crash. Now, it seems to work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Does
echo on > /sys/bus/usb/devices/1-3/power/control
make any difference?
It will disable auto suspend for the port, power will always be on.
1-3 is the hub and port you had the dongle connected to
--
You received this bug notification because you are a member of Desktop
Packages, which is
I mean; does 'top' report constant CPU without moving the mouse, or was
that only with gnome-system-monitor? (bug 1773502)
-- top reports constant CPU without moving mouse ... and it increases to a
higher value on Mouse / touchpad activity this is even without Gnome-system
monitor.
Regards ///
On 2020-11-07 13:42, Lars Melin wrote:
> Installing another version of usb-modeswitch will not solve the
> problem because usb-modeswitch is not the problem.
Right, that was my impression from previous comments above, and now the
bug reporter has confirmed it.
On 2020-11-07 13:57, Abnilson
I am experiencing this on Kubuntu 20.04.
Version: 6.4.6.2
Build ID: 1:6.4.6-0ubuntu0.20.04.1
CPU threads: 4; OS: Linux 5.4; UI render: GL; VCL: kf5;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: CL
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
I still have this (or a very similar issue) after having upgraded to
20.04
```
gnome-shell[4128]: ###!!! [Parent][RunMessage] Error: Channel closing: too late
to send/recv, messages will be lost
```
--
You received this bug notification because you are a member of Desktop
Packages, which is
Yeah, it's true. I tried to install usb-modeswitch from focal universe,
nothing changed... I don't know what to do any more...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
Happened again with distro-info-data on Ubuntu 20.04.
$ apt policy distro-info-data
distro-info-data:
Installert: 0.43ubuntu1.2
Kandidat: 0.43ubuntu1.4
Versjonstabell:
0.43ubuntu1.4 500
500 http://no.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
500
@Gunnar Hjalmarsson:
Installing another version of usb-modeswitch will not solve the problem because
usb-modeswitch is not the problem.
usb-modeswitch does what it should do and that is switch the dongle from
19d2:1595 into 19d2:1592 and then leave the stage. Exit.
usb-modeswitch will do the
** Changed in: gnome-shell
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1728045
Title:
Please restore battery time remaining to top bar!
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing
all old bug reports in Bugzilla which have not seen updates for many
years.
If you can still reproduce this issue in a currently supported version
of GNOME (currently that would be 3.38), then please feel free to report
it
I think it might have been something wrong with my wireless mouse,
because it also caused some issues with the window manager on Macs. I
have a set of Microsoft keyboard and mouse, and when I used the mouse on
Mac, it caused some issues with highlighting of menu items. When I
replaced it with a
Hi,
I'm running focal (20.04.1 LTS) -- and hit this only just now when
upgrading to the new LTS.
So this is to confirm this affects the LTS release and I'd like to ask
for it back-ported. :)
Thanks,
-- Peter
--
You received this bug notification because you are a member of Desktop
Packages,
@Abnilson: Maybe you as an experiment could download the focal version
of usb-modeswitch and install it manually.
https://packages.ubuntu.com/focal/amd64/usb-modeswitch/download
Does that make a difference for you on Ubuntu 20.10?
--
You received this bug notification because you are a member
On 20/10/2020, Daniel van Vugt <1900...@bugs.launchpad.net> wrote:
> That sounds like it might be the problem. Please look in /etc/pulse/ and
> see if you can remember what you changed. Failing that, just
> reinstalling and not modifying the system, might be the fastest
> solution.
Audio works
I don't doubt that it was working in earlier versions.
The point is that the cause of the problem is somewhere else, probably in the
USB driver.
It's not a usb_modeswitch problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I installed the budgie-desktop 10.5.1-6ubuntu0.2 packages from focal-
proposed, and could then successfully verify the test case using im-
config 0.44-1ubuntu1.3 from focal-proposed.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done
But it was working well in earlier Ubuntu versions and others Linux
Distros... That was my first worst UX with Ubuntu 20.10 since I started
to use it few weeks ago.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in
Your log shows many disconnects and reconnects, as Lars has noticed.
If you have not unplugged your modem manually, then there is a problem
with the USB connection. Note that it may also be driver-related, so
does not happen on Windows.
In any case, usb_modeswitch is not the problem. The mode
If I try to connect before that, the connection is automatically
interrupted somehow.
** Attachment added: "True network device ready mode notification"
I'm using my Mobile Broadband device for 2 years, I came from Ubuntu
20.04 and those unusual behaviours weren't happening there. The time
range of 15-25 mins is the time the device is truly ready and even
appears on as USB mass on any device management tool (I see it from
gnome dock). And I don't
** Description changed:
The bug occurs with any XWayland application. I tried VSCode, Chrome,
Audacity, Darktable...
I have two monitors with a different DPI. One is 4K HiDPI monitor and
the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI
monitor and 100% scale for a
Ah, that makes sense. So these are not manual disconnects then.
Why would the first run of usb_modeswitch (during boot) take so long?
Just system load perhaps?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
Public bug reported:
The bug occurs with any XWayland application. I tried VSCode, Chrome,
Audacity, Darktable...
I have two monitors with a different DPI. One is 4K HiDPI monitor and
the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI
monitor and 100% scale for a LowDPI. All
** Attachment added: "HiDPI monitor is primary"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+attachment/5432118/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-11-07%2012-26-50.png
--
You received this bug
** Also affects: webkit2gtk (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gnome-control-center (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
Public bug reported:
Fresh install of groovy. When I try to add Google, Flickr or Microsoft
account, the loading window stays grey forever. When trying Facebook, i
can see the loaded page for a second then switches to grey also.
gnome-online-accounts:
Telepítve: 3.37.90-1ubuntu1
Jelölt:
The around 50 seconds between each sequence matches very well the time it takes
for a Mobile Broadband device to become ready and start communicating with the
tower.
The overcurrent draw occurs when it at that time turns on its transmitter.
--
You received this bug notification because you are
I can't see any usb-modeswitch problem but your ZTE dongle does
repeatedly fall off the usb bus and moment later arriving again with its
initial id 19d2:1595 which usb_modeswitch immediately switches to
19d2:1592. This sequence is repeated through the whole log session:
09:49:38 19d2:1595
I have trouble pinpointing the actual problem. Did you want to say
"15-25 seconds" instead of "minutes"?
The only unusual behaviour I see in your log is that the very first run
of usb_modeswitch takes roughly 40 seconds. Afterwards, everything seems
to be fine, modem and storage.
I suppose the
Well I think the situation is kinda little new because in default
package my USB drive was never recognized as USB mass. Now it may take
it's time (15-25 mins) but in final it's recognized as USB mass.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
I have the habit of having the generic LibreOffice icon added to the
Ubuntu dock instead of the icons specific to Writer, Calc etc. However,
suddenly the Dock started to ignore my attempts to add that generic
icon.
I have LibreOffice installed via .deb files.
** Affects:
** Attachment added: "'journalctl -b 0' log"
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1903331/+attachment/5432096/+files/on-HP-250-G6-Notebook-PC%20kernel%3A%20microcode%3A%20microcode%20updated%20early%20to%20revision%200x411%2C%20date%20%3D%202019-04-23
--
You received
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1903376
Title:
Suddenly Graphic Display issue
Status in xorg package in Ubuntu:
New
Bug
You have been subscribed to a public bug:
i recently installed XDM (xtreme download manager) after my display
changed to 1024x768 before it was good with 1336x768.
i have also uninstalled it but still the problem persists
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1903377
Title:
package nvidia-340 340.108-0ubuntu2 failed to install/upgrade:
Public bug reported:
It gives me an error message.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.11
63 matches
Mail list logo
