[Desktop-packages] [Bug 1728791] Re: [SRU] pulseaudio-droid module crashes on start
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => bhushan (bhush94) ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => In Progress -- 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/1728791 Title: [SRU] pulseaudio-droid module crashes on start Status in pulseaudio package in Ubuntu: In Progress Bug description: Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4 [Impact] * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) from using the pulseaudio-modules-droid on android devices. * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates enabled. * Last 3 releases of pulseaudio included multiple patches which modified behavior of pulsecore library but required changes were not made in pulseaudio-module-droid. * This results in crash in pulseaudio-modules-droid #0 init_profile (u=0x59528) at modules/droid/module-droid-card.c:370 #1 module_droid_card_22_LTX_pa__init (m=0x3c3f8) at modules/droid/module-droid-card.c:923 #2 0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 "module-droid-card-22", argument=0x0) at pulsecore/module.c:180 #3 0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, fail=0x3c1f4) at pulsecore/cli-command.c:439 #4 0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at pulsecore/cli-command.c:2134 #5 0xf76f6fc8 in pa_cli_command_execute_line (c=, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155 #6 0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153 #7 0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at pulsecore/ioline.c:269 #8 do_read (l=0x3c208) at pulsecore/ioline.c:337 #9 do_work (l=0x3c208) at pulsecore/ioline.c:386 #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655 #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898 #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, retval=0xfffef1c4) at pulse/mainloop.c:929 #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944 #14 0x000158ca in main (argc=, argv=) at daemon/main.c:1152 [Test Case] * Start pulseaudio * From another session run pacmd * In prompt type load-module module-droid-discover * On ubuntu touch devices, it will crash at startup [Regression Potential] * There is no regression potential for other parts of pulseaudio components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728791/+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 1629837] Re: Chrome + hardware acceleration after resume causes unusable system with Nvidia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1629837 Title: Chrome + hardware acceleration after resume causes unusable system with Nvidia Status in xorg package in Ubuntu: Confirmed Bug description: After resuming from a suspend, the Ubuntu UI lags so much the system is not usable. However, this happens only if chrome is running (or is started if not already running) and hardware acceleration is enabled in chrome. I've tried both GNOME Shell and Unity with the same result. ssh into the host works fine while the UI is unusable, showing excessive CPU usage by Xorg, gnome-shell and chrome processes. I tried disable the NVIDIA drivers to test with nouveau, but then the screen will not turn on after resume. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm zfs zunicode zcommon znvpair zavl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 370.28 Thu Sep 1 19:45:04 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Oct 3 12:10:12 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed nvidia-370, 370.28, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:6a04] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 10ab:9008 USI Co., Ltd Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 002: ID 046d:c047 Logitech, Inc. Laser Mouse M-UAL120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65xRP ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.4.0-38-generic root=ZFS=rpool/ROOT/ubuntu ro boot=zfs bootfs=rpool/ROOT/ubuntu SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65xRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.01:bd07/18/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P65xRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 3 11:34:58 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1714647] Re: Video Drivers
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1714647 Title: Video Drivers Status in xorg package in Ubuntu: Expired Bug description: I am not able to used by video drivers at full ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 2 13:51:22 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:145d] InstallationDate: Installed on 2017-08-29 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK COMPUTER INC. X551CA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551CA.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551CA.207:bd10/23/2013:svnASUSTeKCOMPUTERINC.:pnX551CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Sep 2 13:40:18 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714647/+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
I did not have the 79-udev-epson.rules file, so I created one with the content you posted. My scanner works now. No root needed. Many thanks. -- 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 1729491] [NEW] incorrectly installed programs
Public bug reported: 1. I installed the package gnome-recipes, tried to send an error report program in response to the received message:you cannot report a problem: The report belongs to a package that was not installed. 2. Expected that the program will be identified as installed. 3. sudo apt -f install [sudo] password for Alexander: Reading package lists... Done Building dependency tree Reading state information... Ready 0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 packages are not updated. sudo gnome-sudo recipes: gnome-recipes: command not found sudo apt install gnome-recipes Reading package lists... Done Building dependency tree Reading state information... Ready E: unable to locate package gnome-recipes I installed via software-center gnome-recipes snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks ubuntu-bug gnome-recipes dpkg-query: template gnome-recipes no corresponding package Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ^C^Z [1]+ Stopped ubuntu-bug gnome-recipes https://youtu.be/AXtR5m2uqUg --- 1. произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке программы, в ответ получил сообщение:Не удаётся сообщить о неполадке: Отчёт относится к пакету , который не был установлен. 2. Ожидал что программа будет идентифицироваться как установленная. 3. sudo apt -f install [sudo] пароль для alexandr: Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено. sudo gnome-recipes sudo: gnome-recipes: команда не найдена sudo apt install gnome-recipes Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово E: Не удалось найти пакет gnome-recipes произвёл установку через software-center gnome-recipes snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks ubuntu-bug gnome-recipes dpkg-query: шаблону gnome-recipes не соответствует ни один пакет Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ^C^Z [1]+ Остановлено ubuntu-bug gnome-recipes https://youtu.be/AXtR5m2uqUg ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-center (not installed) Uname: Linux 4.14.0-041400rc7-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 2 08:06:48 2017 InstallationDate: Installed on 2017-10-29 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1729491 Title: incorrectly installed programs Status in software-center package in Ubuntu: New Bug description: 1. I installed the package gnome-recipes, tried to send an error report program in response to the received message:you cannot report a problem: The report belongs to a package that was not installed. 2. Expected that the program will be identified as installed. 3. sudo apt -f install [sudo] password for Alexander: Reading package lists... Done Building dependency tree Reading state information... Ready 0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 packages are not updated. sudo gnome-sudo recipes: gnome-recipes: command not found sudo apt install gnome-recipes Reading package lists... Done Building dependency tree Reading state information... Ready E: unable to locate package gnome-recipes I installed via software-center gnome-recipes snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks ubuntu-bug gnome-recipes dpkg-query: template gnome-recipes no corresponding package Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ^C^Z [1]+ Stopped ubuntu-bug gnome-recipes https://youtu.be/AXtR5m2uqUg --- 1. произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке программы, в ответ получил сообщение:Не удаётся сообщить о неполадке: Отчёт относится к пакету , который не был установлен. 2. Ожидал что программа будет идентифицироваться как установленная. 3. sudo apt -f install [sudo] пароль для alexandr: Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово обновлено 0, установлено 0 новых
[Desktop-packages] [Bug 1727160] Re: alt-tabbing out of a fullscreen game and back in causes the game to not come back fullscreen
*** This bug is a duplicate of bug 1725649 *** https://bugs.launchpad.net/bugs/1725649 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/1727160 Title: alt-tabbing out of a fullscreen game and back in causes the game to not come back fullscreen Status in gnome-shell package in Ubuntu: Confirmed Bug description: Launch any game full screen on steam (Civ5 is a good example) and alt- tab. When you alt-tab back to the game it will not be full screen, but windowed and slightly down and right from where it should be. Some applications have alt-enter to switch from windowed to fullscreen and toggling that will work (0 AD) is a good example. Most do not. Ubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 00:06:36 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:119e] InstallationDate: Installed on 2017-10-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Alienware Aurora-R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: Alienware dmi.bios.version: A11 dmi.board.name: 07JNH0 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00: dmi.product.family: 0 dmi.product.name: Aurora-R4 dmi.product.version: 00 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/gnome-shell/+bug/1727160/+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 1729441] Re: changing display mode after login terminates session
Sounds like you might have multiple bugs. (1) Failure to remember the correct display configuration when logging in is bug 1726538. (2) If your session is getting terminated then something is crashing. Please forgive the standard response... Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. ** 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/1729441 Title: changing display mode after login terminates session Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I login, I type the password on the laptop screen. (Maybe it's important.) After a while, while I'm waiting to get logged in, Ubuntu changes the display mode. Both monitor goes black, laptop screen becomes the secondary and my external monitor becomes the primary display. Because of Ubuntu is unable to remember to the previously set display mode, I usually change it a bit after I have logged in. However, if I (would like to) do this too quickly, say... less than 4-5 seconds after I can see my desktop, my session gets terminated and I'm returned to the login screen. You can repeat it indefinitely, it always worked for me. I thought it's because of one of my extensions but I could reproduce it after I have disabled them. I haven't found any useful log entries. UPDATE 1: While I was writing this, I thought it has something to do with theme loading or something like this, so I continued to test with startup applications. I just rarely managed to reproduce this bug when I didn't execute the following script (as a file) at login: ``` #!/bin/bash sleep 1s; firefox & sleep 1s; thunderbird & ``` I also noticed that after I have some faulty logins and then I login without changing display mode, I >sometimes< have no desktop, no startup applications and when I click power off/logout buttons nothing happens, but that's sure I will being logged out randomly in the near future - even if I don't touch my computer (I'm talking about minutes). Plus, I can see the desktop and the top bar (so it's the primary screen) with two wide black bars on the two sides of my laptop monitor for a moment before I get logged out. (However, I don't see any resolution changes so I guess it's not 640x480, or 800x600, etc.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 1 21:00:45 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-08 (85 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-21 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729441/+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 1729461] Re: Clicking notification raises a slew of unrelated windows
I can't seem to find any previous reports of this issue. Can you log it on https://bugzilla.gnome.org too? -- 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/1729461 Title: Clicking notification raises a slew of unrelated windows Status in gnome-shell package in Ubuntu: New Bug description: Running GNOME Shell. When (for example) I click on a Signal notification, Shell will raise the Signal window, and then raises my password manager window, and two different(!) Telegram windows over the top. This is not the ideal behaviour :). This is not limited to Signal; Geary notifications suffer the same behaviour. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:26:18 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-20 (42 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729461/+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 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language
+1 Ubuntu 16.04.3 and Brazilian Portuguese Traduction. -- 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/1491787 Title: Gnome's Activities Overview search is always in English, regardless of the system language Status in Ubuntu GNOME: New Status in Ubuntu Translations: New Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hey, I'm referring to this issue on AskUbuntu: http://askubuntu.com/questions/600656/change-language-of-the-gnome- shell-overview On my Ubuntu Gnome 15.04 system all entries from the gnome-control- center are shown in English in the Gnome-Shell overview (see screenshot in the above mentioned link), even though my system language is German. The entries in the gnome-control-center itself are however in German. Is this due to a bug or missing translations? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1491787/+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 1729394] Re: Activities Overview on a rotated screen displays with wrong orientation (unrotated)
Doug, I can't seem to find anyone else having reported this problem already. So could you please also report it here (with product 'gnome-shell')?: https://bugzilla.gnome.org When done, let us know here what the new bug ID on bugzilla is. -- 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/1729394 Title: Activities Overview on a rotated screen displays with wrong orientation (unrotated) Status in gnome-shell package in Ubuntu: New Bug description: Having a secondary monitor in landscape mode works flawlessly in 17.10. However, problems arise when I set a monitor to portrait mode. One thing that happens is when I bring my mouse to the edge of the screen, I see the cursor mirrored on the second screen. The main issue is when I hit the windows key and try to search for an application. The results look all scrambled and my secondary monitor is displayed in landscape mode with all of my windows. Look at my bug attachment to see a screenshot of what happens when I press the windows/super key and try to search for a program. On the left is my secondary monitor in portrait mode. When moving Windows to that monitor, it works as it should, but when I hit the Windows/super key to show all of my open windows, it displays in landscape. On the right is my main monitor in landscape mode. In that screen I was searching for my GEdit program. Specs: Integrated Intel graphics card Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729394/+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 1729394] Re: 17.10 - Second monitor in portrait mode causes graphical issue
Yes let's keep the double cursor issue in bug 1724977. This bug should be about the incorrect screen orientation after hitting the Super (Windows) key. ** Summary changed: - 17.10 - Second monitor in portrait mode causes graphical issue + Activities Overview on a rotated screen displays with wrong orientation (unrotated) ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1729394 Title: Activities Overview on a rotated screen displays with wrong orientation (unrotated) Status in gnome-shell package in Ubuntu: New Bug description: Having a secondary monitor in landscape mode works flawlessly in 17.10. However, problems arise when I set a monitor to portrait mode. One thing that happens is when I bring my mouse to the edge of the screen, I see the cursor mirrored on the second screen. The main issue is when I hit the windows key and try to search for an application. The results look all scrambled and my secondary monitor is displayed in landscape mode with all of my windows. Look at my bug attachment to see a screenshot of what happens when I press the windows/super key and try to search for a program. On the left is my secondary monitor in portrait mode. When moving Windows to that monitor, it works as it should, but when I hit the Windows/super key to show all of my open windows, it displays in landscape. On the right is my main monitor in landscape mode. In that screen I was searching for my GEdit program. Specs: Integrated Intel graphics card Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729394/+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 1718654] Re: Touchpad input doesn't work after longer suspend.
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/1718654 Title: Touchpad input doesn't work after longer suspend. Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I resume my laptop from a longer (not sure what the threshold is yet) suspend, I don't get input from the touchpad, a short suspend cycle fixes it. Touchscreen works all the time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 14:20:56 2017 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718654/+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 1729391] Re: Trackpad stops responding after suspend
*** This bug is a duplicate of bug 1718654 *** https://bugs.launchpad.net/bugs/1718654 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1718654, so it 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. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-bluetooth (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1718654 Touchpad input doesn't work after longer suspend. -- 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/1729391 Title: Trackpad stops responding after suspend Status in gnome-shell package in Ubuntu: New Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, the trackpad stops working after suspend (it actually works for a few seconds, then doesn't react). I can still use the touch screen. Please tell me which log-files to upload. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729391/+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 1729372] Re: traduction fr not valid for settings in dash gnome-shell
*** This bug is a duplicate of bug 1491787 *** https://bugs.launchpad.net/bugs/1491787 ** This bug has been marked a duplicate of bug 1491787 Gnome's Activities Overview search is always in English, regardless of the system language -- 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/1729372 Title: traduction fr not valid for settings in dash gnome-shell Status in gnome-shell package in Ubuntu: Invalid Bug description: Hi, I have a fresh install of Ubuntu 17.10 in french. When i put something in search dash I have result in french but not for settings search : http://image.noelshack.com/fichiers/2017/44/3/1509546937-bug-ko.png When I clic at more setting search result, traduction are fine in french : http://image.noelshack.com/fichiers/2017/44/3/1509546937-bug-ok.png other search result category are in french : http://image.noelshack.com/fichiers/2017/44/3/1509548466-capture-d -ecran-de-2017-11-01-16-00-29.png So it's just a traduction bug for result search for settings in dash. More infos : 'lsb_release -rd : Description: Ubuntu 17.10 Release: 17.10 apt-cache policy gnome-shell : gnome-shell: Installé : 3.26.1-0ubuntu5 Candidat : 3.26.1-0ubuntu5 Table de version : *** 3.26.1-0ubuntu5 500 500 http://fr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages Sincerely, P.S : sorry for my bad english ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 15:52:05 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-30 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729372/+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 1728977] Re: back to the choice of apps in alt+tab+shift
Seems to work for me: Alt+Shift+Tab to switch to the previous app. Alt+Shift+` to switch to the previous window. Gnome Shell is different to Unity in that you need to use ` instead of Tab to switch windows of an app. But in both cases using Shift to switch to the previous one seems to work fine... What keyboard layout are you using? And what key do you have above the Tab key? -- 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/1728977 Title: back to the choice of apps in alt+tab+shift Status in gnome-shell package in Ubuntu: Incomplete Bug description: back to the choice of apps in alt+tab+shift ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.14.0-041400rc7-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 18:21:20 2017 DisplayManager: gdm3 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-30 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728977/+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 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
Please run 'apport-collect 1729389' on the affected machine to help us gather more information. ** Package changed: gnome-bluetooth (Ubuntu) => bluez (Ubuntu) ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1728585] Re: no screen, no keyboard, no mouse, high cpu usage
Thank you for taking the time to report this bug and helping to make Ubuntu better. A freeze or black screen often means something has crashed. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. ** 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/1728585 Title: no screen, no keyboard, no mouse, high cpu usage Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have just switched to the last (dynamic) workspace and a half minute later computer froze. It didn't reacted to any keyboard and mouse events, laptop lid closing (I hoped I can suspend) or HDMI cable un/plug (it sometimes used to solve some freezes). That's all I know. (I have reported the bug in gnome-shell.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 30 13:28:43 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-08 (83 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728585/+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 1724105] Re: Privacy : Deactivating screen lock doesn't work
I confirm that I cannot duplicate the issue on Fedora 27 or on Debian Buster. ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gdm3 (Ubuntu) Status: New => Triaged ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low -- 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/1724105 Title: Privacy : Deactivating screen lock doesn't work Status in gdm3 package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: What steps do I need to follow to reproduce this bug : Install gnome- session. In that session, open System Settings/Privacy Uncheck Lock Screen. What did I expect to happen : When opening the lid of my laptop, I was expecting to see no login screen and be back right away in my session, without having to enter my password. What actually happens: After opening the lid, the screen flashes, then goes black. After hitting the space bar, I get the "clock screen", swipe up, then get login screen. Sometimes, the screen just freeze. Have to hard reboot. Side effect : Lock Screen activated, only way that the laptop will come back from sleep normally. Dell XPS 13 (9360) --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016) Package: gnome-shell 3.26.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724105/+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 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
I fully agree this bug is valid and needs to be fixed. I only disagree with Sebastian's selection of High importance in the bigger picture. "cannot open display" either means it's an X app and XOpenDisplay failed (Xwayland isn't running because mutter failed to start). Or it means it's a native Wayland client and it can't start because mutter failed to start. Either way, "cannot open display" is an expected error that's a side-effect of this bug (mutter failed to start). But it's not the cause of this bug and not relevant. I have some older hardware laying around that might experience this or similar issues. So I'll try to get to testing it out before we're too far into the new year. -- 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/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-05-04 (539 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed third-party-packages Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+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 1729181] Re: directory and file icons are same in "Files" app
Hi, How do I find this information? I know how to check themes in 16.04 but in 17.10 I am not able to locate that setting so not able to tell you exactly. If it helps, I am using outbox theme that comes with default installation of Ubuntu 17.10 and with wayland display server not xOrg. Thanks Kunal Shah -- 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/1729181 Title: directory and file icons are same in "Files" app Status in nautilus package in Ubuntu: New Bug description: while browsing File Manager with nautilus, it does not show different icons for files and directory. Please see attached screenshot. using Ubuntu Desktop 17.10 with wayland GNOME nautilus 3.26.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729181/+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 1566357] Re: Unable to type passwords with non-English/non-Latin input source
Nikita: Is bug 1725676 the same issue or different from your perspective? ** Changed in: ubuntu-gnome Status: Confirmed => Incomplete ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/1566357 Title: Unable to type passwords with non-English/non-Latin input source Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I recently found that I am unable to type using the "Japanese (Anthy)" input source in password fields in gnome-shell. That is I am unable to type using it (I just get English) on the login screen in the password field (though I haven't tried the username field), I am unable to type using it in the graphical prompts for authentication, and I am unable to type using it when setting a new password through the gnome- control-center. I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well as with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1566357/+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 1193525] Re: rhythmbox crashed with SIGSEGV in sem_post()
I don't use either rhythmbox or Ubuntu anymore, so I can't say. On 1 Nov 2017 11:55 p.m., "rithik g" <1193...@bugs.launchpad.net> wrote: > Is this still a problem ? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1199159). > https://bugs.launchpad.net/bugs/1193525 > > Title: > rhythmbox crashed with SIGSEGV in sem_post() > > Status in Rhythmbox: > Expired > Status in rhythmbox package in Ubuntu: > Confirmed > > Bug description: > Possible Workaround: > > Try disabling all the python based plugins: > * Context Pane > * Cover art search > * IM status > * Magnatune store > * Python console > * Send tracks > * Song lyrics > * Ubuntu One > * Zeitgeist > > Crashed while clicking 'next' > > ProblemType: Crash > DistroRelease: Ubuntu 13.10 > Package: rhythmbox 2.99.1-0ubuntu1 > ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 > Uname: Linux 3.9.0-6-generic x86_64 > ApportVersion: 2.10.2-0ubuntu2 > Architecture: amd64 > CrashCounter: 1 > Date: Sat Jun 22 11:12:40 2013 > ExecutablePath: /usr/bin/rhythmbox > InstallationDate: Installed on 2012-09-09 (285 days ago) > InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 > (20120905.2) > MarkForUpload: True > ProcCmdline: rhythmbox > ProcEnviron: >XDG_RUNTIME_DIR= >SHELL=/bin/bash >LANGUAGE=en_AU:en >PATH=(custom, no user) >LANG=en_AU.UTF-8 > SegvAnalysis: >Segfault happened at: 0x7f76731561e0 : mov(%rdi),%eax >PC (0x7f76731561e0) ok >source "(%rdi)" (0x) not located in a known VMA region (needed > readable region)! >destination "%eax" ok >Stack memory exhausted (SP below stack segment) > SegvReason: reading NULL VMA > Signal: 11 > SourcePackage: rhythmbox > StacktraceTop: >sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0 >PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/ > libpython2.7.so.1.0 >g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 >g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > Title: rhythmbox crashed with SIGSEGV in sem_post() > UpgradeStatus: Upgraded to saucy on 2013-05-25 (27 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > > To manage notifications about this bug go to: > https://bugs.launchpad.net/rhythmbox/+bug/1193525/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1193525 Title: rhythmbox crashed with SIGSEGV in sem_post() Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Confirmed Bug description: Possible Workaround: Try disabling all the python based plugins: * Context Pane * Cover art search * IM status * Magnatune store * Python console * Send tracks * Song lyrics * Ubuntu One * Zeitgeist Crashed while clicking 'next' ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Sat Jun 22 11:12:40 2013 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2012-09-09 (285 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MarkForUpload: True ProcCmdline: rhythmbox ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76731561e0 : mov(%rdi),%eax PC (0x7f76731561e0) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0 PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in sem_post() UpgradeStatus: Upgraded to saucy on 2013-05-25 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1193525/+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 1724977] Re: two mouse cursors visible at the same time on rotated screen
I doubt this bug is driver-specific. A rotated screen might get "software" (GL) cursor rendering by default in Wayland sessions (I am guessing since we did the same in Mir). And the hardware cursor is used on non-rotated screens. The two should co-exist and only one display at a time, so that's no excuse, just a possible explanation. One reason why the problem might appear to go away with the proprietary Nvidia driver is because that uses Xorg by default. So it avoids all such issues that are peculiar to the Wayland/eglnative case. -- 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/1724977 Title: two mouse cursors visible at the same time on rotated screen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: When my 2nd Asus (Ancor) display is in portrait mode and is set to be to the left of my centered landscape display in extended mode, moving the mouse to roughly the left 20% of my landscape display will show a mouse cursor on my landcape display AND portrait display at the same time. Oddly moving a window into this area only shows on the landscape display. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 13:43:30 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 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/gnome-shell/+bug/1724977/+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 1566357] Re: Unable to type passwords with non-English/non-Latin input source
I'm trying to keep everyone on the same (web)page. See the duplicate bugs attached to this. If they really are a different issue then we can detach them, but I think/hope it's all related. I'm sure Nikita can confirm... -- 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/1566357 Title: Unable to type passwords with non-English/non-Latin input source Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I recently found that I am unable to type using the "Japanese (Anthy)" input source in password fields in gnome-shell. That is I am unable to type using it (I just get English) on the login screen in the password field (though I haven't tried the username field), I am unable to type using it in the graphical prompts for authentication, and I am unable to type using it when setting a new password through the gnome- control-center. I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well as with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1566357/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Note that if the workarounds at the top of this bug don't work for you then you're subscribed to the wrong bug. In that case, please open a new one. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Sorry you can't get it working, that's all I can think of. My advice would be to just go back to 17.04 and install Gnome there if you want the Gnome experience. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu
For the last few YEARS, I fix this by adding "--password-store=basic" to the command line. It's "insecure credential storage", but it greatly speeds up Chrome password login and no high CPU utilization. Simply edit /usr/share/applications/google-chrome.desktop, and add --password-store=basic to the 3 Exec= lines in that file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Bug description: After upgrading to 13.04, when starting the chromium browser, the gnome-keyring-daemon runs at full CPU load and the chromium-browser has no access to the stored passwords. The issue seems to be known (https://code.google.com/p/chromium/issues/detail?id=98601). I'm personally a bit surprised that Ubuntu 13.04 was released with such a serious problem. The frequently proposed workaround (e.g. https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4) doesn't work because (a) there is no .gnome2/keyrings any more and (b) it's rather inresponsible to store your passwords unencryted. I found that killing gnome-keyring-server several times eventually gives you a working system. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mnl 18759 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140 InstallationDate: Installed on 2010-11-10 (900 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD) MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice wireshark WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP] dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDD Ver. F.20 dmi.board.name: 30DD dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.23 dmi.chassis.asset.tag: CNU9326SJY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6730b (GB990EA#ABD) dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 1718552] Re: gnome-shell uses lots of memory
Please disable that extension and restart your computer and see if your memory usage is better. -- 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/1718552 Title: gnome-shell uses lots of memory Status in gnome-shell package in Ubuntu: Confirmed Bug description: On Ubuntu 17.10 (daily build, VirtualBox), gnome-shell uses lots of memory, even more after opening and closing just a few apps (LibreOffice Writer, Chromium, Nautilus.) More than 640 mb. Also,the CPU usage is quite high too, even if nothing is running in the foreground. See screen captures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718552/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu
I experience this with Chrome 63 beta and Ubuntu 16.04 all up to date as of today. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Bug description: After upgrading to 13.04, when starting the chromium browser, the gnome-keyring-daemon runs at full CPU load and the chromium-browser has no access to the stored passwords. The issue seems to be known (https://code.google.com/p/chromium/issues/detail?id=98601). I'm personally a bit surprised that Ubuntu 13.04 was released with such a serious problem. The frequently proposed workaround (e.g. https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4) doesn't work because (a) there is no .gnome2/keyrings any more and (b) it's rather inresponsible to store your passwords unencryted. I found that killing gnome-keyring-server several times eventually gives you a working system. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mnl 18759 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140 InstallationDate: Installed on 2010-11-10 (900 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD) MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice wireshark WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP] dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDD Ver. F.20 dmi.board.name: 30DD dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.23 dmi.chassis.asset.tag: CNU9326SJY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6730b (GB990EA#ABD) dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 785681] Re: Unable to unblank screen, cursor still present
Sergio Callegari, while the original reporter wasn't using either Kubuntu, or a nvidia graphics card, given how old this report is, it is likely you are experiencing a completely different problem with a different root cause. Hence, it will help immensely if you use the computer the problem is reproducible with, file a new report with Ubuntu by first ensuring the package xdiagnose is installed, click the Yes button for attaching additional debugging information after running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. -- 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/785681 Title: Unable to unblank screen, cursor still present Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Status in Baltix: New Bug description: Binary package hint: xserver-xorg-video-intel This is ~ev filing this bug on behalf of Ellen. When her laptop blanked the screen, she tried to unlock it; however, it did not return from this state and only the mouse cursor was ever visible. Switching to a VT showed that all the desktop processes were still running. Killing gnome-screensaver did not fix the issue, nor did running unity --reset. This issue occurs sporadically. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DRM.card0.DP.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.DP.2: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.HDMI.A.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1366x768 edid-base64: AP///wBMo0FUAAATAQOQIhN4CsiVnldUkiYPUFQBAQEBAQEBAQEBAQEBAQEBQRxWoFAAFjAwICUAWMIQAAAaQRxWoFAAFjAwICUAWMIQAAAa/gBTQU1TVU5HCiAgICAg/gBMVE4xNTZBVDAyUDA2AMQ= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Fri May 20 11:20:14 2011 DistUpgraded: Log time: 2011-05-03 09:09:17.573737 DistroCodename: natty DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1862] Subsystem: ASUSTeK Computer Inc. Device [1043:1862] InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: ASUSTeK Computer Inc. P50IJ ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=59f9e85c-7640-46a4-9844-626f6dd584e9 ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to natty on 2011-05-03 (17 days ago) dmi.bios.date: 12/04/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P50IJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr203:bd12/04/2009:svnASUSTeKComputerInc.:pnP50IJ:pvr1.0:rvnASUSTeKComputerInc.:rnP50IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P50IJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/785681/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
K...so we’re getting closer! After a fresh install yet again, and following very closely the steps outlined in post #66, I am now at the lighten login screen. It will NOT let me login, it’s a constant login loop every time I put in my password. But at least I’m past boot loop. I attempted to fix the login loop by using a hack: Carl+Alt+F1 mv.Xauthority .Xauthority.bak Then back to the GUI. Unfortunately this did not work. So I am currently just sitting at the login screen, unable then loginlol This is a bit comical that we need to jump thru these hoops for drivers to work :-( -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
I’ve attempted login to Ubuntu on Xorg(Default) and also Ubuntu on Xorg, and even Ubuntu(Default). Any and all options just bring me right back to the password boxlogin loop. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
** Changed in: libinput Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in libinput: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Status in libinput package in Ubuntu: Triaged Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+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 1729394] Re: 17.10 - Second monitor in portrait mode causes graphical issue
Yep, that seems to be describing the same issue. They didn't mention the issue window pressing the super key and searching, but I'd imagine they have that issue too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1729394 Title: 17.10 - Second monitor in portrait mode causes graphical issue Status in wayland package in Ubuntu: New Bug description: Having a secondary monitor in landscape mode works flawlessly in 17.10. However, problems arise when I set a monitor to portrait mode. One thing that happens is when I bring my mouse to the edge of the screen, I see the cursor mirrored on the second screen. The main issue is when I hit the windows key and try to search for an application. The results look all scrambled and my secondary monitor is displayed in landscape mode with all of my windows. Look at my bug attachment to see a screenshot of what happens when I press the windows/super key and try to search for a program. On the left is my secondary monitor in portrait mode. When moving Windows to that monitor, it works as it should, but when I hit the Windows/super key to show all of my open windows, it displays in landscape. On the right is my main monitor in landscape mode. In that screen I was searching for my GEdit program. Specs: Integrated Intel graphics card Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1729394/+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 1729469] [NEW] nautilus freezes when dragging files from desktop to open usb folder
Public bug reported: Description:Ubuntu 17.10 Release:17.10 nautilus: Installed: 1:3.26.0-0ubuntu1 Candidate: 1:3.26.0-0ubuntu1 Version table: *** 1:3.26.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Steps to Reproduce: 1. Open USB drive in nautilus 2. Drag file from desktop to USB folder What happens: - Nautilus freezes - Mouse pointer gets stuck as a hand - File doesn't transfer - Unable to access Firefox address bar with mouse; entering url, pressing enter doesn't register - Requires logout or restart to fix Expected: - File moves to USB - Doesn't freeze ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1729469 Title: nautilus freezes when dragging files from desktop to open usb folder Status in nautilus package in Ubuntu: New Bug description: Description: Ubuntu 17.10 Release: 17.10 nautilus: Installed: 1:3.26.0-0ubuntu1 Candidate: 1:3.26.0-0ubuntu1 Version table: *** 1:3.26.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Steps to Reproduce: 1. Open USB drive in nautilus 2. Drag file from desktop to USB folder What happens: - Nautilus freezes - Mouse pointer gets stuck as a hand - File doesn't transfer - Unable to access Firefox address bar with mouse; entering url, pressing enter doesn't register - Requires logout or restart to fix Expected: - File moves to USB - Doesn't freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729469/+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 1581151] Re: Time to drop 69-language-selector-zh-??.conf?
** Changed in: language-selector (Ubuntu) Status: New => Fix Committed ** Changed in: language-selector (Ubuntu) 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/1581151 Title: Time to drop 69-language-selector-zh-??.conf? Status in language-selector package in Ubuntu: Fix Committed Bug description: With the transition to Noto Sans CJK as default font for Chinese, we have established a fontconfig configuration for rendering Chinese under an *English* locale via these three files: /etc/fonts/conf.avail/64-language-selector-prefer.conf /etc/fonts/conf.avail/65-fonts-arphic-ukai.conf /etc/fonts/conf.avail/65-fonts-arphic-uming.conf (I questioned the need for the two latter in bug #1560548, but I think we'd better consider the need for the 69-language-selector-zh-??.conf files first.) So, if I have understood the feedback from Chinese users correctly, both Chinese and Japanese are properly rendered under an English locale in Ubuntu 16.04. It's my belief that what's happening if you switch to a Chinese locale is that one of the 69-language-selector-zh-??.conf files is enabled, and Japanese is no longer properly rendered while there is no improvement in rendering Chinese. If I'm right, I think we should drop 69-language-selector-zh-??.conf. Did I miss anything? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581151/+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 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?
Let's get started with this. I have uploaded some language-selector changes to bionic. They include: * The Japanese config file proposed by Mitsuya Shibata in comment #11. * Adding of Korean entries to /etc/fonts/conf.avail/64-language-selector-prefer.conf To make it easier to test on Ubuntu 17.10, I also uploaded the new language-selector version to the artful pocket of this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/noto-test However, Launchpad seems to be unusually busy for some reason, so it will probably take several hours for both uploads before they are available... Later on, if we decide to switch to Noto, changes need to be done to several seed branches, so the installer does not install Takao/Nanum fonts. At this time, to test the changes, you need to remove Takao/Nanum packages manually: sudo apt purge fonts-takao-* sudo apt purge fonts-nanum* Also, the fonts-noto-cjk package, which is installed by default for all users, only includes the font weights "Regular" and "Bold". To get access to the other weights, you need to do: sudo apt install fonts-noto-cjk-extra I ask our Japanese and Korean users to please test this and provide feedback. ** Changed in: language-selector (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: language-selector (Ubuntu) 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/1581160 Title: Switch to Noto Sans as default font for Japanese and/or Korean? Status in language-selector package in Ubuntu: Fix Committed Bug description: In Ubuntu 16.04 Noto Sans CJK is the default font for rendering Chinese. After having struggled with a few issues, I believe that we finally achieved the desired improvement of the rendering experience. So now I ask: Is there an interest from Japanese and Korean users to consider a switch to Noto Sans? (The fonts are already installed for all users on Ubuntu 16.04.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+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 460039] ✔something really amazing
Hey, I've just found some stuff that is absolutely amazing, please take a peek and inform me your thoughts http://www.teenauthorbootcamp.com/sanction.php?UE80NjAwMzlAYnVncy5sYXVuY2hwYWQubmV0 Good wishes, Julio Lind -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-butterfly in Ubuntu. https://bugs.launchpad.net/bugs/460039 Title: telepathy-butterfly crashed with TypeError in __common_callback() Status in telepathy-butterfly: Fix Released Status in telepathy-butterfly package in Ubuntu: Fix Released Bug description: Binary package hint: telepathy-butterfly I was going to the list of Empathy notifications (Mail Icon in Top panel) and I refused all contact requests as I did not know those contacts. One entry appeared 2 times: "Ajinkya X0m". When clicking in the lower entry the telepathy-butterfly crashed and apport came up. ProblemType: Crash Architecture: i386 Date: Sat Oct 24 23:09:15 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/lib/telepathy/telepathy-butterfly InterpreterPath: /usr/bin/python2.6 Package: telepathy-butterfly 0.5.2-0ubuntu1 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly'] SourcePackage: telepathy-butterfly Title: telepathy-butterfly crashed with TypeError in __common_callback() Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-butterfly/+bug/460039/+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 468288] ✈cool places to visit
*** This bug is a duplicate of bug 460039 *** https://bugs.launchpad.net/bugs/460039 Hi friend! Here is a nice selection of great places to go to, just look into my list http://www.tahirilhan.com/show.php?UE80NjgyODhAYnVncy5sYXVuY2hwYWQubmV0 Take care, Etta Novak -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-butterfly in Ubuntu. https://bugs.launchpad.net/bugs/468288 Title: telepathy-butterfly crashed with TypeError in __common_callback() Status in telepathy-butterfly package in Ubuntu: New Bug description: Binary package hint: telepathy-butterfly I don't know what to write here... ProblemType: Crash Architecture: amd64 Date: Sun Nov 1 11:56:09 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/lib/telepathy/telepathy-butterfly InterpreterPath: /usr/bin/python2.6 Package: telepathy-butterfly 0.5.2-0ubuntu1 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly ProcEnviron: SHELL=/bin/bash LANG=sv_SE.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly'] SourcePackage: telepathy-butterfly Title: telepathy-butterfly crashed with TypeError in __common_callback() Uname: Linux 2.6.31-14-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (gnome-settings-daemon:1813): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:1813): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:1941): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1914): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-butterfly/+bug/468288/+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 1724105] Re: Privacy : Deactivating screen lock doesn't work
I don't think it's an upstream bug at all, as I didn't have that problem on Fedora 27 and Manjaro, both on Gnome 3.26. And I had the same problem with Ubuntu Gnome 17.04 Please don't put the blame on upstream before investigating. -- 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/1724105 Title: Privacy : Deactivating screen lock doesn't work Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: What steps do I need to follow to reproduce this bug : Install gnome- session. In that session, open System Settings/Privacy Uncheck Lock Screen. What did I expect to happen : When opening the lid of my laptop, I was expecting to see no login screen and be back right away in my session, without having to enter my password. What actually happens: After opening the lid, the screen flashes, then goes black. After hitting the space bar, I get the "clock screen", swipe up, then get login screen. Sometimes, the screen just freeze. Have to hard reboot. Side effect : Lock Screen activated, only way that the laptop will come back from sleep normally. Dell XPS 13 (9360) --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016) Package: gnome-shell 3.26.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724105/+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 1729461] [NEW] Clicking notification raises a slew of unrelated windows
Public bug reported: Running GNOME Shell. When (for example) I click on a Signal notification, Shell will raise the Signal window, and then raises my password manager window, and two different(!) Telegram windows over the top. This is not the ideal behaviour :). This is not limited to Signal; Geary notifications suffer the same behaviour. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:26:18 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-20 (42 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session -- 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/1729461 Title: Clicking notification raises a slew of unrelated windows Status in gnome-shell package in Ubuntu: New Bug description: Running GNOME Shell. When (for example) I click on a Signal notification, Shell will raise the Signal window, and then raises my password manager window, and two different(!) Telegram windows over the top. This is not the ideal behaviour :). This is not limited to Signal; Geary notifications suffer the same behaviour. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:26:18 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-20 (42 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729461/+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 1729441] Re: changing display mode after login terminates session
** Description changed: When I login, I type the password on the laptop screen. (Maybe it's important.) After a while, while I'm waiting to get logged in, Ubuntu changes the display mode. Both monitor goes black, laptop screen becomes the secondary and my external monitor becomes the primary display. Because of Ubuntu is unable to remember to the previously set display mode, I usually change it a bit after I have logged in. However, if I (would like to) do this too quickly, say... less than 4-5 seconds after I can see my desktop, my session gets terminated and I'm returned to the - login screen. You can repeat it indefinitely, it always worked (?) for - me. + login screen. You can repeat it indefinitely, it always worked for me. I thought it's because of one of my extensions but I could reproduce it after I have disabled them. I haven't found any useful log entries. + + + UPDATE 1: + While I was writing this, I thought it has something to do with theme loading or something like this, so I continued to test with startup applications. + I just rarely managed to reproduce this bug when I didn't execute the following script (as a file) at login: + ``` + #!/bin/bash + sleep 1s; firefox & + sleep 1s; thunderbird & + ``` + + I also noticed that after I have some faulty logins and then I login + without changing display mode, I >sometimes< have no desktop, no startup + applications and when I click power off/logout buttons nothing happens, + but that's sure I will being logged out randomly in the near future - + even if I don't touch my computer (I'm talking about minutes). + + Plus, I can see the desktop and the top bar (so it's the primary screen) + with two wide black bars on the two sides of my laptop monitor for a + moment before I get logged out. (However, I don't see any resolution + changes so I guess it's not 640x480, or 800x600, etc.) + ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 1 21:00:45 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-08 (85 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-21 (10 days ago) -- 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/1729441 Title: changing display mode after login terminates session Status in gnome-shell package in Ubuntu: New Bug description: When I login, I type the password on the laptop screen. (Maybe it's important.) After a while, while I'm waiting to get logged in, Ubuntu changes the display mode. Both monitor goes black, laptop screen becomes the secondary and my external monitor becomes the primary display. Because of Ubuntu is unable to remember to the previously set display mode, I usually change it a bit after I have logged in. However, if I (would like to) do this too quickly, say... less than 4-5 seconds after I can see my desktop, my session gets terminated and I'm returned to the login screen. You can repeat it indefinitely, it always worked for me. I thought it's because of one of my extensions but I could reproduce it after I have disabled them. I haven't found any useful log entries. UPDATE 1: While I was writing this, I thought it has something to do with theme loading or something like this, so I continued to test with startup applications. I just rarely managed to reproduce this bug when I didn't execute the following script (as a file) at login: ``` #!/bin/bash sleep 1s; firefox & sleep 1s; thunderbird & ``` I also noticed that after I have some faulty logins and then I login without changing display mode, I >sometimes< have no desktop, no startup applications and when I click power off/logout buttons nothing happens, but that's sure I will being logged out randomly in the near future - even if I don't touch my computer (I'm talking about minutes). Plus, I can see the desktop and the top bar (so it's the primary screen) with two wide black bars on the two sides of my laptop monitor for a moment before I get logged out. (However, I don't see any resolution changes so I guess it's not 640x480, or 800x600, etc.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 1 21:00:45 2017 DisplayManager: gdm3
[Desktop-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language
Same problem for me for french traduction. http://image.noelshack.com/fichiers/2017/44/3/1509546937-bug-ko.png It's not critical bug but I hope it will be fixed more quick now than ubuntu gnome and ubuntu are same team now. -- 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/1491787 Title: Gnome's Activities Overview search is always in English, regardless of the system language Status in Ubuntu GNOME: New Status in Ubuntu Translations: New Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hey, I'm referring to this issue on AskUbuntu: http://askubuntu.com/questions/600656/change-language-of-the-gnome- shell-overview On my Ubuntu Gnome 15.04 system all entries from the gnome-control- center are shown in English in the Gnome-Shell overview (see screenshot in the above mentioned link), even though my system language is German. The entries in the gnome-control-center itself are however in German. Is this due to a bug or missing translations? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1491787/+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 1729181] Re: directory and file icons are same in "Files" app
What session and theme do you use? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1729181 Title: directory and file icons are same in "Files" app Status in nautilus package in Ubuntu: New Bug description: while browsing File Manager with nautilus, it does not show different icons for files and directory. Please see attached screenshot. using Ubuntu Desktop 17.10 with wayland GNOME nautilus 3.26.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729181/+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 1724105] Re: Privacy : Deactivating screen lock doesn't work
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. -- 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/1724105 Title: Privacy : Deactivating screen lock doesn't work Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: What steps do I need to follow to reproduce this bug : Install gnome- session. In that session, open System Settings/Privacy Uncheck Lock Screen. What did I expect to happen : When opening the lid of my laptop, I was expecting to see no login screen and be back right away in my session, without having to enter my password. What actually happens: After opening the lid, the screen flashes, then goes black. After hitting the space bar, I get the "clock screen", swipe up, then get login screen. Sometimes, the screen just freeze. Have to hard reboot. Side effect : Lock Screen activated, only way that the laptop will come back from sleep normally. Dell XPS 13 (9360) --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016) Package: gnome-shell 3.26.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724105/+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 1729264] Re: Regression of file rename popover bug
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1729264 Title: Regression of file rename popover bug Status in nautilus package in Ubuntu: New Bug description: It seems ctrl+z undo tries to undo the last file operation rather than the last text edit in the file name dialog. nautilus devs have fixed this behaviour previously, so it's probably an Ubuntu patch that's causing the problem. Here's the patch that was committed to fix it previously: https://gitlab.gnome.org/GNOME/nautilus/commit/bf6b1e2c2f0cd3d882f99029af79a3439bdacec1 Here's a video showing that the behaviour regression in 17.10 (ctrl+z is used to undo a text edit): https://www.dropbox.com/s/pvywye6alea76j4/nautilus_undo_history_bug.movie.mp4?dl=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729264/+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 1708306] Re: Middle click paste not working in terminal launched from context menu
*** This bug is a duplicate of bug 1722121 *** https://bugs.launchpad.net/bugs/1722121 I'm marking it as anachronistic duplicate because investigating happened in the other bugreport. ** This bug has been marked a duplicate of bug 1722121 Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop -- 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/1708306 Title: Middle click paste not working in terminal launched from context menu Status in gnome-terminal package in Ubuntu: Confirmed Bug description: On a clean up to date Artful system I noticed some odd behavior in the terminal. Steps to reproduce:- 1. Open a terminal by right clicking the desktop and Open Terminal. 2. Double click the command prompt 3. Middle click to paste Expected behavior Contents of terminal appears pasted Actual behavior Nothing Oddly, terminals launched from the activities menu or by pressing CTRL+ALT+T don't exhibit this behavior. In addition, sometimes it works if you copy from a terminal launched in the two mentioned ways, and try to paste into the one launched from the desktop. https://youtu.be/aKfb9DCfPUI Video showing me launching a terminal from the activities menu where middle click paste works. Launching a terminal from the desktop context menu and middle click paste not working. Then launching gedit where also I can't paste what I have highlighted in the terminal, but can copy from gedit to terminal via middle click paste. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 2 23:08:44 2017 InstallationDate: Installed on 2017-08-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) 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/1708306/+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 1722256] Re: Wifi connection status icon shows a "?" when connected
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1722256 Title: Wifi connection status icon shows a "?" when connected Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: Wifi connection status icon on the top bar shows a "?" even when connected to a wifi network. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: gnome-shell 3.26.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722256/+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 1729372] Re: traduction fr not valid for settings in dash gnome-shell
it's a gnome-control-center issue, see bug #1712664 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1729372 Title: traduction fr not valid for settings in dash gnome-shell Status in gnome-shell package in Ubuntu: Invalid Bug description: Hi, I have a fresh install of Ubuntu 17.10 in french. When i put something in search dash I have result in french but not for settings search : http://image.noelshack.com/fichiers/2017/44/3/1509546937-bug-ko.png When I clic at more setting search result, traduction are fine in french : http://image.noelshack.com/fichiers/2017/44/3/1509546937-bug-ok.png other search result category are in french : http://image.noelshack.com/fichiers/2017/44/3/1509548466-capture-d -ecran-de-2017-11-01-16-00-29.png So it's just a traduction bug for result search for settings in dash. More infos : 'lsb_release -rd : Description: Ubuntu 17.10 Release: 17.10 apt-cache policy gnome-shell : gnome-shell: Installé : 3.26.1-0ubuntu5 Candidat : 3.26.1-0ubuntu5 Table de version : *** 3.26.1-0ubuntu5 500 500 http://fr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages Sincerely, P.S : sorry for my bad english ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 15:52:05 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-30 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729372/+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 1607711] Re: Starting nautilus crashes with Segmentation Fault
don't reopen expired bugs if you are not the original submiter, report a
new bug instead
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1607711
Title:
Starting nautilus crashes with Segmentation Fault
Status in nautilus package in Ubuntu:
Invalid
Bug description:
After last updates to my Ubuntu 16.04 x64 nautilus crashes with the
following message:
misel@misel-amphinicy[~]:
[11:44:18] $ nautilus
Maximum number of clients reached
** (nautilus:25112): WARNING **: Could not open X display
sys:1: PyGIWarning: Nautilus was imported without specifying a version first.
Use gi.require_version('Nautilus', '3.0') before import to ensure that the
right version gets loaded.
[Errno 2] No translation file found for domain: 'nautilus-image-tools'
Initializing nautilus-image-converter extension
Initializing nautilus-dropbox 2.10.0
** (nautilus:25112): CRITICAL **:
nautilus_menu_provider_get_background_items: assertion
'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
** (nautilus:25112): CRITICAL **:
nautilus_menu_provider_get_background_items: assertion
'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Maximum number of clients reached
(nautilus:25112): GnomeDesktop-WARNING **: Unable to open display ':0' when
setting background pixmap
Segmentation fault (core dumped)
misel@misel-amphinicy[~]:
[11:44:20]
backtrace:
misel@misel-amphinicy[/usr/bin]:
[11:46:17] $ LC_ALL=EN_US gdb nautilus
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop
With the help of main gnome-terminal developer Christian (thanks!) we've noticed the following: When "Ubuntu" graphical session is chosen, the background (nautilus- desktop) uses X11 (XWayland). This can be confirmed by xeyes following the mouse movements made there. (With "GNOME" graphical session this is not the case, the background there is native Wayland.) Using dbus-monitor, this is seen when opening a "good" terminal with the global shortcut Ctrl+Alt+T: method call time=1509569901.444518 sender=:1.72 -> destination=:1.73 serial=12 path=/org/gnome/Terminal/Factory0; interface=org.gnome.Terminal.Factory0; member=CreateInstance array [ dict entry( string "display" variant array of bytes "wayland-0" + \0 ) dict entry( string "encoding" variant string "UTF-8" ) ] and its counterpart with the "bad" terminal (desktop's right click menu) is: method call time=1509569929.217075 sender=:1.64 -> destination=:1.80 serial=148 path=/org/gnome/Terminal/Factory0; interface=org.gnome.Terminal.Factory0; member=CreateInstance array [ dict entry( string "display" variant array of bytes ":1.0" + \0 ) dict entry( string "desktop-startup-id" variant array of bytes "_TIME180922528" + \0 ) dict entry( string "active" variant boolean true ) ] Later on, however, pretty much the same set of environment variables, including "DISPLAY=:1" and "WAYLAND_DISPLAY=wayland-0" are passed in both cases. (The concrete values might vary of course, typically it's "DISPLAY=:0" but I'm opening a second graphical session for testing.) (The only difference in the environment variables is the presence/absence of DESKTOP_AUTOSTART_ID. I guess that's irrelevant.) So there's the following to the story: - gnome-terminal was meant to support multiple displays handled by the same server process, but it suffered from problems anyway. Christian has just removed this feature, which is a proper workaround/fix for this bug. The fix is at https://git.gnome.org/browse/gnome- terminal/commit/?id=36cce22 and https://git.gnome.org/browse/gnome- terminal/commit/?id=8d75f15. Ubuntu should go ahead and backport it. - nautilus-desktop should be converted to a proper Wayland app with no leftover X11 stuff. That would also be a proper fix on its own, without the gnome-terminal fix. (Isn't this done in mainstream GNOME yet? Does Ubuntu bring back the X11 dependency with a patch? Dunno.) - Why did this cause copy-paste not working and the theme not being the correct one? Perhaps there's no gnome-settings-daemon running for the X11/XWayland display, and perhaps its clipboard is not (or not properly) connected to Wayland's. We're unsure about these. At this point I'm passing the ball to Ubuntu developers to come up with some fix based on these findings. ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1722121 Title: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop Status in gnome-terminal package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 gnome-terminal: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Expected behavior Right-clicking on the desktop and selecting "Open Terminal" should give me the same terminal as running gnome-terminal or or opening terminal in the activity view. What happens Gnome-Terminal launches with the correct GTK theme, but not the correct theme variant (light instead of dark). The "Preferences" option is gone from the top bar. Trying to copy something from the terminal and pasting outputs "unavailable". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 22:49:01 2017 InstallationDate: Installed on 2017-09-30 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1729394] Re: 17.10 - Second monitor in portrait mode causes graphical issue
seems similar to bug #1724977 / https://bugzilla.gnome.org/show_bug.cgi?id=789675 ** Bug watch added: GNOME Bug Tracker #789675 https://bugzilla.gnome.org/show_bug.cgi?id=789675 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1729394 Title: 17.10 - Second monitor in portrait mode causes graphical issue Status in wayland package in Ubuntu: New Bug description: Having a secondary monitor in landscape mode works flawlessly in 17.10. However, problems arise when I set a monitor to portrait mode. One thing that happens is when I bring my mouse to the edge of the screen, I see the cursor mirrored on the second screen. The main issue is when I hit the windows key and try to search for an application. The results look all scrambled and my secondary monitor is displayed in landscape mode with all of my windows. Look at my bug attachment to see a screenshot of what happens when I press the windows/super key and try to search for a program. On the left is my secondary monitor in portrait mode. When moving Windows to that monitor, it works as it should, but when I hit the Windows/super key to show all of my open windows, it displays in landscape. On the right is my main monitor in landscape mode. In that screen I was searching for my GEdit program. Specs: Integrated Intel graphics card Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1729394/+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 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1722121 Title: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop Status in gnome-terminal package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 gnome-terminal: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Expected behavior Right-clicking on the desktop and selecting "Open Terminal" should give me the same terminal as running gnome-terminal or or opening terminal in the activity view. What happens Gnome-Terminal launches with the correct GTK theme, but not the correct theme variant (light instead of dark). The "Preferences" option is gone from the top bar. Trying to copy something from the terminal and pasting outputs "unavailable". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 22:49:01 2017 InstallationDate: Installed on 2017-09-30 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1722121/+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 1392389] Re: rhythmbox crashed with SIGSEGV in totem_pl_parser_parse_with_base()
** Changed in: rhythmbox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1392389 Title: rhythmbox crashed with SIGSEGV in totem_pl_parser_parse_with_base() Status in rhythmbox package in Ubuntu: Fix Released Bug description: I am behind a firewall that requires me to login before I can use the internet. When rhythmbox checks podcast feeds when I am not logged in, I am greeted with a crash report with "rhythmbox crashed with SIGSEGV in totem_pl_parser_parse_with_base()" as the title. It would be nice if the function threw an exception when did not get what it expected and present an error rather than a crash. I would submit a patch, but do not have the coding expertise to do so :/ When I am logged into our filter to access the internet, I do not get this crash. It only happens when I am not logged into the filter. Description: Ubuntu 14.04.1 LTS Release: 14.04 rhythmbox: Installed: 3.0.2-0ubuntu2 Candidate: 3.0.2-0ubuntu2 Version table: *** 3.0.2-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1392389/+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 1729394] Re: 17.10 - Second monitor in portrait mode causes graphical issue
Thanks for adding that Brian. Appreciate it. Any type of other information or data I could provide to better help developers? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1729394 Title: 17.10 - Second monitor in portrait mode causes graphical issue Status in wayland package in Ubuntu: New Bug description: Having a secondary monitor in landscape mode works flawlessly in 17.10. However, problems arise when I set a monitor to portrait mode. One thing that happens is when I bring my mouse to the edge of the screen, I see the cursor mirrored on the second screen. The main issue is when I hit the windows key and try to search for an application. The results look all scrambled and my secondary monitor is displayed in landscape mode with all of my windows. Look at my bug attachment to see a screenshot of what happens when I press the windows/super key and try to search for a program. On the left is my secondary monitor in portrait mode. When moving Windows to that monitor, it works as it should, but when I hit the Windows/super key to show all of my open windows, it displays in landscape. On the right is my main monitor in landscape mode. In that screen I was searching for my GEdit program. Specs: Integrated Intel graphics card Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1729394/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Good luck! I went through several tries to get it right. Make sure after removing gdm that lightdm is installed.. that's key. And if you get a login screen, be sure to use Xorg. Those two things SHOULD get you on the right track hopefully. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
@CaptSaltyJack - I'm reinstalling from scratch...should be about an hour or so. Then before I do anything at all, I will go ahead with each of your steps and then report back if I have success or not. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1729441] [NEW] changing display mode after login terminates session
Public bug reported: When I login, I type the password on the laptop screen. (Maybe it's important.) After a while, while I'm waiting to get logged in, Ubuntu changes the display mode. Both monitor goes black, laptop screen becomes the secondary and my external monitor becomes the primary display. Because of Ubuntu is unable to remember to the previously set display mode, I usually change it a bit after I have logged in. However, if I (would like to) do this too quickly, say... less than 4-5 seconds after I can see my desktop, my session gets terminated and I'm returned to the login screen. You can repeat it indefinitely, it always worked (?) for me. I thought it's because of one of my extensions but I could reproduce it after I have disabled them. I haven't found any useful log entries. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 1 21:00:45 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-08 (85 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-21 (10 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1729441 Title: changing display mode after login terminates session Status in gnome-shell package in Ubuntu: New Bug description: When I login, I type the password on the laptop screen. (Maybe it's important.) After a while, while I'm waiting to get logged in, Ubuntu changes the display mode. Both monitor goes black, laptop screen becomes the secondary and my external monitor becomes the primary display. Because of Ubuntu is unable to remember to the previously set display mode, I usually change it a bit after I have logged in. However, if I (would like to) do this too quickly, say... less than 4-5 seconds after I can see my desktop, my session gets terminated and I'm returned to the login screen. You can repeat it indefinitely, it always worked (?) for me. I thought it's because of one of my extensions but I could reproduce it after I have disabled them. I haven't found any useful log entries. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 1 21:00:45 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-08 (85 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-21 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729441/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
I'm sorry, it still does not work for me with my Perfection V33 Scanner, even though everything is similar. -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 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/1707352/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
did the steps in post #60now I'm just frozen with no opportunity to do anything at all. gonna have to reinstall 17.10 once again. This will me my 6th reinstall... -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1721707] Re: Rhythmbox crashes after pressing "Install Additional Software"
From: gdb-RB-Crash.txt Backtrace stopped: Cannot access memory at address 0x7fffbc48 Core seems to be corrupted. That would normally mean RAM / disk space / swap issue. Please recheck and attach a proper backtrace, if the crash happens again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1721707 Title: Rhythmbox crashes after pressing "Install Additional Software" Status in rhythmbox package in Ubuntu: Incomplete Bug description: Steps: 1. Add .m4a music to the library (or any music with not installed codecs) 2. Go to 'Import Errors' on the left sidebar 3. Press 'Install Additional Software' at the bottom right 4. Rhythmbox crashes I attached a backtrace. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: rhythmbox 3.4.1-2ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 09:11:16 2017 InstallationDate: Installed on 2017-10-02 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1721707/+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 1536217] Re: crash when toggling grilo plugin
Not reproducible anymore ( in Ubuntu 17.10 ). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1536217 Title: crash when toggling grilo plugin Status in rhythmbox package in Ubuntu: Confirmed Bug description: Go to Tools/plugins, toggle grilo media browser on/off or off/on and rhythmbox will crash. whoopsie sent a crash file but I wasn't prompted to file a bug as part of that upload so filing here. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rhythmbox 3.2.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3 Uname: Linux 4.3.0-6-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 20 08:56:01 2016 InstallationDate: Installed on 2015-06-13 (220 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: rhythmbox UpgradeStatus: Upgraded to xenial on 2016-01-12 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1536217/+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 1547297] Re: No auto login in Ubuntu GNOME Xenial
I have the same problem in Ubuntu 17.10. I configure in settings my user to autologon in system but it don't works. If I type in a console: cat /etc/gdm3/custom.conf | grep Auto I have this: AutomaticLoginEnable=True AutomaticLogin=leo I think that it's correct, but It don't login into my gnome xorg session ** Changed in: gdm3 (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1547297 Title: No auto login in Ubuntu GNOME Xenial Status in Ubuntu GNOME: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Confirmed Bug description: Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto login during installation, but once the installation was complete and I booted into Ubuntu GNOME I was asked for my password. I looked in the user UI and auto login was set to off, so I unlocked it, selected auto login = on, clicked on lock again, and rebooted but was once again asked for my password and the user UI once again showed auto login = off. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gdm3 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Feb 18 20:26:14 2016 InstallationDate: Installed on 2016-02-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+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 1193525] Re: rhythmbox crashed with SIGSEGV in sem_post()
Is this still a problem ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1193525 Title: rhythmbox crashed with SIGSEGV in sem_post() Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Confirmed Bug description: Possible Workaround: Try disabling all the python based plugins: * Context Pane * Cover art search * IM status * Magnatune store * Python console * Send tracks * Song lyrics * Ubuntu One * Zeitgeist Crashed while clicking 'next' ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Sat Jun 22 11:12:40 2013 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2012-09-09 (285 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MarkForUpload: True ProcCmdline: rhythmbox ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76731561e0 : mov(%rdi),%eax PC (0x7f76731561e0) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0 PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in sem_post() UpgradeStatus: Upgraded to saucy on 2013-05-25 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1193525/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Bernadette: Just to make sure, did you try the below in this exact order? sudo apt purge gdm3 (optional step if lightdm is not auto installe) sudo apt install -y lightdm sudo apt purge nvidia* sudo apt install linux-headers-$(uname -r) sudo apt install nvidia-384 This worked for me. At the lightdm login screen, I had to choose "Ubuntu on Xorg" as the default environment before logging in. Wayland does not work at all. Your kernel should be ok. You may be experiencing an unrelated issue. 17.10 is kind of a mess. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1729394] Re: 17.10 - Second monitor in portrait mode causes graphical issue
** Tags added: artful ** Package changed: ubuntu => wayland (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1729394 Title: 17.10 - Second monitor in portrait mode causes graphical issue Status in wayland package in Ubuntu: New Bug description: Having a secondary monitor in landscape mode works flawlessly in 17.10. However, problems arise when I set a monitor to portrait mode. One thing that happens is when I bring my mouse to the edge of the screen, I see the cursor mirrored on the second screen. The main issue is when I hit the windows key and try to search for an application. The results look all scrambled and my secondary monitor is displayed in landscape mode with all of my windows. Look at my bug attachment to see a screenshot of what happens when I press the windows/super key and try to search for a program. On the left is my secondary monitor in portrait mode. When moving Windows to that monitor, it works as it should, but when I hit the Windows/super key to show all of my open windows, it displays in landscape. On the right is my main monitor in landscape mode. In that screen I was searching for my GEdit program. Specs: Integrated Intel graphics card Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1729394/+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 1487666] Re: non-fatal error right after login (just upgraded the kernel to 4.1)
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1487666 Title: non-fatal error right after login (just upgraded the kernel to 4.1) Status in bbswitch package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: During kernel install, the log said (see attachment for the complete log): [...] Entering directory '/var/lib/dkms/nvidia-340/340.76/build' NVIDIA: calling KBUILD... make[2]: Entering directory '/usr/src/linux-headers-4.1.0-040100rc2-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ [...] but following that instruction I get more errors: /usr/src/linux-headers-4.1.0-040100rc2-generic$ sudo make oldconfig && make prepare [sudo] password for presence: scripts/kconfig/conf --oldconfig Kconfig # # configuration written to .config # arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support Makefile:657: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler scripts/kconfig/conf --silentoldconfig Kconfig *** Error during update of the configuration. scripts/kconfig/Makefile:37: recipe for target 'silentoldconfig' failed make[2]: *** [silentoldconfig] Error 1 Makefile:541: recipe for target 'silentoldconfig' failed make[1]: *** [silentoldconfig] Error 2 make[1]: *** No rule to make target 'arch/x86/syscalls/syscall_32.tbl', needed by 'arch/x86/syscalls/../include/generated/asm/syscalls_32.h'. Stop. arch/x86/Makefile:181: recipe for target 'archheaders' failed make: *** [archheaders] Error 2 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: bbswitch-dkms 0.7-2ubuntu1 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 DKMSKernelVersion: 4.1.0-040100rc2-generic Date: Fri Aug 21 21:43:25 2015 InstallationDate: Installed on 2014-05-31 (447 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 0.7-2ubuntu1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: bbswitch Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1487666/+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 1487666] Re: non-fatal error right after login (just upgraded the kernel to 4.1)
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1487666 Title: non-fatal error right after login (just upgraded the kernel to 4.1) Status in bbswitch package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: During kernel install, the log said (see attachment for the complete log): [...] Entering directory '/var/lib/dkms/nvidia-340/340.76/build' NVIDIA: calling KBUILD... make[2]: Entering directory '/usr/src/linux-headers-4.1.0-040100rc2-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ [...] but following that instruction I get more errors: /usr/src/linux-headers-4.1.0-040100rc2-generic$ sudo make oldconfig && make prepare [sudo] password for presence: scripts/kconfig/conf --oldconfig Kconfig # # configuration written to .config # arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support Makefile:657: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler scripts/kconfig/conf --silentoldconfig Kconfig *** Error during update of the configuration. scripts/kconfig/Makefile:37: recipe for target 'silentoldconfig' failed make[2]: *** [silentoldconfig] Error 1 Makefile:541: recipe for target 'silentoldconfig' failed make[1]: *** [silentoldconfig] Error 2 make[1]: *** No rule to make target 'arch/x86/syscalls/syscall_32.tbl', needed by 'arch/x86/syscalls/../include/generated/asm/syscalls_32.h'. Stop. arch/x86/Makefile:181: recipe for target 'archheaders' failed make: *** [archheaders] Error 2 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: bbswitch-dkms 0.7-2ubuntu1 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 DKMSKernelVersion: 4.1.0-040100rc2-generic Date: Fri Aug 21 21:43:25 2015 InstallationDate: Installed on 2014-05-31 (447 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 0.7-2ubuntu1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: bbswitch Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1487666/+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 1729394] [NEW] 17.10 - Second monitor in portrait mode causes graphical issue
You have been subscribed to a public bug: Having a secondary monitor in landscape mode works flawlessly in 17.10. However, problems arise when I set a monitor to portrait mode. One thing that happens is when I bring my mouse to the edge of the screen, I see the cursor mirrored on the second screen. The main issue is when I hit the windows key and try to search for an application. The results look all scrambled and my secondary monitor is displayed in landscape mode with all of my windows. Look at my bug attachment to see a screenshot of what happens when I press the windows/super key and try to search for a program. On the left is my secondary monitor in portrait mode. When moving Windows to that monitor, it works as it should, but when I hit the Windows/super key to show all of my open windows, it displays in landscape. On the right is my main monitor in landscape mode. In that screen I was searching for my GEdit program. Specs: Integrated Intel graphics card Ubuntu 17.10 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: artful bot-comment gnome-17.10 -- 17.10 - Second monitor in portrait mode causes graphical issue https://bugs.launchpad.net/bugs/1729394 You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. -- 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 1729433] Re: LibreOffice doesn't remember non-maximized size when closed while maximized
This might be eligible for a `regression-release` tag since 17.04 didn't have this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1729433 Title: LibreOffice doesn't remember non-maximized size when closed while maximized Status in libreoffice package in Ubuntu: New Bug description: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/+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 1724977] Re: two mouse cursors visible at the same time on rotated screen
My notebook is using the default Intel driver. -- 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/1724977 Title: two mouse cursors visible at the same time on rotated screen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: When my 2nd Asus (Ancor) display is in portrait mode and is set to be to the left of my centered landscape display in extended mode, moving the mouse to roughly the left 20% of my landscape display will show a mouse cursor on my landcape display AND portrait display at the same time. Oddly moving a window into this area only shows on the landscape display. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 13:43:30 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 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/gnome-shell/+bug/1724977/+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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Greetings, this bug is also affecting my brand new fresh clean install of Ubuntu 17.10 to my Dell XPS 15 laptop. I have gone thru this thread and have tried every single trick/hack and nothing allows the machine to boot successfully once the Nvidia drivers are installed. In fact, I am facing consisten boot loops no matter which driver I install. I was also unsuccessful in being able to log in wiht lightdm, even though the machine did successfullly boot to the lightdm login screen after Nvidia-375 was installed. I was wondering if I should try a different kernel than the one that ships with 17.10?? I have as GeoForce GTX 1050 video card in the machine, so its not uncommon. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1729433] [NEW] LibreOffice doesn't remember non-maximized size when closed while maximized
Public bug reported: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1729433 Title: LibreOffice doesn't remember non-maximized size when closed while maximized Status in libreoffice package in Ubuntu: New Bug description: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/+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 1729428] [NEW] /usr/lib/firefox/firefox:11:mozilla::ipc::MessageChannel::OnChannelErrorFromLink:mozilla::ipc::ProcessLink::OnChannelError:event_process_active_single_queue:even
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding firefox. This problem was most recently seen with package version 53.0.3+build1-0ubuntu0.16.04.2, the problem page at https://errors.ubuntu.com/problem/7c18a62611c0ea4abbb769fd81ab5947015bf4bc 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/. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: xenial zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1729428 Title: /usr/lib/firefox/firefox:11:mozilla::ipc::MessageChannel::OnChannelErrorFromLink:mozilla::ipc::ProcessLink::OnChannelError:event_process_active_single_queue:event_process_active:event_base_loop Status in firefox package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding firefox. This problem was most recently seen with package version 53.0.3+build1-0ubuntu0.16.04.2, the problem page at https://errors.ubuntu.com/problem/7c18a62611c0ea4abbb769fd81ab5947015bf4bc 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/firefox/+bug/1729428/+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 1729427] [NEW] /usr/bin/yelp:11:elf_machine_rela_relative:elf_dynamic_do_Rela:_dl_relocate_object:dl_main:_dl_sysdep_start
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding yelp. This problem was most recently seen with package version 3.18.1-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/498b5d720bc1e2ac9df4297f5a5556cc3c14359d 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/. ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: precise saucy xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1729427 Title: /usr/bin/yelp:11:elf_machine_rela_relative:elf_dynamic_do_Rela:_dl_relocate_object:dl_main:_dl_sysdep_start Status in yelp package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding yelp. This problem was most recently seen with package version 3.18.1-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/498b5d720bc1e2ac9df4297f5a5556cc3c14359d 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/yelp/+bug/1729427/+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 1487666] Re: non-fatal error right after login (just upgraded the kernel to 4.1)
After trying to build a different kernel module on Ubuntu 17.04 (Zesty), I can replicate these errors. The first "error" isn't really an error unless the echo statements are triggered if the "test" command fails: test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( [...SNIP...] ) Notice in the part with parentheses that each line is prefixed by: echo >&2 " ... " This behavior of GNU Make is normal. It will print back the commands it runs unless told not to. If you saw this message without 'echo >&2' in front, it would immediately exit afterwards with a message like: make: *** [all] Error 1 This "test -e [...]" command is checking that the mentioned files exist within the Linux Kernel source directory. This directory is mentioned above when Make changes into it: "/usr/src/linux- headers-4.1.0-040100rc2-generic" The two files it is checking exist are therefore: /usr/src/linux-headers-4.1.0-040100rc2-generic/include/generated/autoconf.h # AND: /usr/src/linux-headers-4.1.0-040100rc2-generic/include/config/auto.conf You can look for these files yourself to make sure they exist. If so, this particular output from Make can be ignored. If they don't exist, then you can usually follow the instructions for running "make oldconfig && make prepare" within the Linux Kernel source directory to create them. The second error message you are getting looks like the real one: make[1]: *** No rule to make target 'arch/x86/syscalls/syscall_32.tbl', needed by 'arch/x86/syscalls/../include/generated/asm/syscalls_32.h'. Stop. arch/x86/Makefile:181: recipe for target 'archheaders' failed make: *** [archheaders] Error 2 This error is listed around the Internet surrounding building Linux Kernel modules on Debian (and Fedora) against Linux Kernel source that is missing "syscalls_32.tbl" and "syscalls_32.h" files. These files should exist in the "Vanilla" Linux Kernel source code which can always be found at kernel.org. However, it appears that some distributions such as Debian and Ubuntu are missing these files in their newer "linux-headers-*" packages. This appears to be a packaging bug which can be filed against "linux- headers-*" package. The "linux-headers" packages should include these files in order to build kernel modules using them. The workaround is to get a full copy of the appropriate version of the Linux Kernel source tree by whatever means, and to use this directory to build your modules against. Note that I'm answering this question based on my personal experience with the linux-headers-4.10.0-37-generic package on Ubuntu 17.04 "Zesty Zapus". I'm under the assumption that this file has been missing from the "linux-headers-*" packages for a while now based on the many instances of people running into this error since 2013 posted on the internet. If you can somehow locate the "syscalls_32.tbl" and "syscalls_32.h" files within your /usr/src/linux-headers-4.1.0-040100rc2-generic/ directory, then you should check the bbswitch module's source directory Makefile. Sometimes the way an external Kernel Module's Makefile is written prevents it from finding the right linux-headers or /lib/modules/ directory during build.Other solutions have been posted for changing the way GNU Make is finding the Linux Source directory and the Kernel Module's working directory usually with $$(PWD) or $(shell $PWD). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1487666 Title: non-fatal error right after login (just upgraded the kernel to 4.1) Status in bbswitch package in Ubuntu: Confirmed Bug description: During kernel install, the log said (see attachment for the complete log): [...] Entering directory '/var/lib/dkms/nvidia-340/340.76/build' NVIDIA: calling KBUILD... make[2]: Entering directory '/usr/src/linux-headers-4.1.0-040100rc2-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ [...] but following that instruction I get more errors: /usr/src/linux-headers-4.1.0-040100rc2-generic$ sudo make oldconfig && make prepare [sudo] password for presence: scripts/kconfig/conf --oldconfig Kconfig # # configuration written to .config # arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support Makefile:657: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler scripts/kconfig/conf --silentoldconfig Kconfig *** Error during update of the configuration. scripts/kconfig/Makefile:37: recipe for
[Desktop-packages] [Bug 1728591] Re: search bar doesn't get the focus
** Summary changed: - search bar don't get the focus + search bar doesn't get the focus -- 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/1728591 Title: search bar doesn't get the focus Status in gnome-shell package in Ubuntu: New Bug description: When I start typing in the activities overview screen I should type into the upper search box. However, sometimes after I press super or super+A (just because I have no activities button in the top-left corner) and I start typing, all my typed characters goes into the currently focused window. Even if I have noticed that I didn't type into the correct location, I was unable to click the search bar to get it focused, because (sometimes) all the overview window gets closed by this click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728591/+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 1487666] Re: non-fatal error right after login (just upgraded the kernel to 4.1)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bbswitch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1487666 Title: non-fatal error right after login (just upgraded the kernel to 4.1) Status in bbswitch package in Ubuntu: Confirmed Bug description: During kernel install, the log said (see attachment for the complete log): [...] Entering directory '/var/lib/dkms/nvidia-340/340.76/build' NVIDIA: calling KBUILD... make[2]: Entering directory '/usr/src/linux-headers-4.1.0-040100rc2-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ [...] but following that instruction I get more errors: /usr/src/linux-headers-4.1.0-040100rc2-generic$ sudo make oldconfig && make prepare [sudo] password for presence: scripts/kconfig/conf --oldconfig Kconfig # # configuration written to .config # arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support Makefile:657: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler scripts/kconfig/conf --silentoldconfig Kconfig *** Error during update of the configuration. scripts/kconfig/Makefile:37: recipe for target 'silentoldconfig' failed make[2]: *** [silentoldconfig] Error 1 Makefile:541: recipe for target 'silentoldconfig' failed make[1]: *** [silentoldconfig] Error 2 make[1]: *** No rule to make target 'arch/x86/syscalls/syscall_32.tbl', needed by 'arch/x86/syscalls/../include/generated/asm/syscalls_32.h'. Stop. arch/x86/Makefile:181: recipe for target 'archheaders' failed make: *** [archheaders] Error 2 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: bbswitch-dkms 0.7-2ubuntu1 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 DKMSKernelVersion: 4.1.0-040100rc2-generic Date: Fri Aug 21 21:43:25 2015 InstallationDate: Installed on 2014-05-31 (447 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 0.7-2ubuntu1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: bbswitch Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1487666/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
I verified that my Epson V300 works with a fresh Ubuntu 17.10
installation by doing the following steps
1. Install libsane1 1.0.27-1~experimental2ubuntu2.1
If you don't want to enable the proposed repository the easiest way is
to download the files and install them from local
https://launchpad.net/ubuntu/artful/+upload/16734103/+files/libsane1_1.0.27-1~experimental2ubuntu2.1_amd64.deb
https://launchpad.net/ubuntu/artful/+upload/16734103/+files/sane-
utils_1.0.27-1~experimental2ubuntu2.1_amd64.deb
https://launchpad.net/ubuntu/artful/+upload/16734103/+files/libsane-
common_1.0.27-1~experimental2ubuntu2.1_all.deb
2. Install iscan-gt-f720-bundle-1.0.1.x64.deb.tar.gz
3. Copy (or move) the files from /usr/lib/sane (libsane-epkowa.la,
libsane-epkowa.so.1, libsane-epkowa.so.1.0.15) to /usr/lib/x86_64-linux-
gnu/sane
4. generate a file /etc/udev/rules.d/79-udev-epson.rules with the following
content:
# chmod device EPSON group
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb",
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"
No reboot needed
After these steps you can attach your scanner and turn it on. It will
start to download the firmware (you can see some blinking lights and
hear some noise). As soon downloading of firmware has finished you can
use the scanner by either Simple-scan, iScan or Xsane (if installed). No
root needed (except for installation).
As other Epson scanners using Iscan differ 'only' by the scanner
specific plugin I expect them to work too.
--
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/1707352
Title:
the change from libsane to libsane1 broke many (all?) 3rd party plug-
ins for sane
Status in sane-backends package in Ubuntu:
Fix Released
Status in sane-backends source package in Artful:
Fix Committed
Status in sane-backends package in Debian:
New
Bug description:
Note to SRU Team
The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it
needed to be a versioned Provides, not just a Provides.
Impact
==
1) The Debian maintainer renamed libsane to libsane1-experimental "to
match with the soname". This apparently fixes a Lintian warning, but
makes installing 3rd-party plug-ins hard, as they typically depend on
"libsane", not on "libsane1". The first try to add a "Provides:
libsane" to libsane1 (which created a virtual package) didn't make
drivers installable that claim to depend on a minimum version of
libsane as virtual packages are ignored in this case.
2) The soname change might be justified by the new version breaking
(several? most?) 3rd party plug-ins even if the library version number
doesn't indicate any bigger change than any ordinary new version of
the library - which might indicate that this phenomenon might be an
upstream bug.
libsane 1.0.25 in zesty includes libsane.so.1.25
libsane1 1.0.27 in artful includes libsane.so.1.27
It is to note that depending on the manufacturer for many old scanners
there won't be new versions of the plug-ins that are recompiled like
this.
Test Case
=
Visit http://support.epson.net/linux/en/iscan_c.html
Download the amd64 deb .tar.gz
Unzip it.
Install the iscan .deb from the core folder.
It won't install before this SRU because it Depends: libsane
Regression Potential
The fix here was proposed to the Debian maintainer in July but there's been
virtually zero response on it. In the meantime the workaround that was proposed
initially has started to result in automatically uninstalling gtk - which makes
the system basically useless.
It doesn't seem like adding the Provides will make things any worse
for third-party drivers but it has a goodme chance of making things
better for some.
Original Bug Report
===
I don't know if that can be prevented in the long run. But both brscan (for
my brother scanner) and iscan (for my epson scanners) have been broken by the
change from libsane to libsane1. For iscan I have unpackaged the debian
package, changed the dependency it contains from libsane to libsane1 and
installed the changed package. But even then my epson scanners no more work
leaving me without any scanner => Reporting a bug.
Impossibility of workarounds
Just installing an old version of libsane is impossible as it uninstalls
libgtk (which depends on libsane1 which conflicts with libsane) making the
system basically useless.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental1ubuntu2
Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Sat Jul 29 08:38:15 2017
EcryptfsInUse: Yes
SourcePackage: sane-backends
UpgradeStatus: No upgrade log present (probably fresh install)
To manage
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
A Test here showed:
without 79-udev-epson.rules in /etc/udev/rules.d
only 'sudo scanimage -L works'
with 79-udev-epson.rules in /etc/udev/rules.d
no root needed, a simple 'scanimage -L' is sufficient
maybe for the brscan scanners also only the udev rule is missing
try to add
# Brother scanners
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="0255", MODE="0660",
GROUP="scanner", ENV{libsane_matched}="yes"
to e.g. /lib/udev/rules.d/60-libsane1.rules
--
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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Do you have really copied the content of /usr/lib64/sane/ to /usr/lib/x86_64-linux-gnu/sane ? Whats with 79-udev-epson.rules in /etc/udev/rules.d ? -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 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/1707352/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
@Peter: Alternatively you could use the sources from SANE's daily git snapshots instead of using Debian experimental branch. This also breaks my ppa, which provides builds from SANE's daily git snapshots. -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 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/1707352/+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 1723802] Re: gnome-software: Something went wrong appears when launched
** Attachment removed: "picture showing the error shown" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723802/+attachment/4972199/+files/Workspace%201_036.jpg -- 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/1723802 Title: gnome-software: Something went wrong appears when launched Status in gnome-software package in Ubuntu: Confirmed Bug description: testing the release candidate. After installation, launched gnome software and editors picks and other software appear to be displayed correctly. However at the top of the screen is "something went wrong" - screenshot is attached ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 CurrentDesktop: Budgie:GNOME Date: Sun Oct 15 22:05:14 2017 InstallationDate: Installed on 2017-10-15 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Beta i386 (20171015) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723802/+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 1728378] Re: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1728378 Title: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed Status in network-manager package in Ubuntu: Confirmed Bug description: This error shows up in boot logs: "NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed". Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728378/+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 1729406] Re: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current statu
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-lang in Ubuntu. https://bugs.launchpad.net/bugs/1729406 Title: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') Status in texlive-lang package in Ubuntu: New Bug description: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-lang-english 2015.20160223-1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Nov 1 19:18:36 2017 DpkgHistoryLog: Start-Date: 2017-11-01 19:18:27 Commandline: aptdaemon role='role-upgrade-packages' sender=':1.79' Upgrade: update-manager-core:i386 (1:16.04.9, 1:16.04.10), update-manager:i386 (1:16.04.9, 1:16.04.10), python3-update-manager:i386 (1:16.04.9, 1:16.04.10) DuplicateSignature: package:texlive-lang-english:2015.20160223-1 Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ... dpkg: error processing package texlive-lang-english (--configure): package texlive-lang-english is not ready for configuration ErrorMessage: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-11 (174 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: texlive-lang Title: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.emacs.site-start.d.50texlive-lang-english.el: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1729406/+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 1729406] [NEW] package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current sta
Public bug reported: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-lang-english 2015.20160223-1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Nov 1 19:18:36 2017 DpkgHistoryLog: Start-Date: 2017-11-01 19:18:27 Commandline: aptdaemon role='role-upgrade-packages' sender=':1.79' Upgrade: update-manager-core:i386 (1:16.04.9, 1:16.04.10), update-manager:i386 (1:16.04.9, 1:16.04.10), python3-update-manager:i386 (1:16.04.9, 1:16.04.10) DuplicateSignature: package:texlive-lang-english:2015.20160223-1 Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ... dpkg: error processing package texlive-lang-english (--configure): package texlive-lang-english is not ready for configuration ErrorMessage: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-11 (174 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: texlive-lang Title: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.emacs.site-start.d.50texlive-lang-english.el: [deleted] ** Affects: texlive-lang (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-lang in Ubuntu. https://bugs.launchpad.net/bugs/1729406 Title: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') Status in texlive-lang package in Ubuntu: New Bug description: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-lang-english 2015.20160223-1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Nov 1 19:18:36 2017 DpkgHistoryLog: Start-Date: 2017-11-01 19:18:27 Commandline: aptdaemon role='role-upgrade-packages' sender=':1.79' Upgrade: update-manager-core:i386 (1:16.04.9, 1:16.04.10), update-manager:i386 (1:16.04.9, 1:16.04.10), python3-update-manager:i386 (1:16.04.9, 1:16.04.10) DuplicateSignature: package:texlive-lang-english:2015.20160223-1 Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ... dpkg: error processing package texlive-lang-english (--configure): package texlive-lang-english is not ready for configuration ErrorMessage: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-11 (174 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: texlive-lang Title: package texlive-lang-english 2015.20160223-1 failed to install/upgrade: package texlive-lang-english is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.emacs.site-start.d.50texlive-lang-english.el: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1729406/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
sudo scanimage -L No scanners were identified. -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 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/1707352/+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 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
However, please read comments #27 - #32 first before you do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes Status in wpa package in Ubuntu: Invalid Bug description: Ubuntu 14.04 LTS wpasupplicant 2.1-0ubuntu1 wpa_supplicant is writing to syslog every couple of minutes. Example output: May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 The message seems harmless as far as the network is concerned, meaning there is no problem with the wifi connection. But it's spamming the syslog, making it very difficult to find any other thing there, and it's generating constant writes to disk, and an unnecessarily large syslog file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+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 1107935] Re: Support for WPA Enterprise wireless networks
Desktop images at http://cdimage.ubuntu.com/xenial/daily-live/pending/ contain all the relevant packages and are good to go to be tested. These images have serial 20171101 or any later. Please test these images and confirm if the proposed updates resolve this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1107935 Title: Support for WPA Enterprise wireless networks Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in network-manager-applet package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in network-manager-applet source package in Xenial: Fix Committed Status in ubiquity source package in Xenial: Fix Committed Bug description: [Impact] In some installations, WPA2 Enterprise support is required to have access to the network to complete the installation. [Test cases] 1) Start installer from ubuntu-desktop image. 2) Follow the prompts to connect to the wireless network 3) Validate that a new dialog appears asking for the network password or credentials. [Regression potential] This impacts all wireless connections and so the type of regression to look for in general failure to connect to a secured wireless network when the authentication settings are correct (pre-shared key is correct), or in cases of connecting to an unsecured network. For network-manager-applet: - ubiquity uses nma gir to implement above - the nma gir is missbuilt in xenial, and does not have correct dependencies, thus is not usable in the same process when both NM and NMA are in use. This was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is minimal regression potential (just a rebuild) because there are no reverse dependencies of the nma gir in xenial. And there are unlikely to be any external users of nma gir on xenial, since it is broken / has wrong dependencies. --- Ubiquity doesn't appear to support WPA-Enterprise wifi networks -- there's just a single textbox shown to enter a passphrase, but most WPA-Enterprise will require at least a specific username and password, and possibly certificates. NM should already export this information on DBus, it should be a matter of using libnm-gtk to query the user for the connection information rather than prompting for it directly from the installer. <http://goo.gl/2iqv6j>: "If the selected network does require authentication, Network Manager’s standard dialog should open for you to enter those authentication details as soon as you choose “Connect…”." (Not to be confused with bug 1018160, about WEP networks.) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1107935/+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 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
On 10/30/17 11:23 AM, Christian Kujau wrote: > Launchpad really needs something similar to RESOLVED/DUPLICATE, as I had > to crawl through the whole report to find out that this is considered a > duplicate of 578431. > Righthand column: "Mark as duplicate" You can click and report this bug as a duplicate of 578431. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes Status in wpa package in Ubuntu: Invalid Bug description: Ubuntu 14.04 LTS wpasupplicant 2.1-0ubuntu1 wpa_supplicant is writing to syslog every couple of minutes. Example output: May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 The message seems harmless as far as the network is concerned, meaning there is no problem with the wifi connection. But it's spamming the syslog, making it very difficult to find any other thing there, and it's generating constant writes to disk, and an unnecessarily large syslog file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Please try 'sudo scanimage -L'
if scanimage succeeds and finds the scanner check if you have a file
named 79-udev-epson.rules in /etc/udev/rules.d
If yes content:
If no it should have the following content:
# chmod device EPSON group
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb",
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"
--
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/1707352
Title:
the change from libsane to libsane1 broke many (all?) 3rd party plug-
ins for sane
Status in sane-backends package in Ubuntu:
Fix Released
Status in sane-backends source package in Artful:
Fix Committed
Status in sane-backends package in Debian:
New
Bug description:
Note to SRU Team
The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it
needed to be a versioned Provides, not just a Provides.
Impact
==
1) The Debian maintainer renamed libsane to libsane1-experimental "to
match with the soname". This apparently fixes a Lintian warning, but
makes installing 3rd-party plug-ins hard, as they typically depend on
"libsane", not on "libsane1". The first try to add a "Provides:
libsane" to libsane1 (which created a virtual package) didn't make
drivers installable that claim to depend on a minimum version of
libsane as virtual packages are ignored in this case.
2) The soname change might be justified by the new version breaking
(several? most?) 3rd party plug-ins even if the library version number
doesn't indicate any bigger change than any ordinary new version of
the library - which might indicate that this phenomenon might be an
upstream bug.
libsane 1.0.25 in zesty includes libsane.so.1.25
libsane1 1.0.27 in artful includes libsane.so.1.27
It is to note that depending on the manufacturer for many old scanners
there won't be new versions of the plug-ins that are recompiled like
this.
Test Case
=
Visit http://support.epson.net/linux/en/iscan_c.html
Download the amd64 deb .tar.gz
Unzip it.
Install the iscan .deb from the core folder.
It won't install before this SRU because it Depends: libsane
Regression Potential
The fix here was proposed to the Debian maintainer in July but there's been
virtually zero response on it. In the meantime the workaround that was proposed
initially has started to result in automatically uninstalling gtk - which makes
the system basically useless.
It doesn't seem like adding the Provides will make things any worse
for third-party drivers but it has a goodme chance of making things
better for some.
Original Bug Report
===
I don't know if that can be prevented in the long run. But both brscan (for
my brother scanner) and iscan (for my epson scanners) have been broken by the
change from libsane to libsane1. For iscan I have unpackaged the debian
package, changed the dependency it contains from libsane to libsane1 and
installed the changed package. But even then my epson scanners no more work
leaving me without any scanner => Reporting a bug.
Impossibility of workarounds
Just installing an old version of libsane is impossible as it uninstalls
libgtk (which depends on libsane1 which conflicts with libsane) making the
system basically useless.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental1ubuntu2
Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Sat Jul 29 08:38:15 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/1707352/+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 1729400] Re: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
** Tags removed: need-duplicate-check -- 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/1729400 Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: Happened when installing Wine ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Wed Nov 1 22:24:09 2017 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-YWUqRx/137-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-11-01 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 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/1729400/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Downloaded and installed (no error messages) libsane-common, libsane1 and sane-utils. Thank you. Installed iscan-gt-x770-bundle-1.0.1.x64.deb with no errors. sudo sane-find-scanner gives found USB scanner (vendor=0x04b8 [EPSON], product=0x0130 [EPSON Scanner]) at libusb:006:004 # Your USB scanner was (probably) detected. scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in [YES], turned on [YES] and detected by the sane-find-scanner tool [YES - see above] iscan gives "Could not send command to scanner. Check the scanner's status" xsane gives "No devices available" -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 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/1707352/+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 1728585] Re: no screen, no keyboard, no mouse, high cpu usage
The same today. I just browsed some pages on the Internet and... BOOM. Unfortunately, I can't provide any details because I always have to unplug the cable from the power outlet. (I don't see any HD activity - as I remember - so I don't think it's because of out of memory.) I don't know what happened to Ubuntu 17.10 but it has became very unstable since the update. Can it be my fault? What should I do? Should I do a clean installation? Any suggestions? -- 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/1728585 Title: no screen, no keyboard, no mouse, high cpu usage Status in gnome-shell package in Ubuntu: New Bug description: I have just switched to the last (dynamic) workspace and a half minute later computer froze. It didn't reacted to any keyboard and mouse events, laptop lid closing (I hoped I can suspend) or HDMI cable un/plug (it sometimes used to solve some freezes). That's all I know. (I have reported the bug in gnome-shell.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 30 13:28:43 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-08 (83 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728585/+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 1729400] [NEW] package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
Public bug reported: Happened when installing Wine ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Wed Nov 1 22:24:09 2017 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-YWUqRx/137-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-11-01 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- 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/1729400 Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: Happened when installing Wine ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Wed Nov 1 22:24:09 2017 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-YWUqRx/137-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-11-01 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 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/1729400/+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
X-Org or wayland doens't matter. My scanner works with both (verfied).
Do you have a file named 79-udev-epson.rules in /etc/udev/rules.d ?
Mine has the following content:
# chmod device EPSON group
# ACTION=="add", ATTRS{manufacturer}=="EPSON", DRIVERS=="usb",
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0666"
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb",
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"
--
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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Did the steps above on my laptop. It works, though the "Ubuntu" login just logs me out right away (I believe that's Wayland). If I choose "Ubuntu on Xorg", I can log in with no issues. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1729388] Re: Xorg failed to load Intel driver for Axiomtek MANO300 which is based on Intel Braswell N3160
** Description changed: - The Mini-ITX SBC platform[1] is using Intel N3160 Processor with - Integrated Graphics Controller. However, the xorg failed to load the - Intel driver as autoconfigured driver. It fallback to using fb and - glamoregl for 2D acceleration method, which caused some issues[2], - including mouse cursor to get corrupted, or leave copies of cursor - around. + The Mini-ITX SBC platform[1] is using Intel N3160 Processor with Integrated Graphics Controller. However, the xorg failed to load the Intel driver as autoconfigured driver. It fallback to using fb and glamoregl for 2D acceleration method, which caused some issues[2] in multi-display mode, + including mouse cursor to get corrupted, or leave copies of cursor around. The issue can be reproduced on 17.04, 17.10. (and most likely on 16.04). The workaround for the issue is to install a xorg.conf to force xorg load the Intel driver, which solved the issue. Workaround: Please write the following content into /usr/share/X11/xorg.conf.d/90-intel.conf (without dash) -- cut -- Section "Device" - Identifier "intel" + Identifier "intel" Driver "intel" EndSection -- cut -- XorgLog [ 7.141] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 7.143] (II) xfree86: Adding drm device (/dev/dri/card0) [ 7.154] (--) PCI:*(0:0:2:0) 8086:22b1:8086:7270 rev 53, Mem @ 0x8000/16777216, 0x9000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072 [ 7.154] (II) LoadModule: "glx" [ 7.155] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 7.167] (II) Module glx: vendor="X.Org Foundation" [ 7.167] compiled for 1.19.3, module version = 1.0.0 [ 7.167] ABI class: X.Org Server Extension, version 10.0 [ 7.167] (==) Matched modesetting as autoconfigured driver 0 [ 7.167] (==) Matched fbdev as autoconfigured driver 1 [ 7.167] (==) Matched vesa as autoconfigured driver 2 UdevDb P: /devices/pci:00/:00:02.0 E: DEVPATH=/devices/pci:00/:00:02.0 E: DRIVER=i915 E: FWUPD_GUID=0x8086:0x22b1 E: ID_MODEL_FROM_DATABASE=Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller E: ID_PCI_CLASS_FROM_DATABASE=Display controller E: ID_PCI_INTERFACE_FROM_DATABASE=VGA controller E: ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller E: ID_VENDOR_FROM_DATABASE=Intel Corporation E: MODALIAS=pci:v8086d22B1sv8086sd7270bc03sc00i00 E: PCI_CLASS=3 E: PCI_ID=8086:22B1 E: PCI_SLOT_NAME=:00:02.0 E: PCI_SUBSYS_ID=8086:7270 E: SUBSYSTEM=pci E: USEC_INITIALIZED=5138332 [1] Mini-ITX SBC with Intel® Celeron® Processor N3160 - MANO300 - http://www.axiomtek.com/Default.aspx?MenuId=Products=ProductView=10882=136 [2] https://drive.google.com/open?id=0B4-sMl3SwjOILUZDX1hhSzlpSjQ ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Mon Oct 23 15:20:59 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: - Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) -Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] + Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) + Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2017-10-18 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=c173e5e9-804e-451f-af6b-0e25d1d5c1f8 ro quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: - + dmi.bios.date: 05/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M.
[Desktop-packages] [Bug 1716749] Re: Synaptics is not fully aware of display environment
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1716749 Title: Synaptics is not fully aware of display environment Status in xorg package in Ubuntu: Confirmed Bug description: In a dual monitor environment where separate Xfce4 desktops are running on each monitor, you can start Synaptic in either desktop environment, but if you start it on display :0.1, it shows the Authenticate pop-up window on display :0.0. Once the password is entered, the main window will then appear on display :0.1. All the components of a given program should be display-environment-aware. There are a number of system applications that have similar problems. I'll report them as I continue to encounter this problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 12 11:21:53 2017 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/ksh SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to zesty on 2017-05-27 (108 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1716749/+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 1729086] Re: Upgrading fontconfig-config causes fonts to look aliased
** Tags added: bionic -- 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/1729086 Title: Upgrading fontconfig-config causes fonts to look aliased Status in fontconfig package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: New Status in msttcorefonts package in Ubuntu: New Bug description: I'm using Ubuntu 18.04 dev and upgrading fontconfig-config to version 2.12.6-0ubuntu1 changed its dependencies from "fonts-dejavu-core | ttf-bitstream-vera | fonts-freefont-ttf | gsfonts-x11, ucf (>= 0.29)" to "ucf (>= 0.29), fonts-dejavu-core | ttf-bitstream-vera | fonts- liberation | fonts-freefont" which caused at default fonts-dejavu-core being additionally installed. My system has also ttf-mscorefonts-installer installed which utilizes custom rules to emulate the sharp looking fonts behavior Windows systems had. But installing fonts-dejavu-core alone causes this sharp look to get aliased again in the most places. A workaround for fontconfig-config is to install fonts-liberation as it seems to not break the sharp look. I can't tell exactly which of the 3 possible packages is the main cause for this issue: - Is that the installation of fonts-dejavu-core alone breaks the look a bug? - Needs ttf-mscorefonts-installer an update to take over priority or such? - Or is it possible that fontconfig-config could also technically support ttf-mscorefonts-installer as additional fonts dependency choice? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1729086/+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
