[Desktop-packages] [Bug 580814] Re: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file()
Thank you, Paul, I reviewed reviewed the package hunspell-bg version 1:6.2.0-1, which will be included in 19.04 and noticed that the dictionaries are already encoded in UTF-8 and not in CP1251, which is the case with the current version 1:6.1.1-1. As a result I expect the problem to be fully fixed in 19.04. -- 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/580814 Title: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file() Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox Using firefox-3.6.3+nobinonly-0ubuntu4 on amd64, Ubuntu 10.04. When trying to navigate to a launchpad page, for example https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/563181, firefox crashes with a segmentation fault. The problem persists when running firefox in safe mode with all addons disabled. The debugging information should be attached to this report. ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 CrashCounter: 1 Date: Sat May 15 09:14:15 2010 ExecutablePath: /usr/lib/firefox-3.6.3/firefox-bin FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcCmdline: /usr/lib/firefox-3.6.3/firefox-bin ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=bg_BG.utf8 Signal: 11 SourcePackage: firefox StacktraceTop: AffixMgr::parse_file (this=0x7fffd8be4000, AffixMgr (this=0x7fffd8be4000, affpath=0x0, Hunspell (this=0x7fffd85d67a0, mozHunspell::SetDictionary (this=0x7fffd82fa9c0, mozSpellChecker::SetCurrentDictionary ( Title: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file() UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare video XsessionErrors: (polkit-gnome-authentication-agent-1:1885): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nm-applet:1882): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed (gnome-terminal:2093): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed (gnome-terminal:3481): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/580814/+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 1781597] Re: [SRU] WoWLAN settings are not supported
** Changed in: network-manager (Ubuntu Cosmic) Importance: Undecided => Wishlist ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1781597 Title: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Status in network-manager source package in Cosmic: Fix Released Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+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 1637988] Re: gvfsd-nfs not present in gvfs-backends, why?
Can this please be backported to 18.04, give it's 10 year LTS status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1637988 Title: gvfsd-nfs not present in gvfs-backends, why? Status in gvfs package in Ubuntu: Fix Released Bug description: We're at the end of 2016 and it's still impossible to browse nfs shares through nautilus, even though this is supported since version 1.23 of gvfs. What's keeping gvfsd-nfs out of the gvfs-backends package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+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 1818371] Re: Simple Scan images are too dark at resolutions > 75ppi.
Ubuntu 18.04.2 Canon Pixma TS6220 These issues are similar to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) The output always contains the images of what ever is on the platen on a "full size" white background; i.e., unlike scangearmp2, if there is a 4” x 6” photo on the platen, the output is a letter size white background with the 4” x 6” image scaled down. 2) Only images at resolutions of 75 ppi are acceptable. When cropped in Gimp, and size adjusted to 4” x 6”, this works out to 300 ppi. The scanned image of photos at all resolutions greater than 75 ppi are very dark/saturated – beyond my ability to correct. 3) The adjustments for Brightness and Contrast have little, if any, affect on the output for scans at resolutions > 75 ppi. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1818371 Title: Simple Scan images are too dark at resolutions > 75ppi. Status in simple-scan package in Ubuntu: New Bug description: Ubuntu 18.04.2 Canon Pixma TS6220 These issues are identical to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) I am able to move the dashed lines to frame the print to be scanned, but the output always contains the images of what ever is on the platen on a "full size" white background. 2) I have selected “inches” as the unit of measurement, but the preview window has “px” in the upper left corner, and the dimensions in the windows at the bottom of the main menu are in pixels. These dimensions do not change as I adjust the frame of the photo to be scanned and always read 2480*3507*24 (24.9MB). 3) There are no length markings along the side or top of the preview window. 4) In Advanced Options, the UOM displays “px”. The sliders change as I adjust the frame, but for a 4” x 6” photo in the upper left corner, the lower right corner is shown to be .00235x, .00154y. 5) The scanned image of the photos is very dark/saturated – beyond my ability to correct. 6) Max scan resolution in the main menu is only 300, whereas it is 1200 with the HP scanner. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Mar 1 20:59:54 2019 InstallationDate: Installed on 2018-08-04 (210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire XC-603 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1818371/+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 1818371] Re: Simple Scan images are too dark at resolutions > 75ppi.
** Summary changed: - Simple Scan does not scan only the area which is framed after "preview" + Simple Scan images are too dark at resolutions > 75ppi. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1818371 Title: Simple Scan images are too dark at resolutions > 75ppi. Status in simple-scan package in Ubuntu: New Bug description: Ubuntu 18.04.2 Canon Pixma TS6220 These issues are identical to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) I am able to move the dashed lines to frame the print to be scanned, but the output always contains the images of what ever is on the platen on a "full size" white background. 2) I have selected “inches” as the unit of measurement, but the preview window has “px” in the upper left corner, and the dimensions in the windows at the bottom of the main menu are in pixels. These dimensions do not change as I adjust the frame of the photo to be scanned and always read 2480*3507*24 (24.9MB). 3) There are no length markings along the side or top of the preview window. 4) In Advanced Options, the UOM displays “px”. The sliders change as I adjust the frame, but for a 4” x 6” photo in the upper left corner, the lower right corner is shown to be .00235x, .00154y. 5) The scanned image of the photos is very dark/saturated – beyond my ability to correct. 6) Max scan resolution in the main menu is only 300, whereas it is 1200 with the HP scanner. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Mar 1 20:59:54 2019 InstallationDate: Installed on 2018-08-04 (210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire XC-603 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1818371/+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 1808226] Re: Rotated screen is blank in Wayland sessions [Failed to set CRTC mode 1600x1200: No space left on device]
Just installed Ubuntu 18.04 LTS on HP EliteBook 8470p. Got the same
error on fresh boot. It probebly was because of ubuntu now uses screen
rotation gyro(?) and started to rotate screen. Anyway, to steps to fix.
1. CTRL+ALT+F2 to get into console.
2. Login
3. Do
https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux
4. Do
https://askubuntu.com/questions/1035209/how-to-turn-off-screen-rotation-in-ubuntu-18-04-lts
--
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/1808226
Title:
Rotated screen is blank in Wayland sessions [Failed to set CRTC mode
1600x1200: No space left on device]
Status in gnome-shell package in Ubuntu:
Fix Released
Bug description:
Using "ubuntu-gnome-desktop" ("vanilla-gnome-desktop" also installed)
with external 1600x1200 monitor rotated 90 deg. Monitor connected via
HDMI and using Inel i915 driver.
1) Login to "Ubuntu" session. Use Settings -> Display to rotate monitor 90
deg left. Accept new settings. Logout.
2) Login to "Ubuntu on Wayland" External monitor gets no signal.
Following line at the end of 'dmesg' output seems to relate to the issue:
Dec 12 14:37:46 saugage gnome-shell[6125]: Failed to set CRTC mode 1600x1200:
No space left on device
Searching for this message reveals several reports of Gnome Shell
crashing at this point. It does not crash for me but the external
monitor remains unusable.
hbarta@saugage:/var/log$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
hbarta@saugage:/var/log$
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:44:42 2018
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US
SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+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 1818382] [NEW] Totem doesn't render videos correctly
Public bug reported: On Ubuntu 18.04, 18.10 and one can only assume 19.04 Videos application doesn't render most of the videos correctly but instead renders something like a fake heat map of the video. I've attached the screenshot to show you the bug. Here is also download the video I was watching, a Big Buck Bunny by Blender Foundation: https://drive.google.com/drive/folders/1uTEk_dIdlAfKG4-s2he4bf9uijqbIY1e?usp=sharing $ neofetch OS: Ubuntu 18.10 x86_64 Kernel: 4.20.13-042013-generic Uptime: 10 hours, 13 mins Packages: 2296 (dpkg), 38 (flatpak), 43 (snap) Shell: bash 4.4.19 Resolution: 1680x1050, 1920x1200 DE: GNOME 3.30.1 WM: GNOME Shell WM Theme: Adwaita Theme: Adwaita-dark [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: AMD Ryzen Threadripper 1900X 8- (16) @ 3.800GHz GPU: AMD ATI Radeon RX Vega 64 Memory: 4447MiB / 15961MiB Now I've tested this on Ubuntu 18.04 and 18.10 with amdgpu that comes in the kernel, with amdgpu-pro installed and with ROCm. All 6 tests showed the same result. Also the result stayed the same on the stock kernel and the latest kernel. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 Uname: Linux 4.20.13-042013-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 02:47:03 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-06 (86 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "Big_Buck_Bunny" https://bugs.launchpad.net/bugs/1818382/+attachment/5243000/+files/Screenshot%20from%202019-03-03%2002-53-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1818382 Title: Totem doesn't render videos correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: On Ubuntu 18.04, 18.10 and one can only assume 19.04 Videos application doesn't render most of the videos correctly but instead renders something like a fake heat map of the video. I've attached the screenshot to show you the bug. Here is also download the video I was watching, a Big Buck Bunny by Blender Foundation: https://drive.google.com/drive/folders/1uTEk_dIdlAfKG4-s2he4bf9uijqbIY1e?usp=sharing $ neofetch OS: Ubuntu 18.10 x86_64 Kernel: 4.20.13-042013-generic Uptime: 10 hours, 13 mins Packages: 2296 (dpkg), 38 (flatpak), 43 (snap) Shell: bash 4.4.19 Resolution: 1680x1050, 1920x1200 DE: GNOME 3.30.1 WM: GNOME Shell WM Theme: Adwaita Theme: Adwaita-dark [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: AMD Ryzen Threadripper 1900X 8- (16) @ 3.800GHz GPU: AMD ATI Radeon RX Vega 64 Memory: 4447MiB / 15961MiB Now I've tested this on Ubuntu 18.04 and 18.10 with amdgpu that comes in the kernel, with amdgpu-pro installed and with ROCm. All 6 tests showed the same result. Also the result stayed the same on the stock kernel and the latest kernel. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 Uname: Linux 4.20.13-042013-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 02:47:03 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-06 (86 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1818382/+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 1818374] [NEW] Firefox: "No video with supported format and MIME type found"
Public bug reported: When I open sites in the Mozilla Firefox Quantum 65.0.1 and click to the video, I get the error: "No video with supported format and MIME type found". My OS is Ubuntu 19.04 (alpha). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 65.0.1+build2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: artyom 999 F pulseaudio BuildID: 20190214235031 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 00:16:23 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-03-02 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.100 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=65.0.1/20190214235031 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832E dmi.board.vendor: HP dmi.board.version: 26.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd05/17/2018:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G6 Notebook PC dmi.product.sku: 3DN65ES#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1818374 Title: Firefox: "No video with supported format and MIME type found" Status in firefox package in Ubuntu: New Bug description: When I open sites in the Mozilla Firefox Quantum 65.0.1 and click to the video, I get the error: "No video with supported format and MIME type found". My OS is Ubuntu 19.04 (alpha). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 65.0.1+build2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: artyom 999 F pulseaudio BuildID: 20190214235031 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 00:16:23 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-03-02 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.100 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=65.0.1/20190214235031 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832E dmi.board.vendor: HP dmi.board.version: 26.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd05/17/2018:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G6 Notebook PC dmi.product.sku: 3DN65ES#ACB dmi.product.version:
[Desktop-packages] [Bug 1818371] [NEW] Simple Scan does not scan only the area which is framed after "preview"
Public bug reported: Ubuntu 18.04.2 Canon Pixma TS6220 These issues are identical to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) I am able to move the dashed lines to frame the print to be scanned, but the output always contains the images of what ever is on the platen on a "full size" white background. 2) I have selected “inches” as the unit of measurement, but the preview window has “px” in the upper left corner, and the dimensions in the windows at the bottom of the main menu are in pixels. These dimensions do not change as I adjust the frame of the photo to be scanned and always read 2480*3507*24 (24.9MB). 3) There are no length markings along the side or top of the preview window. 4) In Advanced Options, the UOM displays “px”. The sliders change as I adjust the frame, but for a 4” x 6” photo in the upper left corner, the lower right corner is shown to be .00235x, .00154y. 5) The scanned image of the photos is very dark/saturated – beyond my ability to correct. 6) Max scan resolution in the main menu is only 300, whereas it is 1200 with the HP scanner. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Mar 1 20:59:54 2019 InstallationDate: Installed on 2018-08-04 (210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire XC-603 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1818371 Title: Simple Scan does not scan only the area which is framed after "preview" Status in simple-scan package in Ubuntu: New Bug description: Ubuntu 18.04.2 Canon Pixma TS6220 These issues are identical to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) I am able to move the dashed lines to frame the print to be scanned, but the output always contains the images of what ever is on the platen on a "full size" white background. 2) I have selected “inches” as the unit of measurement, but the preview window has “px” in the upper left corner, and the dimensions in the windows at the bottom of the main menu are in pixels. These dimensions do not change as I adjust the frame of the photo to be scanned and always read 2480*3507*24 (24.9MB). 3) There are no length markings along the side or top of the preview window. 4) In Advanced Options, the UOM displays “px”. The sliders change as I adjust the frame, but for a 4” x 6” photo in the upper left corner, the lower right corner is shown to be .00235x, .00154y. 5) The scanned image of the photos is very dark/saturated – beyond my ability to correct. 6) Max scan resolution in the main menu is only 300, whereas it is 1200 with the HP scanner. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Mar 1 20:59:54 2019 InstallationDate: Installed on 2018-08-04 (210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire XC-603 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3
[Desktop-packages] [Bug 580814] Re: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file()
In the current development release (19.04) myspell-bg is a transitional package that depends on hunspell-bg. May be your problem will be fixed by that change in future Ubuntu releases? -- 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/580814 Title: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file() Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox Using firefox-3.6.3+nobinonly-0ubuntu4 on amd64, Ubuntu 10.04. When trying to navigate to a launchpad page, for example https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/563181, firefox crashes with a segmentation fault. The problem persists when running firefox in safe mode with all addons disabled. The debugging information should be attached to this report. ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 CrashCounter: 1 Date: Sat May 15 09:14:15 2010 ExecutablePath: /usr/lib/firefox-3.6.3/firefox-bin FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcCmdline: /usr/lib/firefox-3.6.3/firefox-bin ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=bg_BG.utf8 Signal: 11 SourcePackage: firefox StacktraceTop: AffixMgr::parse_file (this=0x7fffd8be4000, AffixMgr (this=0x7fffd8be4000, affpath=0x0, Hunspell (this=0x7fffd85d67a0, mozHunspell::SetDictionary (this=0x7fffd82fa9c0, mozSpellChecker::SetCurrentDictionary ( Title: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file() UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare video XsessionErrors: (polkit-gnome-authentication-agent-1:1885): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nm-applet:1882): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed (gnome-terminal:2093): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed (gnome-terminal:3481): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/580814/+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 1434830] Re: Clicking on Files bookmark doesn't open the requested folder but gives error message
Sorry for the delay in getting back to you Svilen. May be an upstream report is long overdue? See comment #3. ** Changed in: nautilus (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1434830 Title: Clicking on Files bookmark doesn't open the requested folder but gives error message Status in nautilus package in Ubuntu: Confirmed Bug description: Setup: Ubuntu and Windows 7 installed on the same PC for dual-boot; on disk there is at least one NTFS partition for Windows, and Ubuntu is installed in a different partition. Steps to reproduce: - Open "Files", and navigate to any folder in the NTFS partition; - Bookmark that folder (e.g. with Ctrl+D); - Reboot the PC and log in with Ubuntu; - Open "Files", and click on the previously created bookmark (under "Bookmarks" on the bar to the left); - An error message pops-up "Unable to find the requested file. Please check the spelling and try again"; it should open to the bookmarked folder instead. The issue is systematic. Workaround: - After logging in, and opening "Files", first click on the NTFS partition in the bar to the left (under "Devices"), and then click on the bookmark. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15.1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 21 15:36:41 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified', 'permissions', 'owner', 'group']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'permissions', 'owner', 'group', 'mime_type', 'where']" InstallationDate: Installed on 2014-11-25 (115 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1434830/+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 1818360] [NEW] system heating and fan running after boot.
Public bug reported: After installing all updates on my DELL XPS 13 2018, I have the fan making a lot of noise and system heating. Looking into the processes, Xorg is eating 28% of the CPU, and also update-mime-dat(abase). This is now a frequent problem and it's eating the battery and slowing down other applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 21:58:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-09-01 (182 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=2fa5defd-84ab-4127-9599-272eec4b5861 ro quiet splash mem_sleep_default=deep vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance ubuntu ** Attachment added: "top command output" https://bugs.launchpad.net/bugs/1818360/+attachment/5242910/+files/topOutput -- 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/1818360 Title: system heating and fan running after boot. Status in xorg package in Ubuntu: New Bug description: After installing all updates on my DELL XPS 13 2018, I have the fan making a lot of noise and system heating. Looking into the processes, Xorg is eating 28% of the CPU, and also update-mime-dat(abase). This is now a frequent problem and it's eating the battery and slowing down other applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 21:58:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-09-01 (182 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=2fa5defd-84ab-4127-9599-272eec4b5861 ro quiet splash mem_sleep_default=deep vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
Confirmed fixed in Pop_OS 18.10 using the test case provided. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Triaged Status in mutter source package in Cosmic: Fix Committed Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+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 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
** Changed in: mutter Status: In Progress => Fix Released -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: Fix Released Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+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 1818274] Re: Cannot change screenshot directory
** Changed in: gnome-settings-daemon Status: Unknown => Won't Fix ** Changed in: gnome-settings-daemon Importance: Unknown => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1818274 Title: Cannot change screenshot directory Status in GNOME Settings Daemon: Won't Fix Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: Expected: Be able to change the directory where the screenshots are saved, either from Settings (GUI) or from gsettings (cli). What happens: Screenshots are unconditionally saved to the Pictures directory (XDG_PICTURES_DIR). Temporary Workaround: Use a specific extension: Screenshot Locations (https://extensions.gnome.org/extension/1179/screenshot-locations/) Previous discussion: The bug was previously reported 5 years ago on bugzilla 699642 (https://bugzilla.gnome.org/show_bug.cgi?id=699642) and closed as WONTFIX. I'm reporting here again, as I hope the time is ripe for a reconsideration, given how many users are affected and willing to see this solved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Mar 1 19:50:31 2019 InstallationDate: Installed on 2019-02-03 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1818274/+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 1704765] Re: can't drag file from desktop to folder window on Artful
Problem remains in 18:10, Wayland, Gnome 3.30.1, 64-bit, 4.18.0-15-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1704765 Title: can't drag file from desktop to folder window on Artful Status in Nautilus: Expired Status in nautilus package in Ubuntu: Triaged Bug description: I'm running Ubuntu 17.10 (Artful). If I create a text file on my desktop and then attempt to drag it into a Nautilus folder window, it fails: when I release the mouse cursor over the folder window nothing happens and the file is not moved. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1704765/+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 1815889]
(In reply to Daniel P. Berrange from comment #3) > (In reply to Ahzo from comment #2) > > To check for the availability of the syscall, one can try it in a child > > process and see if the child is terminated by a signal, e.g. like this: > > Afraid not, QEMU's seccomp filter blocks use of fork() too :-) Maybe it should, at least when using the spawn=deny option, but currently it doesn't. That option only blocks the fork, vfork and execve syscalls, but glibc's fork() function uses the clone syscall, and thus continues to work. However, that behavior might be different when using other C library implementations, so it wouldn't be correct to rely on this. One could use clone() instead of fork(), but future versions of qemu might block the clone syscall, as well. Unfortunately, I'm not aware of a proper solution for this bug short of adding a new API to the kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Confirmed Status in QEMU: New Status in mesa package in Ubuntu: New Status in qemu package in Ubuntu: Triaged Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1771396] Re: Pasted Twitter links are invisble.
In firefox, the pasted url is there too, but invisible.
See attachment.
Only show up when going to plain text mode.
I cannot select it, even though it is there.
Only been able to reproduce this with twitter's "Copy Link To Tweet"
function.
** Attachment added: "How it looks in firefox"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1771396/+attachment/5242875/+files/firefox.png
--
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/1771396
Title:
Pasted Twitter links are invisble.
Status in firefox package in Ubuntu:
Incomplete
Bug description:
If I:
1. point my browser to twitter.com and select a random tweet.
2. And then from the Drop Down menu, select: "Copy Link to Tweet."
3. And then paste that link into a gmail composition
Then the link will not show up, although it is there.
It's almost as if it is pasted as white text on white background?
With the difference that even when selecting it, it still doesn't show.
The only way to make it show up, is change your gmail composition mode to
'Plain text mode.'
Once you do that, you see that the link is actually there.
I expected, instead, to have the link visible after pasting it into gmail.
Note: same issue happens if I use Chromium browser instead.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 60.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bram 1345 F pulseaudio
/dev/snd/controlC0: bram 1345 F pulseaudio
BuildID: 20180509234620
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue May 15 10:27:22 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-04-29 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
default via 10.0.1.1 dev enp5s1 proto dhcp metric 100
10.0.1.0/24 dev enp5s1 proto kernel scope link src 10.0.1.78 metric 100
169.254.0.0/16 dev enp5s1 scope link metric 1000
IwConfig:
enp5s1no wireless extensions.
enp3s0no wireless extensions.
lono wireless extensions.
MostRecentCrashID: bp-64ea59d4-fe25-4952-b630-d4b561180214
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_CA.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=60.0/20180509234620 (In use)
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2108
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2108:bd06/02/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1771396/+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 1771396] Re: Pasted Twitter links are invisble.
Yes, still happens in Firefox 65.0.1
Does no longer happen in Chromium Version 71.0.3578.98 (Official Build)
Built on Ubuntu , running on Ubuntu 18.04 (64-bit)
Attached is how it looks in chromium after paste: note that colour
formatting.
** Attachment added: "How it looks in chromium"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1771396/+attachment/5242874/+files/chromium.png
--
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/1771396
Title:
Pasted Twitter links are invisble.
Status in firefox package in Ubuntu:
Incomplete
Bug description:
If I:
1. point my browser to twitter.com and select a random tweet.
2. And then from the Drop Down menu, select: "Copy Link to Tweet."
3. And then paste that link into a gmail composition
Then the link will not show up, although it is there.
It's almost as if it is pasted as white text on white background?
With the difference that even when selecting it, it still doesn't show.
The only way to make it show up, is change your gmail composition mode to
'Plain text mode.'
Once you do that, you see that the link is actually there.
I expected, instead, to have the link visible after pasting it into gmail.
Note: same issue happens if I use Chromium browser instead.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 60.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bram 1345 F pulseaudio
/dev/snd/controlC0: bram 1345 F pulseaudio
BuildID: 20180509234620
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue May 15 10:27:22 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-04-29 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
default via 10.0.1.1 dev enp5s1 proto dhcp metric 100
10.0.1.0/24 dev enp5s1 proto kernel scope link src 10.0.1.78 metric 100
169.254.0.0/16 dev enp5s1 scope link metric 1000
IwConfig:
enp5s1no wireless extensions.
enp3s0no wireless extensions.
lono wireless extensions.
MostRecentCrashID: bp-64ea59d4-fe25-4952-b630-d4b561180214
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_CA.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=60.0/20180509234620 (In use)
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2108
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2108:bd06/02/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1771396/+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 1818348] [NEW] When window title bar controls are on left, close window button is cut off in title bar of Disks application
Public bug reported: When you configure your window title bar buttons to be on the left instead of the right in the tweaks app, the close window button is cut off in the Disks app. I don't see this behavior in other apps. See attached screenshot for illustration of what I mean. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-disk-utility 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 12:32:43 2019 InstallationDate: Installed on 2019-03-02 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "upper left corner of Disks app window" https://bugs.launchpad.net/bugs/1818348/+attachment/5242869/+files/2019-03-02_12-31.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1818348 Title: When window title bar controls are on left, close window button is cut off in title bar of Disks application Status in gnome-disk-utility package in Ubuntu: New Bug description: When you configure your window title bar buttons to be on the left instead of the right in the tweaks app, the close window button is cut off in the Disks app. I don't see this behavior in other apps. See attached screenshot for illustration of what I mean. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-disk-utility 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 12:32:43 2019 InstallationDate: Installed on 2019-03-02 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1818348/+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 1818347] [NEW] LibreOffice don't go full screen but sometimes it does.
Public bug reported: Install LibreOffice and try to go fullscreen. 1 out 10 chances, you will be getting fullscreen otherwise there is still top notch & sidebar showing up whenever u go fullscreen in LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 23:09:13 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2018-12-24 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=aad43495-2006-41af-bcb1-f91673ac405e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2018:svnDellInc.:pnInspiron5548:pvrA09:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1818347 Title: LibreOffice don't go full screen but sometimes it does. Status in xorg package in Ubuntu: New Bug description: Install LibreOffice and try to go fullscreen. 1 out 10 chances, you will be getting fullscreen otherwise there is still top notch & sidebar showing up whenever u go fullscreen in LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 23:09:13 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2018-12-24 (68 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=aad43495-2006-41af-bcb1-f91673ac405e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2018:svnDellInc.:pnInspiron5548:pvrA09:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1818274] Re: Cannot change screenshot directory
** Bug watch added: GNOME Bug Tracker #699642 https://bugzilla.gnome.org/show_bug.cgi?id=699642 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=699642 Importance: Unknown Status: Unknown ** Description changed: Expected: Be able to change the directory where the screenshots are saved, either from Settings (GUI) or from gsettings (cli). What happens: Screenshots are unconditionally saved to the Pictures directory (XDG_PICTURES_DIR). Temporary Workaround: Use a specific extension: Screenshot Locations (https://extensions.gnome.org/extension/1179/screenshot-locations/) Previous discussion: The bug was previously reported 5 years ago on bugzilla 699642 (https://bugzilla.gnome.org/show_bug.cgi?id=699642) and closed as WONTFIX. I'm reporting here again, as I hope the time is ripe for a reconsideration, given how many users are affected and willing to see this solved. - - Tracked on GitLab: https://gitlab.gnome.org/GNOME/gnome-settings- - daemon/issues/153 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Mar 1 19:50:31 2019 InstallationDate: Installed on 2019-02-03 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1818274 Title: Cannot change screenshot directory Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: Expected: Be able to change the directory where the screenshots are saved, either from Settings (GUI) or from gsettings (cli). What happens: Screenshots are unconditionally saved to the Pictures directory (XDG_PICTURES_DIR). Temporary Workaround: Use a specific extension: Screenshot Locations (https://extensions.gnome.org/extension/1179/screenshot-locations/) Previous discussion: The bug was previously reported 5 years ago on bugzilla 699642 (https://bugzilla.gnome.org/show_bug.cgi?id=699642) and closed as WONTFIX. I'm reporting here again, as I hope the time is ripe for a reconsideration, given how many users are affected and willing to see this solved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Mar 1 19:50:31 2019 InstallationDate: Installed on 2019-02-03 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1818274/+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 220263]
If you uncheck "Use System Colors" it's no longer a problem. -- 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/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+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 1802569] Re: RM openssl1.0 from Ubuntu
** Changed in: openssl1.0 (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1802569 Title: RM openssl1.0 from Ubuntu Status in freerdp package in Ubuntu: Fix Released Status in guacamole-client package in Ubuntu: Fix Released Status in guacamole-server package in Ubuntu: Fix Released Status in libpam-freerdp package in Ubuntu: Fix Released Status in moonshot-trust-router package in Ubuntu: Fix Released Status in netkit-ftp-ssl package in Ubuntu: Fix Released Status in openssl1.0 package in Ubuntu: Fix Released Status in pidentd package in Ubuntu: Fix Released Status in freerdp package in Debian: Fix Released Status in openssl1.0 package in Debian: Fix Released Bug description: RM openssl1.0 from Ubuntu reconserver has multiple ftbfs issues / bugs. freerdp is superseeded by freerdp2. = Step 1: migrate https://launchpad.net/ubuntu/+source/guacamole-server/0.9.9-2ubuntu2 as it drops dependency on freerdp Step 2: remove libpam-freerdp ; OpenSSL 1.0 removal and freerdp Step 3: remove freerdp -> the only outstanding reverse-dep (apart from step1,2) is ltsp-client which has an alternative: 'freerdp2-x11 | freerdp-x11 | rdesktop' Step 4: remove openssl1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1802569/+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 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
Hi Daniel. I can't even reproduce it in 18.04 anymore. I tried: - Booting 18.04.2 from a usb disk - The 18.04 GNOME Wayland session (what I'm trying now to avoid a bunch of other bugs) - The 18.04 default Ubuntu Xorg session all of them seem to be showing reasonable <1% gnome-shell CPU usage when showing just a gnome-terminal running top. Don't know what fixed it but it does seem fixed. I can live boot 18.10 if that's useful or even 19.04 if there are images for that already somewhere. -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+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 1817128] Re: gnome-keyring not automatically unlocked on login
Hello guys Perfect! Many thanks to all involved for the prompt resolution of the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1817128 Title: gnome-keyring not automatically unlocked on login Status in gnome-keyring package in Ubuntu: Fix Released Bug description: Hi After initializing and filling the login screen, at the start screen prompts for password to unlock the session keyring. Is this normal on Ubuntu disk 19.04.02? Note: When filling the login screen to start the micro, should it not be unlocked automatically? Attached the image of the request I fired it. Thank you ** Hi Após inicialização e preenchimento da tela de login, ao iniciar a tela pede senha para desbloqueio do chaveiro de sessão. Isso é normal no Ubuntu disco 19.04.02? Obs: Quando do preenchimento da tela de login para iniciar o micro o desbloqueio não deveria ser automático? Em anexo a imagem da solicitação de desboquei-o. Obrigado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
Attached. ** Attachment added: "dump.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812527/+attachment/5242850/+files/dump.txt -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
I only tested bionic, the stereo playback works seemingly flawless. The
low volume problem is indeed still present, but as Dave pointed out,
changing the headphone gain from -16 (50%) to 0 (100%) solves it (Thanks
Dave!).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
mono playback
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
Fix Committed
Status in pulseaudio source package in Cosmic:
Fix Committed
Status in pulseaudio source package in Disco:
Fix Released
Bug description:
[Impact]
* User is only able to get mono audio from steelseries headsets
because they provide both a stereo and mono output. PA selects the
mono output by default.
* This should be backported to stable releases because this fix is
isolated to code that only applies to the affected headsets.
Additionally other gaming headsets may be more easily enabled by adding
ATTRS{idVendor}=="", ATTRS{idProduct}=="",
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
to /lib/udev/rules.d/90-pulseaudio.rules now. Such as the Lucidsound
LS31 which I own.
* The upload fixes the bug by conditionally setting a pulseaudio
profile for the headset based on specific usb vendor and product ids
in the udev rules.
[Test Case]
1. Acquire headset.
2. Open sound settings, and click test speakers.
3. Only option available will be mono sound
[Regression Potential]
* Risk of regressions should be mitigated to those who own the
headset. In which case it is likely that their headset is already not
working.
[Other Info]
* All patches originate from upstream pulseaudio, and are documented as
such including the shas.
* I will be pursuing enabling other similar headsets in the coming weeks.
* I plan to work with upstream pulseaudio to enable my own headset and to
also make the headset templates backported here more generic.
Original Description -
There is not stereo playback only mono playback
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio
/dev/snd/controlC1: kaj1755 F pulseaudio
/dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio
/dev/snd/controlC0: kaj1755 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 21:30:50 2018
InstallationDate: Installed on 2018-03-08 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET35W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS2AV00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS2AV00
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1818338] [NEW] Add support for Chromebook keyboards
Public bug reported: Please review this patch for inclusion in Ubuntu or upstream: https://github.com/GalliumOS/xkeyboard- config/blob/master/debian/patches/chromebook.patch I have been using Gallium OS on a Chromebook and like to switch to Ubuntu. I tested the modifications on my Chromebook and they are working on the Xorg Gnome session. ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1818338 Title: Add support for Chromebook keyboards Status in xkeyboard-config package in Ubuntu: New Bug description: Please review this patch for inclusion in Ubuntu or upstream: https://github.com/GalliumOS/xkeyboard- config/blob/master/debian/patches/chromebook.patch I have been using Gallium OS on a Chromebook and like to switch to Ubuntu. I tested the modifications on my Chromebook and they are working on the Xorg Gnome session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1818338/+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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
Can anyone affected post a the result of journalctl /usr/bin/gnome-shell -b Or otherwise follow what explaind here to have a full javascript dump too. https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details #Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome- shell -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+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 580814] Re: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file()
Firefox no longer crashes because of this problem, but the spell- checking functionality still does not work in Bulgarian unless the corresponding files from the myspell-bg package are converted to UTF-8. Perhaps a separate bug needs to be opened about the problem, but the crash described definitely does not occur anymore. -- 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/580814 Title: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file() Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox Using firefox-3.6.3+nobinonly-0ubuntu4 on amd64, Ubuntu 10.04. When trying to navigate to a launchpad page, for example https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/563181, firefox crashes with a segmentation fault. The problem persists when running firefox in safe mode with all addons disabled. The debugging information should be attached to this report. ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 CrashCounter: 1 Date: Sat May 15 09:14:15 2010 ExecutablePath: /usr/lib/firefox-3.6.3/firefox-bin FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcCmdline: /usr/lib/firefox-3.6.3/firefox-bin ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=bg_BG.utf8 Signal: 11 SourcePackage: firefox StacktraceTop: AffixMgr::parse_file (this=0x7fffd8be4000, AffixMgr (this=0x7fffd8be4000, affpath=0x0, Hunspell (this=0x7fffd85d67a0, mozHunspell::SetDictionary (this=0x7fffd82fa9c0, mozSpellChecker::SetCurrentDictionary ( Title: firefox-bin crashed with SIGSEGV in AffixMgr::parse_file() UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare video XsessionErrors: (polkit-gnome-authentication-agent-1:1885): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nm-applet:1882): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed (gnome-terminal:2093): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed (gnome-terminal:3481): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/580814/+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 1818331] Re: Rhythmbox segfault since opening flac file
*** This bug is a duplicate of bug 1812683 *** https://bugs.launchpad.net/bugs/1812683 This is funny, yes. "LANG=C rhythmbox" works. Deactivated the alternative toolbar then, and it worked again. Thanks, this is a dupe. ** This bug has been marked a duplicate of bug 1812683 rhythmbox crashes when trying to play music -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1818331 Title: Rhythmbox segfault since opening flac file Status in rhythmbox package in Ubuntu: Incomplete Bug description: I hope this is no dupe. Since I opened a flac file per doubleclick on my desktop with Rhythmbox, it crashes everytime right after the start, even when started without parameters. I just started a gdb session and ran rhythmbox, maybe this in fo helps a bit. Please tell me how to help further - ATM Rhythmbox is unusable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 13:44:00 2019 InstallationDate: Installed on 2019-01-27 (33 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1818331/+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 1817128] Re: gnome-keyring not automatically unlocked on login
This bug was fixed in the package gnome-keyring - 3.31.91-1ubuntu1 --- gnome-keyring (3.31.91-1ubuntu1) disco; urgency=medium * Sync with Debian. Remaining changes: - debian/user/*, debian/gnome-keyring.links, debian/gnome-keyring.install: + Install units to start gnome-keyring with systemd if the session is using it gnome-keyring (3.31.91-1) experimental; urgency=medium * New upstream development release - Fix loging keyring not automatically unlocked on log in (LP: #1817128) -- Jeremy Bicha Sat, 02 Mar 2019 08:15:13 -0500 ** Changed in: gnome-keyring (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1817128 Title: gnome-keyring not automatically unlocked on login Status in gnome-keyring package in Ubuntu: Fix Released Bug description: Hi After initializing and filling the login screen, at the start screen prompts for password to unlock the session keyring. Is this normal on Ubuntu disk 19.04.02? Note: When filling the login screen to start the micro, should it not be unlocked automatically? Attached the image of the request I fired it. Thank you ** Hi Após inicialização e preenchimento da tela de login, ao iniciar a tela pede senha para desbloqueio do chaveiro de sessão. Isso é normal no Ubuntu disco 19.04.02? Obs: Quando do preenchimento da tela de login para iniciar o micro o desbloqueio não deveria ser automático? Em anexo a imagem da solicitação de desboquei-o. Obrigado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+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 1790816] Re: Terrible sound after update to 18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1790816 Title: Terrible sound after update to 18.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: The sound just is extremely distorted after update to 18.04. Like an old radio that's not picking up the station right. I saw a webpage about the same device I am using and tried their solution. That didn't help at all. Hope I didn't make things worse. I saw a page that mentioned the lspci command. Based on that, I guess I am using an Intel 82801 JD/DO audio card. One site said that requires an snd_hda_intel driver, but all I could find in Synaptic Package Manager was that an alsa driver and pulse audio were installed. Could the correct driver have been removed with the new installation? This computer has been kind of buggy as of late, but the audio had been working. I had problems installing this OS. Mostly it seems to be working otherwise though. 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) N: Unable to locate package pkgname 3) What you expected to happen: sound to work properly 4) What happened instead: sound distorted Hope my attempt to fix it doesn't screw up the bug report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: szettner 2030 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Sep 5 03:07:08 2018 InstallationDate: Installed on 2017-06-28 (433 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [OptiPlex 760, Analog Devices AD1984A, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-09-02 (2 days ago) dmi.bios.date: 12/03/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0D517D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd12/03/2008:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0D517D:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1790816/+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 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
I deleted all printers and waited for CUPS / driverless to find them again.
Here a few CLI outputs (which are small enough so I dare to spost them inline )
$ ls -1 /etc/cups/ppd/
Kyocera_ECOSYS_P6026cdn.ppd
Kyocera-ECOSYS-P6026cdn.ppd
Kyocera_ECOSYS_P6026cdn.ppd.O
Kyocera-ECOSYS-P6026cdn.ppd.O
$ sudo systemctl stop cups-browsed
$ ls -1 /etc/cups/ppd/
Kyocera-ECOSYS-P6026cdn.ppd
Kyocera-ECOSYS-P6026cdn.ppd.O
$ sudo systemctl stop cups-browsed
I see 2 in the GUI, why there are 4 files here - I don't know why.
Seems that cups-browsed adds the "_" separated files
$ lp -d Kyocera-ECOSYS-P6026cdn ~/.bashrc
Anfrage-ID ist Kyocera-ECOSYS-P6026cdn-52 (1 Datei(en))
$ sudo cupstestppd /etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd
/etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd: FAIL
**FAIL** Missing choice *Option18 SDCard in UIConstraints "*KCCollate
CustomBox *Option18 SDCard".
**FAIL** Missing choice *Option18 SDCard in UIConstraints "*Option18
SDCard *KCCollate CustomBox".
WARNDatei einthält gemischt CR, LF, und CR LF Zeilenmenden.
WARNSize "A5" should be "149x210mm".
WARNSize "A6" should be "105x149mm".
WARNSize "B6" should be "128x182mm".
WARNSize "OficioII" should be the Adobe standard name
"FanFoldGermanLegal".
WARNSize "P16K" should be "7,75x10,75".
WARNSize "OficioMX" should be the Adobe standard name "Oficio".
$ lpstat -e
Kyocera-ECOSYS-P6026cdn
$ lpstat -v
Gerät für Kyocera-ECOSYS-P6026cdn:
dnssd://Kyocera%20ECOSYS%20P6026cdn._ipp._tcp.local/?uuid=4509a320-003a-00ad-0042-0025074ef136
$ driverless
ipp://KM15881D.local:631/ipp/print
But where is the "get-printer-attributes-2.0.test" file - I cant find
this file.
$ ipptool -tv ipp://KM15881D.local:631/ipp/print
get-printer-attributes-2.0.test > ~/attrs.txt
ipptool: Unable to open test file get-printer-attributes-2.0.test - No such
file or directory
It seems so confusing to me as there are no reliable on/offs: sometimes the
files are available, sometimes not.
Maybe this outputs help a bit. Hope you see something in there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer workflow has bad usability/ is partly broken
Status in gnome-control-center package in Ubuntu:
Incomplete
Bug description:
Hi,
since Ubuntu uses IPP ("driverless") printing, I have a bad time using
printers. I don't know exactly which package this bug belongs to, I think it is
gnome-control-center.
I have a Kyocera EcosysP6026cdn network printer, which provides a PPD
file by the manufacturer. (But I tested this behaviour as well with
other printers from eg. Brother, etc., and on Debian and Arch linux
too). When I switch on the printer, after a few seconds, it is found
in Ubuntu and installed automatically as "Kyocera_ECOSYS_P6026cdn". So
far, so good.
1) I can't remove this printer. If I WANT to install it using another
protocol (dnss etc), it adds another printer, and I have 2 Printers.
So it should be easy to switch off "driverless" printing.
2) Using it as "Default printer" does not work. Clicking the cog
wheel, and using the menu item "Use printer by default" is clickable,
but it does not save any setting: "printers-cc-panel-WARNING **:
20:45:36.812: cups-pk-helper: setting default printer to
Kyocera_ECOSYS_P6026cdn failed: client-error-not-found"
3) "Printing Options" opens an empty dialog, see screenshot attached.
This dialog is useless.
4) The "Printer Detail" dialog shows a "null" address and links to
"(null):631", which is a 404.
I think this "driverless" printing is still in a very "unstable" state. It
helps discovering printers in new Networks where I attach too with my laptop,
and I can print there basically, But most of the day I use my own printer in my
office or at home, and I want to have my special settings for exact this
printer with color profile, duplex settings etc.
And this all is not possible with driverless printing.
So, if you don't "fix" all the not-working options in the UI, please
at least give us an option to easily switch off driverless printing at
all. I really prefer the "old school" way of installing printers.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 29 19:34:39 2019
InstallationDate: Installed on 2019-01-27 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1818331] Re: Rhythmbox segfault since opening flac file
Thank you for your bug report. Could you type 'backtrace' in gdb to get more information on the issue? Also could you try to start with another locale or to disable the alternative toolbar plugin? The issue sounds similar to bug #1812683 ** Changed in: rhythmbox (Ubuntu) Importance: Undecided => High ** Changed in: rhythmbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1818331 Title: Rhythmbox segfault since opening flac file Status in rhythmbox package in Ubuntu: Incomplete Bug description: I hope this is no dupe. Since I opened a flac file per doubleclick on my desktop with Rhythmbox, it crashes everytime right after the start, even when started without parameters. I just started a gdb session and ran rhythmbox, maybe this in fo helps a bit. Please tell me how to help further - ATM Rhythmbox is unusable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 13:44:00 2019 InstallationDate: Installed on 2019-01-27 (33 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1818331/+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 1818315] Re: Can't install applications: "E: could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)"
Thank you for your bug report, as indicated by the error message (which
could probably be a bit nicer/user friendly) the packaging system seems
currently locked by another proceess. Did you have any other packaging
tools in use at the time? Did that resolve itself after some time?
** Changed in: gnome-software (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1818315
Title:
Can't install applications: "E: could not get lock /var/lib/dpkg/lock-
frontend - open (11: Resource temporarily unavailable)"
Status in gnome-software package in Ubuntu:
New
Bug description:
1. Start Software Center.
2. Select an application to install
3. Click install
Expected: application installs
Actual: error message "E: could not get lock /var/lib/dpkg/lock-frontend -
open (11: Resource temporarily unavailable)" (see attached screenshot)
Solutions attempted:
1. Closing and re-opening software center
2. Checking 'updates' tab in software center ('Software is up to date')
---
Version information:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.8
Version table:
*** 3.28.1-0ubuntu4.18.04.8 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 1 20:06:51 2019
InstallationDate: Installed on 2019-01-20 (40 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1818315/+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 1818331] [NEW] Rhythmbox segfault since opening flac file
Public bug reported: I hope this is no dupe. Since I opened a flac file per doubleclick on my desktop with Rhythmbox, it crashes everytime right after the start, even when started without parameters. I just started a gdb session and ran rhythmbox, maybe this in fo helps a bit. Please tell me how to help further - ATM Rhythmbox is unusable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 13:44:00 2019 InstallationDate: Installed on 2019-01-27 (33 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "gdb screen output running rhythmbox" https://bugs.launchpad.net/bugs/1818331/+attachment/5242804/+files/gdb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1818331 Title: Rhythmbox segfault since opening flac file Status in rhythmbox package in Ubuntu: New Bug description: I hope this is no dupe. Since I opened a flac file per doubleclick on my desktop with Rhythmbox, it crashes everytime right after the start, even when started without parameters. I just started a gdb session and ran rhythmbox, maybe this in fo helps a bit. Please tell me how to help further - ATM Rhythmbox is unusable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 13:44:00 2019 InstallationDate: Installed on 2019-01-27 (33 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1818331/+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 1423912] Re: Chrome Remote Desktop Plugin Fails To Show Screen On Client
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time. Do you still see a problem related to the one that you reported using currently supported versions of Ubuntu and Chromium? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1423912 Title: Chrome Remote Desktop Plugin Fails To Show Screen On Client Status in chromium-browser package in Ubuntu: Incomplete Bug description: If I'm trying to remotely access my Ubuntu machine from my Android device using the Chrome Remote Desktop app, all the app lives me is a black screen with an "X" as a mouse pointer. No commands filter through to the computer either, so if I do a CTRL ALT DEL, nothing happens. Please fix. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 40.0.2214.111-0ubuntu0.14.10.1. ProcVersionSignature: Ubuntu 3.16.0-30.40-lowlatency 3.16.7-ckt3 Uname: Linux 3.16.0-30-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 20 08:49:13 2015 InstallationDate: Installed on 2014-11-08 (104 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1423912/+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 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
This file is named .0 because I have the printer installed with a custom
ppd file (from kyocera) manually - with the same name, so I think cups
adds the .0 automatically.
** Attachment added: "IPP PPD file"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5242802/+files/Kyocera-ECOSYS-P6026cdn.ppd.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer workflow has bad usability/ is partly broken
Status in gnome-control-center package in Ubuntu:
Incomplete
Bug description:
Hi,
since Ubuntu uses IPP ("driverless") printing, I have a bad time using
printers. I don't know exactly which package this bug belongs to, I think it is
gnome-control-center.
I have a Kyocera EcosysP6026cdn network printer, which provides a PPD
file by the manufacturer. (But I tested this behaviour as well with
other printers from eg. Brother, etc., and on Debian and Arch linux
too). When I switch on the printer, after a few seconds, it is found
in Ubuntu and installed automatically as "Kyocera_ECOSYS_P6026cdn". So
far, so good.
1) I can't remove this printer. If I WANT to install it using another
protocol (dnss etc), it adds another printer, and I have 2 Printers.
So it should be easy to switch off "driverless" printing.
2) Using it as "Default printer" does not work. Clicking the cog
wheel, and using the menu item "Use printer by default" is clickable,
but it does not save any setting: "printers-cc-panel-WARNING **:
20:45:36.812: cups-pk-helper: setting default printer to
Kyocera_ECOSYS_P6026cdn failed: client-error-not-found"
3) "Printing Options" opens an empty dialog, see screenshot attached.
This dialog is useless.
4) The "Printer Detail" dialog shows a "null" address and links to
"(null):631", which is a 404.
I think this "driverless" printing is still in a very "unstable" state. It
helps discovering printers in new Networks where I attach too with my laptop,
and I can print there basically, But most of the day I use my own printer in my
office or at home, and I want to have my special settings for exact this
printer with color profile, duplex settings etc.
And this all is not possible with driverless printing.
So, if you don't "fix" all the not-working options in the UI, please
at least give us an option to easily switch off driverless printing at
all. I really prefer the "old school" way of installing printers.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 29 19:34:39 2019
InstallationDate: Installed on 2019-01-27 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+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 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
Second file. The printer is added automatically twice. Maybe this is
because the printer has a print server, which exports the printer again
and announces it to the network? KM15881D.local is the network name of
the printer.
** Attachment added: "autogenerated 2. ppd file"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5242803/+files/Kyocera_ECOSYS_P6026cdn%40KM15881D.local.ppd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer workflow has bad usability/ is partly broken
Status in gnome-control-center package in Ubuntu:
Incomplete
Bug description:
Hi,
since Ubuntu uses IPP ("driverless") printing, I have a bad time using
printers. I don't know exactly which package this bug belongs to, I think it is
gnome-control-center.
I have a Kyocera EcosysP6026cdn network printer, which provides a PPD
file by the manufacturer. (But I tested this behaviour as well with
other printers from eg. Brother, etc., and on Debian and Arch linux
too). When I switch on the printer, after a few seconds, it is found
in Ubuntu and installed automatically as "Kyocera_ECOSYS_P6026cdn". So
far, so good.
1) I can't remove this printer. If I WANT to install it using another
protocol (dnss etc), it adds another printer, and I have 2 Printers.
So it should be easy to switch off "driverless" printing.
2) Using it as "Default printer" does not work. Clicking the cog
wheel, and using the menu item "Use printer by default" is clickable,
but it does not save any setting: "printers-cc-panel-WARNING **:
20:45:36.812: cups-pk-helper: setting default printer to
Kyocera_ECOSYS_P6026cdn failed: client-error-not-found"
3) "Printing Options" opens an empty dialog, see screenshot attached.
This dialog is useless.
4) The "Printer Detail" dialog shows a "null" address and links to
"(null):631", which is a 404.
I think this "driverless" printing is still in a very "unstable" state. It
helps discovering printers in new Networks where I attach too with my laptop,
and I can print there basically, But most of the day I use my own printer in my
office or at home, and I want to have my special settings for exact this
printer with color profile, duplex settings etc.
And this all is not possible with driverless printing.
So, if you don't "fix" all the not-working options in the UI, please
at least give us an option to easily switch off driverless printing at
all. I really prefer the "old school" way of installing printers.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 29 19:34:39 2019
InstallationDate: Installed on 2019-01-27 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+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 1792668] Re: gnome-calendar fails to sync, update, or cache
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-calendar (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1792668 Title: gnome-calendar fails to sync, update, or cache Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Not sure if this is three different bugs or three symptoms of the same problem, but I am observing three different problematic behaviors on a fresh 18.04.1 install with latest updates: 1. Failure to sync: I have all my online google accounts active, but the calendar does not seem to grab new events from the online database. Nor does it transmit new events to the online database. Nor does it do any of these things when manually selecting the "synchronize" option under the menu. 2. Failure to update: I cannot manually add new events to the calendar. Although the app appears fully interactive, none of my interactions (e.g., adding an event) seem to actually get entered into the calendar, even locally. 3. Failure to cache: I have many local calendars displayed that the calendar app has appeared to pick up from other applications' data. I try to manually remove them by opening the calendars display, clicking on the calendar and clicking "remove." This appears to remove the calendar from this menu, but it doesn't remove it from being displayable. When I close and re-open the application, the local calendars have reappeared. Also, I cannot permanently rename calendars. When I close the app and re-open it, the calendar name has reverted to its original state. This might be related in part to another issue, where I have my UbuntuOne account active, but still get prompted regularly for my username and password from various programs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 15 15:06:10 2018 InstallationDate: Installed on 2018-09-12 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1792668/+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 1187724] Re: thunderbird crashes at startup
Is this still an issue for anyone now that Thunderbird 60.5.1 is the currently supported version? ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1187724 Title: thunderbird crashes at startup Status in thunderbird package in Ubuntu: Incomplete Bug description: This is repeatible. thunderbird --safe-mode also crashes Removing ~.thunderbird/ does not fix the problem. Running thunderbird as another user (different home directory, user never ran thunderbird before) DOES fix the problem and thunderbird starts normally. Clearly there is something about my user environment which is crashing thunderbird - but it is also a bug in thunderbird (it should not crash). I have tried removing gconf settings too - but that made no difference. Next step suggestions would be welcome! Cheers Tim ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: thunderbird 17.0.6+build1-0ubuntu0.13.04.1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twatts 1920 F pulseaudio BuildID: 20130510125337 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Channel: Unavailable CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Jun 5 11:24:25 2013 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-26 (39 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 137.73.122.1 dev eth0 proto static 137.73.122.0/24 dev eth0 proto kernel scope link src 137.73.122.214 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NoProfiles: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/31/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0F428D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/31/2009:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0F428D:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1187724/+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 829015] Re: Thunderbird "Login Failed" dialogue loop
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Thunderbird since that time. Do you still see a problem related to the one that you reported using currently supported versions of Ubuntu and Thunderbird? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/829015 Title: Thunderbird "Login Failed" dialogue loop Status in thunderbird package in Ubuntu: Incomplete Bug description: I set up thunderbird to be my mail client on my work computer. It has been working without issue My network administrator made me change my network password, which I have done. 1. I open thunderbird, and it downloads my incoming mail from our company mail, no problem. 2. It displays a dialogue box saying "Login to failed." 3. I click the "Enter New Password" button. Expected behavior = Login text box appears Actual behavior = The "Login Failed" dialogue box just keeps refreshing and appearing on the screen ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: thunderbird 3.1.11+build2+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 Architecture: amd64 Date: Thu Aug 18 12:50:12 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/829015/+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 383123] Re: can't open an attachement if not listed in registered files types
Is this still an issue with any file type (PDF or otherwise) now that Thunderbird 60.5.1 is the currently supported version? ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/383123 Title: can't open an attachement if not listed in registered files types Status in thunderbird package in Ubuntu: Incomplete Bug description: Binary package hint: thunderbird Hello, I received an email with a PDF attachment but I have no way to open it except saving it and open it later with my file explorer. Before attempting to open the attachement, I had the below file types association: - file extension: PDF - action: open with kpdf - mime type: application/pdf The attachement had "text/octet-stream" MIME type. I get the attached error message. Why not proposing a menu entry with an action like "open with..." in order to avoid to use the file explorer as a workaround. ProblemType: Bug Architecture: amd64 Date: Wed Jun 3 12:42:04 2009 Dependencies: DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list] PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-24-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/383123/+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 372389] Re: copy filter broken resulting in empty email from 01.01.1970
I couldn't reproduce using Thunderbird 60.5.1 in Ubuntu 18.04. Is this still an issue for anyone? If so, please report to https://bugzilla.mozilla.org/ and let us know the URL of the bug report. ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/372389 Title: copy filter broken resulting in empty email from 01.01.1970 Status in thunderbird package in Ubuntu: Incomplete Bug description: Binary package hint: thunderbird To reproduce the problem 2 filters are needed, example: 1: if 'to or cc' contains 'my_add...@test.net' copy to 'directory_1' 2: if 'subject' contains 'test_123' move to 'directory_test' with such filter when the email is received which match both filters the email correctly appears in 'directory_test' but in 'directory_1' where should be copied at the begining instead of original one is only empty email with date 01/01/1970 I saw some similar bugs reported about 2007 but using latest Thunderbird I have the same issue, Cheers, Goral, ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 9.04 Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list] PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.28-11-generic i686 UnreportableReason: This is not a genuine Ubuntu package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/372389/+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 1818327] [NEW] Integrated graphics card is not working
Public bug reported: I am using i7-8700 CPU with Ubuntu 16.04 with kernel version 4.9.38. But, integrated graphics is not working. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 Uname: Linux 4.9.38-xenomai-3.0.5-rt0.1a x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 679078/13180928 files, 17799761/52706560 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 2 17:12:17 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-1021-oem, x86_64: installed bbswitch, 0.8, 4.9.38-xenomai-3.0.5-rt0.1a, x86_64: installed oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1: added DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0871] InstallationDate: Installed on 2018-12-01 (91 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 Lsusb: Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 3630 Tower ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.38-xenomai-3.0.5-rt0.1a root=UUID=be789075-06c0-4bea-a10d-b7d7c4331c85 ro locale=en_IN quiet splash i915.alpha_support=1 video=LVDS-1:d vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0NNNCT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd05/30/2018:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0NNNCT:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: Precision 3630 Tower dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 2 11:27:20 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- 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/1818327 Title: Integrated graphics card is not working Status in xorg package in Ubuntu: New Bug description: I am using i7-8700 CPU with Ubuntu 16.04 with kernel version 4.9.38. But, integrated graphics is not working. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 Uname: Linux 4.9.38-xenomai-3.0.5-rt0.1a x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 679078/13180928 files, 17799761/52706560 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 2 17:12:17 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1
[Desktop-packages] [Bug 1682799] Re: mouse pointer disappears on tabs/navbar when screen scaled
Yes, that's still the case. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1682799 Title: mouse pointer disappears on tabs/navbar when screen scaled Status in chromium-browser package in Ubuntu: New Bug description: Hi, running chromium 57.0.2987.98-0ubuntu1.1348 on zesty on a 2016 XPS 13. When using xrandr --scale to make my HiDPI screen usable with my lower DPI screen, moving the mouse over the navbar makes the mouse pointer disappear. I've took a video to demonstrate this: https://www.youtube.com/watch?v=x_YmsFbtcOA Steps to reproduce: 0. Connect additional, external display 1. run: xrandr --output DP-1 --right-of eDP-1 --output eDP-1 --auto --scale 0.75x0.75 2. hover mouse over navbar I don't know if this is an issue in chromium or xorg. I filled https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123 last year for another issue with scaling. Looks like xorg is pretty much dead. Also happy for any workarounds, chromium is not really usable like this. Fwiw, I'm running xorg 1:7.7+16ubuntu3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1682799/+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 868749] Re: chromium doesn't recognize that it's the default browser
Not reproducible here using Ubuntu 18.04 and Chromium 71. Presumably fixed long ago? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/868749 Title: chromium doesn't recognize that it's the default browser Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Incomplete Bug description: Ubuntu 11.04 chromium-browser 13.0.782.215~r97094-0ubuntu0.11.04.1 from natty-proposed set chromium to your default browser using 'preferred applications' chromium still reports not being the default browser when started. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/868749/+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 1186636] Re: about:permissions doesn't remember changes
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.
Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.
Thank you for helping make Ubuntu better.
Paul White
[Ubuntu Bug Squad]
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
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/1186636
Title:
about:permissions doesn't remember changes
Status in firefox package in Ubuntu:
Incomplete
Bug description:
I went to about:config and changed plugins.click_to_play to true, as
instructed at e.g. https://support.mozilla.org/en-US/questions/956759
Now I'd like youtube to play without clicking. I go to
about:permissions, find youtube.com and www.youtube.com, and set
Plugins to "Allow". Now go to youtube, and ask it to show me
something. It sits there, waiting for me to click on the player
window as instructed by plugins.click_to_play. Huh? Go back to
about:permissions, and find out that Plugins under www.youtube.com has
been reset to Always Ask.
Expected behaviour: about:permissions should save my changes, and
www.youtube.com (e.g.) should stop asking for permission to play
videos.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: firefox 21.0+build2-0ubuntu0.13.04.2
ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bwp4240 F pulseaudio
/dev/snd/controlC0: bwp4240 F pulseaudio
BuildID: 20130512193848
Channel: Unavailable
Date: Sat Jun 1 14:57:15 2013
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-05-18 (14 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
default via 10.1.1.1 dev wlan0 proto static
10.1.1.0/24 dev wlan0 proto kernel scope link src 10.1.1.10 metric 9
169.254.0.0/16 dev wlan0 scope link metric 1000
MarkForUpload: True
PrefSources:
prefs.js
[Profile]/extensions/{f69e22c7-bc50-414a-9269-0f5c344cd94c}/defaults/preferences/defaults.js
Profiles: Profile0 (Default) - LastVersion=21.0/20130512193848 (In use)
RelatedPackageVersions:
google-talkplugin 3.19.1.0-1
icedtea-7-plugin 1.3.2-1ubuntu1
totem-mozilla 3.6.3-0ubuntu6
rhythmbox-mozilla 2.98-0ubuntu5
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC7WW (2.27 )
dmi.board.name: 6465CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6465CTO
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1186636/+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 1796548] Re: [regression] New windows are all centred
I really liked the previous behavior. I think that this was changed by did rocks and suugested by me. What makes it "annoying"? I find th upstream behavior annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1796548 Title: [regression] New windows are all centred Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: In a fresh cosmic installation new windows all appear in the same place; the middle of the screen. This makes opening multiple windows annoying. WORKAROUND: Gnome Tweaks > Windows > Center New Windows = OFF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1796548/+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 231502] Re: Passphrase dialog doesn't accept input
** Changed in: seahorse (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/231502 Title: Passphrase dialog doesn't accept input Status in seahorse package in Ubuntu: Incomplete Bug description: Binary package hint: seahorse Since upgrading to Hardy Heron, I ran into problems with the Passphrase dialog when using Enigmail with Thunderbird. It'll plug along fine, not grabbing focus, but accepting input. But then, at some point, I'll hit "send" on a message, the passphrase dialog will come up, and it won't accept input. Even if I click to give it focus, it still won't accept input. Characters don't show in the text box, and typing return won't confirm/close the dialog. Strangely, hitting Escape _will_ close the dialog. Once this starts happening, it seems to keep happening. Logging out/in, even restarting (IIRC) don't fix the problem. It took me a while to figure out that Enigmail was delegating the passphrase stuff to a gpg-agent, and wrapping thunderbird with a script that unsets GPG_AGENT_INFO did the trick (so that it doesn't call out to seahorse). Once I experienced the problem and tracked it to seahorse, I also tried gpg directly from the commandline with --use-agent, and see the same symptoms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/231502/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: hikaricp (Ubuntu) Importance: Undecided Status: New ** Also affects: ecj (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-l10n in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in activemq package in Ubuntu: New Status in afterburner.fx package in Ubuntu: New Status in annotation-indexer package in Ubuntu: New Status in apache-directory-server package in Ubuntu: New Status in aspectj package in Ubuntu: New Status in aspectj-maven-plugin package in Ubuntu: New Status in batik package in Ubuntu: New Status in bindex package in Ubuntu: New Status in bridge-method-injector package in Ubuntu: New Status in ca-certificates-java package in Ubuntu: New Status in carrotsearch-hppc package in Ubuntu: New Status in commons-httpclient package in Ubuntu: New Status in ecj package in Ubuntu: New Status in eclipselink package in Ubuntu: New Status in elki package in Ubuntu: New Status in figtree package in Ubuntu: New Status in fontawesomefx package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gkl package in Ubuntu: New Status in gluegen2 package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in hikaricp package in Ubuntu: New Status in hsqldb package in Ubuntu: New Status in hsqldb1.8.0 package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jackson-core package in Ubuntu: New Status in jackson-databind package in Ubuntu: New Status in jackson-dataformat-xml package in Ubuntu: New Status in jackson-module-jaxb-annotations package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javafxsvg package in Ubuntu: New Status in javamail package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jboss-classfilewriter package in Ubuntu: New Status in jboss-jdeparser2 package in Ubuntu: New Status in jboss-modules package in Ubuntu: New Status in jcommander package in Ubuntu: New Status in jersey1 package in Ubuntu: New Status in jftp package in Ubuntu: New Status in jmdns package in Ubuntu: New Status in jnr-posix package in Ubuntu: New Status in jruby package in Ubuntu: New Status in jruby-openssl package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libapache-poi-java package in Ubuntu: New Status in libbtm-java package in Ubuntu: New Status in libcommons-collections3-java package in Ubuntu: New Status in libcommons-collections4-java package in Ubuntu: New Status in libcommons-compress-java package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in libjackson-json-java package in Ubuntu: New Status in libjavaewah-java package in Ubuntu: New Status in libjdo-api-java package in Ubuntu: New Status in libjdom1-java package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libnetx-java package in Ubuntu: New Status in libpdfbox2-java package in Ubuntu: New Status in libpicocontainer-java package in Ubuntu: New Status in libquartz-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in libsambox-java package in Ubuntu: New Status in libscram-java package in Ubuntu: New Status in libsejda-java package in Ubuntu: New Status in libspring-java package in Ubuntu: New Status in libswingx-java package in Ubuntu: New Status in libxml-security-java package in Ubuntu: New Status in libxstream-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in mariadb-connector-java package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in mavibot package in Ubuntu: New Status in mckoisqldb package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mockito package in Ubuntu: New Status in msv package in Ubuntu: New Status in obantoo package in Ubuntu: New Status in objenesis package in Ubuntu: New Status in octave package
[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
Hi everyone, I'm not exactly sure how but this is now fixed, I did an update and it works. Thanks to everyone who worked on this fix. My question is, can updates that break accessibility be stopped until they are accessible for all? This issue should not have happened and I wonder how we can stop it from happening again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) [Test Case] 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. [Regression Potential] Low. The affected code is only used in rendering shell panels and popup menus at the moment. So any potential regression (like the original bug) would be noticed in those places only, and not beyond. Furthermore, the upstream fix has been tested regularly for 8 months already. [Other Info] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+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 1782096] Re: (generic?) problem with clickable menues. Here: Firefox
is this still an issue now that Firefox 65.0.1 is the currently supported release? I'm not seeing this problem running Kubuntu 19.04 (dev) in a VM. ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1782096 Title: (generic?) problem with clickable menues. Here: Firefox Status in firefox package in Ubuntu: Incomplete Bug description: After the most recent updates, in the previous around 2 weeks, subsequently mouse interaction of menues fail. In this case, Firefox does not longer allow access of its menu with mouse clicks. Firefox is not the only application with this problem, and I am not the only person experiencing this trouble, see 1781163. Even in firefox this behavoiur is highly selective: the general menu is inaccessible, while the bookmark menu opens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 61.0.1+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: udippel3133 F pulseaudio /dev/snd/controlC0: udippel3133 F pulseaudio BuildID: 20180704194937 Channel: Unavailable CurrentDesktop: KDE Date: Tue Jul 17 10:39:37 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-04-01 (1202 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IpRoute: default via 134.91.100.126 dev eth0 proto static metric 100 134.91.100.0/25 dev eth0 proto kernel scope link src 134.91.100.61 metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=61.0.1/20180704194937 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-12-07 (586 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1782096/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: libpicocontainer-java (Ubuntu) Importance: Undecided Status: New ** Also affects: openhft-lang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-l10n in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in activemq package in Ubuntu: New Status in afterburner.fx package in Ubuntu: New Status in annotation-indexer package in Ubuntu: New Status in apache-directory-server package in Ubuntu: New Status in aspectj package in Ubuntu: New Status in aspectj-maven-plugin package in Ubuntu: New Status in batik package in Ubuntu: New Status in bindex package in Ubuntu: New Status in bridge-method-injector package in Ubuntu: New Status in ca-certificates-java package in Ubuntu: New Status in carrotsearch-hppc package in Ubuntu: New Status in commons-httpclient package in Ubuntu: New Status in eclipselink package in Ubuntu: New Status in elki package in Ubuntu: New Status in figtree package in Ubuntu: New Status in fontawesomefx package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gkl package in Ubuntu: New Status in gluegen2 package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in hsqldb package in Ubuntu: New Status in hsqldb1.8.0 package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jackson-core package in Ubuntu: New Status in jackson-databind package in Ubuntu: New Status in jackson-dataformat-xml package in Ubuntu: New Status in jackson-module-jaxb-annotations package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javafxsvg package in Ubuntu: New Status in javamail package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jboss-classfilewriter package in Ubuntu: New Status in jboss-jdeparser2 package in Ubuntu: New Status in jboss-modules package in Ubuntu: New Status in jcommander package in Ubuntu: New Status in jersey1 package in Ubuntu: New Status in jftp package in Ubuntu: New Status in jmdns package in Ubuntu: New Status in jnr-posix package in Ubuntu: New Status in jruby package in Ubuntu: New Status in jruby-openssl package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libapache-poi-java package in Ubuntu: New Status in libbtm-java package in Ubuntu: New Status in libcommons-collections3-java package in Ubuntu: New Status in libcommons-collections4-java package in Ubuntu: New Status in libcommons-compress-java package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in libjackson-json-java package in Ubuntu: New Status in libjavaewah-java package in Ubuntu: New Status in libjdo-api-java package in Ubuntu: New Status in libjdom1-java package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libnetx-java package in Ubuntu: New Status in libpdfbox2-java package in Ubuntu: New Status in libpicocontainer-java package in Ubuntu: New Status in libquartz-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in libsambox-java package in Ubuntu: New Status in libscram-java package in Ubuntu: New Status in libsejda-java package in Ubuntu: New Status in libspring-java package in Ubuntu: New Status in libswingx-java package in Ubuntu: New Status in libxml-security-java package in Ubuntu: New Status in libxstream-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in mariadb-connector-java package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in mavibot package in Ubuntu: New Status in mckoisqldb package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mockito package in Ubuntu: New Status in msv package in Ubuntu: New Status in obantoo package in Ubuntu: New Status in objenesis package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-bytes package in
[Desktop-packages] [Bug 1771396] Re: Pasted Twitter links are invisble.
is this still an issue now that Firefox 65.0.1 is the currently
supported release? Is Chromium still affected too? Did/does this affect
links from other websites or just Twitter?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
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/1771396
Title:
Pasted Twitter links are invisble.
Status in firefox package in Ubuntu:
Incomplete
Bug description:
If I:
1. point my browser to twitter.com and select a random tweet.
2. And then from the Drop Down menu, select: "Copy Link to Tweet."
3. And then paste that link into a gmail composition
Then the link will not show up, although it is there.
It's almost as if it is pasted as white text on white background?
With the difference that even when selecting it, it still doesn't show.
The only way to make it show up, is change your gmail composition mode to
'Plain text mode.'
Once you do that, you see that the link is actually there.
I expected, instead, to have the link visible after pasting it into gmail.
Note: same issue happens if I use Chromium browser instead.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 60.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bram 1345 F pulseaudio
/dev/snd/controlC0: bram 1345 F pulseaudio
BuildID: 20180509234620
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue May 15 10:27:22 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-04-29 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
default via 10.0.1.1 dev enp5s1 proto dhcp metric 100
10.0.1.0/24 dev enp5s1 proto kernel scope link src 10.0.1.78 metric 100
169.254.0.0/16 dev enp5s1 scope link metric 1000
IwConfig:
enp5s1no wireless extensions.
enp3s0no wireless extensions.
lono wireless extensions.
MostRecentCrashID: bp-64ea59d4-fe25-4952-b630-d4b561180214
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_CA.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=60.0/20180509234620 (In use)
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2108
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2108:bd06/02/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1771396/+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 598932] Re: multiple disk acess when resizing a window
Bug did not expire due to bug watch No reply to comment #6 or to upstream request Closing as invalid as issue not confirmed ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/598932 Title: multiple disk acess when resizing a window Status in Nautilus: Expired Status in nautilus package in Ubuntu: Invalid Bug description: Binary package hint: nautilus if i drag and drop a nautilus window that takes the whole screen to resizing it, and then resizing it again to take the whole screen, I've got multiple disk acess that I don't have with other window like firefox or openoffice. I can see this bug with and without the compiz effects. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Sun Jun 27 05:00:11 2010 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/598932/+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 593502] Re: incorrect file contents listed for digital camera
Bug did not expire due to bug watch No reply to comment #6 or to upstream request Closing as invalid as issue not confirmed ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/593502 Title: incorrect file contents listed for digital camera Status in Nautilus: Expired Status in nautilus package in Ubuntu: Invalid Bug description: Binary package hint: nautilus I have two devices I connect to my computer via USB, a Canon digital camera and a HTC mobile phone. If I connect the phone first and then the camera, Nautilus shows the contents of the phone as being on the camera. If I connect the camera first and then the phone, correct contents are shown for both. I will attach a screenshot of Nautilus displaying the wrong files. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 CheckboxSubmission: 6cd1043ca94c0e13013154feb8688148 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Sun Jun 13 20:48:32 2010 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/593502/+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
