[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
Discovered this upstream bug report: https://gitlab.gnome.org/GNOME/gdm/-/issues/714 Allegedly the problem affects fonts that don't provide the oddball ratio character GNOME insists on using for the clock colon, including the default Ubuntu font. This can also cause the colon to render incorrectly depending on which fonts are installed on the system and what the GNOME interface font is set to. I'm going to try the Cantarell font (the upstream GNOME default font, I think) and see if it resolves the issue. ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #714 https://gitlab.gnome.org/GNOME/gdm/-/issues/714 -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
I've been seeing it too in 20.04 (Focal), using NVIDIA binary drives and Xorg. I usually see it on the top bar (has happened several times over the past couple of days) but I've also seen it at least once on the lock screen. It seems that moving the mouse pointer over the time corrects it temporarily until the glitch next happens. I could run an apport-collect command on this bug if anybody is still interested. -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
I just discovered this the hard way. I happened to have speedtest.net
opened in an unfocused Chromium tab on an inactive workspace and spent
quite a bit of time going through a wild goose chase trying to figure
out why my previously reliable DPMS/screen-locking setup suddenly flat-
out refused to work at all. This was just running in the i3 window
manager; no Gnome or KDE, nothing fancy. Closing the tab involved, or
Chromium altogether, makes it work again.
The closest upstream bug I could find is
https://bugs.chromium.org/p/chromium/issues/detail?id=654659 , but it
appears to have been basically ignored by the developers.
It seems that Chromium has issues with inhibiting power management too
aggressively. So aggressively I'd almost call it abusive.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
Status in gnome-session package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
*** 3.18.1.2-1ubuntu1.16.04.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.18.1.2-1ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
I'm using gnome-session-flashback
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
I've been having this issue sice before 14.04, which I recently
upgraded (fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer
after 10 minutes (or whatever time I setup). At one point it stopped
working. The screen never shuts down unless I manually lock the
session with CTRL-ALT-L.
I've followed the steps in
https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
The culprit seems to be that Chrome issues some suspend inhibitions
through dbus when doing certain operations. Many people find this
problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
pretty sure that Chrome is doing something else of what i've found
out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensaver-command -a
2) Gnome screen saver never receives the "session idle" status
callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-inhibit --app-id test --reason "manual idle inhibit"
--inhibit-only --inhibit idle:suspend
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103
reply_serial=2
array [
object path "/org/gnome/SessionManager/Inhibitor1686"
]
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
('test',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetFlags
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60
(1 minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the
inhibitor:
GetAppId: ('/usr/bin/google-chrome-stable',)
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving
mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for
another 30-60 seconds. The screen NEVER locks when this tab is open.
No matter the inhibitor is present or not.
I'm not sure where to go on. If it's a Chrome bug it must be using
other mechanisms to prevent the idle timeout. Any ideas on what to
look for?
Julian.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654392] Re: growisofs -speed parameter has no effect
Thanks for the response and sorry for the delay! I actually don't burn optical discs very often anymore and needed to wait for another opportunity to arise (my discs are DVD+R which don't work with simulated writing, and I didn't want to waste them in order to test). With -speed=1, growisofs still writes at maximum speed (16x). However, with xorrecord, the speed control works fine. Thanks for suggesting those tools; my GNU/Linux burning knowledge has been out of date for a while and I lost track of all the forks. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dvd+rw-tools in Ubuntu. https://bugs.launchpad.net/bugs/1654392 Title: growisofs -speed parameter has no effect Status in dvd+rw-tools package in Ubuntu: New Bug description: growisofs apparently ignores the -speed parameter when burning a DVD ISO regardless of the given value or the supported writing speeds. ——— $ dvd+rw-mediainfo /dev/dvd INQUIRY:[HP ][DVD Writer 1270d][GH24] GET [CURRENT] CONFIGURATION: Mounted Media: 1Bh, DVD+R Media ID: MBIPG101/R05 Current Write Speed: 16.0x1385=22160KB/s Write Speed #0:16.0x1385=22160KB/s Write Speed #1:12.0x1385=16620KB/s Write Speed #2:8.0x1385=11080KB/s Write Speed #3:6.0x1385=8310KB/s Speed Descriptor#0:00/2295103 R@16.0x1385=22160KB/s W@16.0x1385=22160KB/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2295104*2KB=4700372992 READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty "Next" Track: 1 Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2295104*2KB Track Size:2295104*2KB ROM Compatibility LBA: 270336 READ CAPACITY: 0*2048=0 $ growisofs -speed 12 -dvd-compat -Z /dev/dvd=dvd1.iso Executing 'builtin_dd if=dvd1.iso of=/dev/dvd obs=32k seek=0' /dev/dvd: "Current Write Speed" is 16.4x1352KBps. 0/4621449216 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/4621449216 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% […] 4328620032/4621449216 (93.7%) @15.6x, remaining 0:20 RBU 100.0% UBU 99.3% 4393402368/4621449216 (95.1%) @14.0x, remaining 0:16 RBU 100.0% UBU 99.3% 4466507776/4621449216 (96.6%) @15.8x, remaining 0:10 RBU 100.0% UBU 99.0% 4527161344/4621449216 (98.0%) @13.1x, remaining 0:06 RBU 100.0% UBU 15.4% 4601151488/4621449216 (99.6%) @16.0x, remaining 0:01 RBU 60.5% UBU 99.0% builtin_dd: 2256576*2KB out @ average 10.4x1352KBps /dev/dvd: flushing cache /dev/dvd: closing track /dev/dvd: closing disc /dev/dvd: reloading tray ——— Same result with -speed=8 or -speed 8: Instead of using the specified speed (listed as supported by dvd+rw-mediainfo), it uses 16x instead. With the same media and drive, setting speed *does* when using wodim (e.g., `wodim -v -dao speed=8 dvd1.iso` does write at 8x), so it isn't simply a drive/media issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: growisofs 7.1-11 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jan 5 14:31:16 2017 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.4 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu4 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.4 InstallationDate: Installed on 2016-04-11 (268 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: dvd+rw-tools UpgradeStatus: Upgraded to xenial on 2016-04-26 (254 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1654392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot
I got hit by this too a while back. I don't expect a simple system upgrade to break my system. I ended up having to continue using an out- of-date kernel for some time as a result. It's still not fixed with nvidia-367 and 4.4.0-59-generic. But manually editing /etc/default/grub and removing "splash" from the GRUB_CMDLINE_LINUX_DEFAULT options, followed by executing update-grub2, does allow my system to boot with 4.4.0-59 (I didn't have to use "nomodeset"). I consider myself lucky. If this really affects *everyone* who simply uses the official Nvidia drivers, then I'm tempted to feel that these updates are not being tested adequately before release. I really hope that this testing will improve once this gets fixed, because things like this encourage users to leave their systems out of date and possibly risk security issues just to ensure that they at least *work*. It certainly doesn't encourage *me* to update my system very often (and I'm bad enough about that as it is). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1638990 Title: nvidia-367 with kernel 4.4.0-45-generic won't boot Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: After I upgraded the nvidia drivers, I could no longer boot via kernel 4.4.0-45-generic. WORKAROUND: Use nouveau. WORKAROUND: Boot with already installed kernel 4.4.0-31-generic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lost 2248 F pulseaudio /dev/snd/controlC0: lost 2248 F pulseaudio /dev/snd/controlC1: lost 2248 F pulseaudio CurrentDesktop: XFCE Date: Thu Nov 3 12:12:55 2016 HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6 InstallationDate: Installed on 2016-11-01 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 11361Q0 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A3KT57AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: 573921 dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 11361Q0 dmi.product.version: ThinkStation C30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654392] [NEW] growisofs -speed parameter has no effect
Public bug reported: growisofs apparently ignores the -speed parameter when burning a DVD ISO regardless of the given value or the supported writing speeds. ——— $ dvd+rw-mediainfo /dev/dvd INQUIRY:[HP ][DVD Writer 1270d][GH24] GET [CURRENT] CONFIGURATION: Mounted Media: 1Bh, DVD+R Media ID: MBIPG101/R05 Current Write Speed: 16.0x1385=22160KB/s Write Speed #0:16.0x1385=22160KB/s Write Speed #1:12.0x1385=16620KB/s Write Speed #2:8.0x1385=11080KB/s Write Speed #3:6.0x1385=8310KB/s Speed Descriptor#0:00/2295103 R@16.0x1385=22160KB/s W@16.0x1385=22160KB/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2295104*2KB=4700372992 READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty "Next" Track: 1 Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2295104*2KB Track Size:2295104*2KB ROM Compatibility LBA: 270336 READ CAPACITY: 0*2048=0 $ growisofs -speed 12 -dvd-compat -Z /dev/dvd=dvd1.iso Executing 'builtin_dd if=dvd1.iso of=/dev/dvd obs=32k seek=0' /dev/dvd: "Current Write Speed" is 16.4x1352KBps. 0/4621449216 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/4621449216 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% […] 4328620032/4621449216 (93.7%) @15.6x, remaining 0:20 RBU 100.0% UBU 99.3% 4393402368/4621449216 (95.1%) @14.0x, remaining 0:16 RBU 100.0% UBU 99.3% 4466507776/4621449216 (96.6%) @15.8x, remaining 0:10 RBU 100.0% UBU 99.0% 4527161344/4621449216 (98.0%) @13.1x, remaining 0:06 RBU 100.0% UBU 15.4% 4601151488/4621449216 (99.6%) @16.0x, remaining 0:01 RBU 60.5% UBU 99.0% builtin_dd: 2256576*2KB out @ average 10.4x1352KBps /dev/dvd: flushing cache /dev/dvd: closing track /dev/dvd: closing disc /dev/dvd: reloading tray ——— Same result with -speed=8 or -speed 8: Instead of using the specified speed (listed as supported by dvd+rw-mediainfo), it uses 16x instead. With the same media and drive, setting speed *does* when using wodim (e.g., `wodim -v -dao speed=8 dvd1.iso` does write at 8x), so it isn't simply a drive/media issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: growisofs 7.1-11 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jan 5 14:31:16 2017 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.4 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu4 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.4 InstallationDate: Installed on 2016-04-11 (268 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: dvd+rw-tools UpgradeStatus: Upgraded to xenial on 2016-04-26 (254 days ago) ** Affects: dvd+rw-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dvd+rw-tools in Ubuntu. https://bugs.launchpad.net/bugs/1654392 Title: growisofs -speed parameter has no effect Status in dvd+rw-tools package in Ubuntu: New Bug description: growisofs apparently ignores the -speed parameter when burning a DVD ISO regardless of the given value or the supported writing speeds. ——— $ dvd+rw-mediainfo /dev/dvd INQUIRY:[HP ][DVD Writer 1270d][GH24] GET [CURRENT] CONFIGURATION: Mounted Media: 1Bh, DVD+R Media ID: MBIPG101/R05 Current Write Speed: 16.0x1385=22160KB/s Write Speed #0:16.0x1385=22160KB/s Write Speed #1:12.0x1385=16620KB/s Write Speed #2:8.0x1385=11080KB/s Write Speed #3:6.0x1385=8310KB/s Speed Descriptor#0:00/2295103 R@16.0x1385=22160KB/s W@16.0x1385=22160KB/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2295104*2KB=4700372992 READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty "Next" Track: 1 Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2295104*2KB Track Size:2295104*2KB ROM Compatibility LBA: 270336 READ CAPACITY: 0*2048=0 $ growisofs -speed 12 -dvd-compat -Z /dev/dvd=dvd1.iso Executing 'builtin_dd if=dvd1.iso of=/dev/dvd obs=32k seek=0' /dev/dvd: "Current Write Speed" is 16.4x1352KBps. 0/4621449216 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/4621449216 ( 0.0%) @0x, remaining ??:?? RBU
[Desktop-packages] [Bug 1605101] [NEW] Writer: Up and down keys move cursor to random line positions instead of directly up or down
Public bug reported: Immediately after writing some text in Writer, using the up and down keyboard keys to move the text cursor results in the cursor moving to unpredictable horizontal positions on the adjacent line (or in rare cases, even *several* lines away) instead of in the expected position, directly above or below. I tried it with a new user and fresh ~/.config/libreoffice profile, running in Unity, and could still reproduce the problem. 1. Open LibreOffice and start a new Writer document. 2. Type several lines of text uninterrupted and then, without ending the paragraph, attempt to move the cursor one line up with the keyboard 3. Contrast resulting cursor behavior to that of virtually every other word processor and text editor (it usually ends up anywhere except directly one line up or down, often appearing at the very end or beginning of the line or somewhere entirely different instead). 4. Repeatedly pressing up or down immediately after this may make the inconsistent movement more obvious (it starts to behave normally, and then after more text is typed it jumps around incorrectly again with up/down movement). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Jul 21 02:07:30 2016 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-04-11 (100 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-04-26 (85 days ago) XsessionErrors: (process:5806): indicator-sound-WARNING **: volume-control-pulse.vala:744: Unable to connect to dbus server at 'unix:path=/run/user/1000/pulse/dbus-socket': Could not connect: No such file or directory (gnome-software:5821): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered (gnome-software:5821): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered cinnamon-session[5571]: WARNING: t+24.67429s: Could not launch application 'telepathy-indicator.desktop': Unable to start application: Failed to execute child process "telepathy-indicator" (No such file or directory) (cinnamon:5773): Cjs-WARNING **: JS ERROR: TypeError: this.actor is null ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1605101 Title: Writer: Up and down keys move cursor to random line positions instead of directly up or down Status in libreoffice package in Ubuntu: New Bug description: Immediately after writing some text in Writer, using the up and down keyboard keys to move the text cursor results in the cursor moving to unpredictable horizontal positions on the adjacent line (or in rare cases, even *several* lines away) instead of in the expected position, directly above or below. I tried it with a new user and fresh ~/.config/libreoffice profile, running in Unity, and could still reproduce the problem. 1. Open LibreOffice and start a new Writer document. 2. Type several lines of text uninterrupted and then, without ending the paragraph, attempt to move the cursor one line up with the keyboard 3. Contrast resulting cursor behavior to that of virtually every other word processor and text editor (it usually ends up anywhere except directly one line up or down, often appearing at the very end or beginning of the line or somewhere entirely different instead). 4. Repeatedly pressing up or down immediately after this may make the inconsistent movement more obvious (it starts to behave normally, and then after more text is typed it jumps around incorrectly again with up/down movement). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Jul 21 02:07:30 2016 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-04-11 (100 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice
[Desktop-packages] [Bug 452313] Re: Unclutter causes text input cursor to blink in unfocused windows
It took me forever to track this problem to unclutter. It was driving me crazy (the cursor blinking gave me false cues as to which window was focused and regularly caused me to begin typing in unintended windows). Another solution might be to use a rewrite of unclutter that uses X's xfixes extensions rather than the sneaky hacks the original unclutter uses: https://github.com/Airblader/unclutter-xfixes I built and have been trying it for about a week and haven't encountered any more cursor blink weirdness. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unclutter in Ubuntu. https://bugs.launchpad.net/bugs/452313 Title: Unclutter causes text input cursor to blink in unfocused windows Status in unclutter package in Ubuntu: New Bug description: When hovering the mouse cursor over a text input widget of an unfocused window, the text input cursor will start blinking in that widget when the Unclutter timeout expires. The window does not receive focus; key presses do not go to the window. Steps to reproduce: 1. Run unclutter 2. Open two Terminal windows. 3. Click one of them. 4. Hover the mouse cursor over the other Terminal until the unclutter timeout expires (5 s default). Expected result: 1. The mouse cursor disappears. Actual result: 1. The mouse cursor disappears. 2. The text input cursor starts blinking in the unfocused Terminal; the unfocused Terminal remains unfocused. The text input cursor also keeps blinking in the focused Terminal, i.e., two text input cursor are now blinking, but key presses only go the the focused one. ProblemType: Bug Architecture: amd64 Date: Thu Oct 15 18:10:44 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: ubuntu-desktop 1.172 ProcEnviron: PATH=(custom, user) LANG=ro_RO.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.45-generic SourcePackage: ubuntu-meta Uname: Linux 2.6.31-13-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unclutter/+bug/452313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1231588] Re: Running unclutter without "-noevent" causes focus problems for Firefox and Thunderbird
I was being driven up the wall with this problem for a long time (even
in a non-Ubuntu distro) and couldn't for the life of me figure out what
was going on until someone mentioned Unclutter! (I was blaming the
window manager, GUI toolkits, etc.--I never would have suspected
unclutter.) It does indeed seem to cause problems.
I sort of worry that -noevent could potentially cause other problems,
though. Apparently unclutter uses a lot of funky hacks to do its work
which causes weird things to happen in general. There's a rewrite of it
using the x11-xfixes extension which looks like a much cleaner solution:
https://github.com/Airblader/unclutter-xfixes
I found it fairly easy to build, and so far I haven't seen any problems
or weird behavior while using it. It would be nice if it could be
considered for inclusion in the Ubuntu repos.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unclutter in Ubuntu.
https://bugs.launchpad.net/bugs/1231588
Title:
Running unclutter without "-noevent" causes focus problems for Firefox
and Thunderbird
Status in Mozilla Firefox:
Won't Fix
Status in unclutter package in Ubuntu:
Confirmed
Bug description:
I have found in the last day or so that Firefox windows do not accept
focus when they are clicked upon. The focus (and key and mouse events)
are still sent to a different window even after it has been selected
for the foreground by click or ALT+TAB,ALT+`.
Initially I experienced this on a dual-head display, but even when the
window is moved from the external monitor to the built-in laptop
monitor, events are routed to the wrong firefox window.
This issue has survived an apt-get upgrade and a reboot, and is still
occurring.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: firefox 24.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic i686
AddonCompatCheckDisabled: False
ApportVersion: 2.12.4-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: cefn 4062 F pulseaudio
BuildID: 20130917154333
Channel: Unavailable
Date: Thu Sep 26 18:07:55 2013
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-08-15 (42 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386
(20130626)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.23 metric
9
MarkForUpload: True
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
Java(TM) Plug-in 10.40.2 -
/usr/lib/jvm/java-7-oracle/jre/lib/i386/libnpjp2.so
Gnome Shell Integration -
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
Silverlight Plug-In - /usr/lib/pipelight/libpipelight.so (pipelight)
iTunes Application Detector -
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
(rhythmbox-mozilla)
PrefSources:
prefs.js
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ubu...@ubuntu.com/defaults/preferences/001ubuntu-gnome-mods.js
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=24.0/20130917154333 (In use)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
gnome-shell 3.8.4-0ubuntu5
pipelight 0.1-4-0~ubuntu13.10.1
rhythmbox-mozilla 2.99.1-0ubuntu1
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.50
dmi.board.asset.tag: 00
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias:
dmi:bvnTOSHIBA:bvrVersion1.50:bd10/23/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE R600
dmi.product.version: PPR61E-00Q00CEN
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1231588/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 435831] Re: unclutter shouldn't be enabled by default
I think I have to agree. I wasn't expecting it to be enabled for all users, and it took me a while to discover that it was getting launched twice and why (because I had already added it to my startup manually with the options I wanted). I can appreciate trying to make it easy for the average user to figure out how to use it given that it lacks a GUI, but auto-launching it globally forces it on users who might not want it and also gets in the way of users launching it with their own command-line options. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unclutter in Ubuntu. https://bugs.launchpad.net/bugs/435831 Title: unclutter shouldn't be enabled by default Status in unclutter package in Ubuntu: Confirmed Bug description: Binary package hint: unclutter When you install unclutter it starts automatically every time you boot your computer. This is set in '/etc/default/unclutter'. It can be confusing for many users (it was for me). I believe the default should be changed so that the user has to enable it. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unclutter/+bug/435831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1470235] Re: PolicyKit high memory usage
This happened to me, too. I installed Multi-Core System Monitor for just a moment and noticed the steadily growing memory usage. Worse, removing the applet did not stop the leak. The leak didn't stop until the next system reboot (presumably restarting polkitd would have also worked, but I didn't try it since I wasn't sure how safe it was). But since there's no way to know if this was the trigger for the original bug report or earlier commenters, perhaps the MCSM case should be opened as a separate, specific bug against policykit? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage Status in policykit-1 package in Ubuntu: Confirmed Bug description: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using > 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
