[Desktop-packages] [Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() f
yeah, ubuntu-bug would at least upload the ShellJournal file which hopefully contains the JS trace (as we've enabled it by default in ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1736664 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_unix64_inner() [any error message logged from JavaScript will look like this] Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.26.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+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 1336274] Re: HDMI Audio and all other audio disappeared from input sources and output sources in the audio control panel and stereo system is looping between audio is coming an
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1336274 Title: HDMI Audio and all other audio disappeared from input sources and output sources in the audio control panel and stereo system is looping between audio is coming and audio is not coming from the computer. Status in pulseaudio package in Ubuntu: Expired Bug description: After I did an update via system update, my system stopped working with audio. I then viewed the audio control panel and non of my output/input sources appear. I'm assuming that a component that Pulse Audio uses has been updated and ether Pulse Audio does not know how to communicate with it, or the component was not tested before being released. I have not changed any of my hardware configurations, so it cannot be a hardware issue. Also using XBMC and I'm guessing XBMC backed down to using ASLA, I am able to set HDMI out (which I had to change from previous configuration which I'm assuming is because Pulse Audio is unable to start) and it works fine until I stop using it for awhile. After I stop using it for awhile, I have to reboot the system to get XBMC working again. The way my stereo system (A Yamaha Receiver) is reacting to this is it's showing it has audio coming from the computer one second, then the other second it doesn't have audio. I'm assuming this is the daemon of Pulse Audio restarting over and over again after it cannot start. I ran pulse audio in verbose mode to show what module is causing it to fail to load, and it is module-systemd-login. The reason it is failing to load is "Failed to create session monitor: No space left on device" but none of my disks are anywhere near being used up, nor is my ram, so I have no idea as to what it could be referring to... Maybe it's referring to space in the audio hardware??? I do not know... I have attached the logs on here. Any help would be useful in getting my audio back, I'm a hacker/developer/all around geek who loves the terminal, so please ask any questions! Please do feel free to email me, I want my audio back! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 1 08:34:09 2014 InstallationDate: Installed on 2014-05-18 (43 days ago) InstallationMedia: It ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1336274/+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 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64 UpgradeStatus:
[Desktop-packages] [Bug 1810176] Re: libmtp error could not get object handles
[Expired for libmtp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libmtp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1810176 Title: libmtp error could not get object handles Status in libmtp package in Ubuntu: Expired Bug description: When connecting my android galaxy s7 phone via usb, I am unable to access my Music folder, which contains 380 subfolders. The file manager is inactive for a long time, and finally displays the error: Sorry, could not display all the contents of "Music": libmtp error: could not get object handles. Adding one more subfolder on the android side seems to work around the issue, so the issue is related to the number of items. Given this, my issue appears to be a specific example of the issue described in the link below. https://sourceforge.net/p/libmtp/bugs/1808/ Observed in linux mint 18.3 64 bit / ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1810176/+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 1834795] Re: xubuntu ethernet does not reconnect unless computer restarted, after power off/on modem or manually off/on "enable networking"
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1834795 Title: xubuntu ethernet does not reconnect unless computer restarted, after power off/on modem or manually off/on "enable networking" Status in network-manager package in Ubuntu: Expired Bug description: Xubuntu 19.04, 64bit, encrypted drive, using a desktop computer with ethernet to connect. Connects fine. Use openvpn also (from terminal). When the modem is turned off and on, or when the modem remains on but the ethernet connection is disabled (by unticking) and then ticking again "enable networking" in the applet taskbar, the connection does not re-establish. This is irregardless of the vpn, which even if i turn off, will not affect the lack of reconnection. If i ping bing.com, after trying to reconnect, I get back one response, but no multiple responses. ping bing.com PING bing.com (204.79.197.200) 56(84) bytes of data. This is slightly different to no connection being present, as then I would not even get back a single ping: "ping: bing.com: Temporary failure in name resolution" The only way to get a connection back is by restarting the system. And then it works fine. This is not an issue for ubuntu mate 19.04. The reconnection works fine, with no restart required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1834795/+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 1836051] Re: autamatic sleep notification cannot close
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1836051 Title: autamatic sleep notification cannot close Status in gnome-shell package in Ubuntu: Expired Bug description: I put my computer to sleep mode. 4 hours set afer no use. Vhen notification appeared, I put comp to sleep. After woke up, notification is still and can not close thru X. ubuntu-bug 18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836051/+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 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64
[Desktop-packages] [Bug 1843854] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
*** This bug is a duplicate of bug 1842022 *** https://bugs.launchpad.net/bugs/1842022 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1842022, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1843854/+attachment/5288419/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1843854/+attachment/5288421/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1843854/+attachment/5288425/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1843854/+attachment/5288426/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1843854/+attachment/5288427/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1843854/+attachment/5288428/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1843854/+attachment/5288429/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1842022 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1843854 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() Status in ibus package in Ubuntu: New Bug description: ... ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: ibus 1.5.19-4ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 13 02:40:36 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2019-09-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 SegvAnalysis: Segfault happened at: 0x7fb50345becb : orq $0x0,(%rsp) PC (0x7fb50345becb) ok source "$0x0" ok destination "(%rsp)" (0x7ffda1a7afc0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () ?? () g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1843854/+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 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Another error message from a flicker Sep 12 20:28:01 shadeball org.gnome.Shell.desktop[5959]: [6514:6514:0912/202801.632870:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1280 times! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+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 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
I ran "journalctl --user" after the last flicker and this is the output from the time around the flicker Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: [1:1:0912/201234.077664:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: [1:1:0912/201234.078033:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: [1:1:0912/201234.084532:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: [1:1:0912/201234.084847:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. I can post the full multi-day output of journalctl --user if that would be useful to you all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+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 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
** Changed in: mutter Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) Status in Mutter: Fix Released Status in gnome-settings-daemon package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to 3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome- tweaks are no longer applied to X11 applications when running in a Wayland session (I tried Firefox and Emacs). This seems to be because gsd-xsettings is not running. Known workarounds: • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or • use Xorg instead of Wayland; or • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.33.92-1ubuntu1 Uname: Linux 5.2.11-050211-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 6 17:24:02 2019 InstallationDate: Installed on 2016-02-19 (1295 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1843107/+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 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
** Changed in: evolution-data-server Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1843627 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() Status in evolution-data-server: Fix Released Status in evolution-data-server package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evolution/issues/616 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi PC (0x7f36355653ae) ok source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: tcache_get (tc_idx=) at malloc.c:2937 __GI___libc_malloc (bytes=32) at malloc.c:3051 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Hmm, I guess we should SRU the --fcf-protection=none change to the 19.04 and 18.04 kernels in that case. I will get this done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+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 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
I am running Ubuntu 19.04 with an XPS 13 9380 with Intel graphics. I installed the kernel mentioned above, and the problem is still occurring. I do a dmesg everytime I see it happen, but I don't see a consistent message every time it happens. I am more than willing to do any and all testing you all need, so if you think of something I could do to further investigate, let me know! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+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 1843132] Re: Cannot open .gif image (or is it .webm or .jpg format image? )
I just noticed that the image is shown right on my desktop (as a thumbnail icon), BUT cannot be shown in the EyeOfGnome. Why this difference? What the fudge is going on? Who makes the software? Do they use the library or different one? Kyndly A user -- 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/1843132 Title: Cannot open .gif image (or is it .webm or .jpg format image? ) Status in nautilus package in Ubuntu: New Bug description: Hello, I just noticed that Nautilus (or Ubuntu/GNOME cannot open all .jpg (or .gif) type images. The image has been attached. When I rename the image to .webm, then Nautilus/GNOME can open/show it. Sorry for the content of the image. (no intent to shock annyone). The image is shown right in Firefox and Chrome browsers. So GNOME should be able too. Kindly Moma ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 7 16:31:27 2019 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1390, 633)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-03-06 (184 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1843132/+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 1843793] Re: wpasupplicant 2.9 on eoan breaks wifi connections on arm64, reversion to 2.6-21ubuntu3.2 fixes.
Here is the wpa supplicant log, gathered as per: https://gist.github.com/wch/8305204#gistcomment-2477237 https://paste.ubuntu.com/p/Nm7G6STc22/ Note there are 3 sections. The first section starts with "wpa_supplicant v2.6" When I upgrade to 2.9 you can see this start with "wpa_supplicant v2.9" When I revert back to 2.6 you can see "wpa_supplicant v2.6" again. The wifi disconnects immediately after upgrading to 2.9, and I am able to reconnect to wifi immediately after downgrading to 2.6 using "sudo nmcli con up Manhattan". (That's the name of my network manager connection.) As to bisecting the changes between 2.6 and 2.9 That might take a while! -- 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/1843793 Title: wpasupplicant 2.9 on eoan breaks wifi connections on arm64, reversion to 2.6-21ubuntu3.2 fixes. Status in wpa package in Ubuntu: Incomplete Bug description: Summary: Connecting from a RPI4 running on arm64 eoan-server- preinstalled image with current "upstream" raspberry pi foundation kernel 4.19.71 to a WPA2 protected access point (Unifi nanoHD). The wifi connection drops out after ~ ten minutes. Reverting wpasupplicant to disco version keeps that from happening. Running on arm64 eoan build with kernel from raspberry pi folks ( 4.19.71-v8-g6de367fd7 ) on a rpi4. lsb_release -rd Description:Ubuntu Eoan Ermine (development branch) Release:19.10 With wpasupplicant 2.9, wifi comes up on boot, but then drops out shortly thereafter. Reverting wpasupplicant to 2.6-21ubuntu3.2 keeps the wifi connection from dropping out. wireless driver: [41385.982747] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [41386.000633] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 Logs using journalctl -xe NM_CONNECTION=f7f9f91f-001a-46b5-9acc- 038db489a0c8 + NM_DEVICE=wlan0 This is what I get with wpasupplicant 2.9: Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.2749] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/7) Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3032] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'ex Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3937] sup-iface[0x55b0b8faf0,wlan0]: supports 5 scan SSIDs Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3957] device (wlan0): supplicant interface state: starting -> ready Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3974] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys- Sep 12 12:09:55 rpi4 NetworkManager[25218]: [1568304595.9790] device (wlan0): supplicant interface state: ready -> scanning Sep 12 12:09:58 rpi4 NetworkManager[25218]: [1568304598.7770] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:01 rpi4 NetworkManager[25218]: [1568304601.9310] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:04 rpi4 NetworkManager[25218]: [1568304604.7332] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5964] device (wlan0): Activation: starting connection 'Manhattan' (f7f9f91f-001a-46b5-9acc-038db489a Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5975] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'manage Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6018] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6027] device (wlan0): Activation: (wifi) access point 'Manhattan' has security, but secrets are requ Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6028] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6115] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6126] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6139] device (wlan0): Activation: (wifi) connection 'Manhattan' has security, and secrets exist. No Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6690] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.4907] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:18 rpi4 NetworkManager[25218]:
[Desktop-packages] [Bug 1843760] Re: Please add a PPA to track only the Still Branch across major versions of LibreOffice
** Description changed: Upstream LibreOffice provides two branches of LibreOffice, the Fresh Branch (6.3.0) and the Still Branch (6.2.7). In Ubuntu there is a PPA that tracks the Fresh Branch (LibreOffice Fresh) and separate PPAs that track one major version of LO without crossing to a higher version in the same PPA. I suggest creating a new PPA that tracks only the Still Branch of LibreOffice. Meaning, today the latest version in the still branch is 6.2.6, the last release from the 6.2.x branch is 6.2.7 and its end of life is on November 30, 2019. Afterwards the still branch will track the 6.3.x branch from the 6.3.4 release and so on. So the PPA would have: - 6.2.6 ⇒ 6.2.7 (EOF) ⇒ 6.3.4 ⇒ 6.3.5 ⇒ 6.3.6 (EOF) ⇒ 6.4.4 ⇒ 6.4.5 ⇒ 6.4.6 ⇒ ... and so on. + 6.2.6 ⇒ 6.2.7 (EOL) ⇒ 6.3.4 ⇒ 6.3.5 ⇒ 6.3.6 (EOL) ⇒ 6.4.4 ⇒ 6.4.5 ⇒ 6.4.6 ⇒ ... and so on. The reason why I ask this is that almost always the first three releases of a new major version of LO are buggy and have regressions. The 6.3.0 version that I'm on now is buggy, but at the same time, newer versions of LO fix bugs and UI enhancements that probably will never be backported to older branches like the one in Bionic. So tracking only the Still Branch solves this issue especially for enterprise and school users. The Still Branch PPA would target only the Ubuntu LTS releases, Xenial and Bionic, because it doesn't make sense to target the short-lived releases. -- 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/1843760 Title: Please add a PPA to track only the Still Branch across major versions of LibreOffice Status in libreoffice package in Ubuntu: New Bug description: Upstream LibreOffice provides two branches of LibreOffice, the Fresh Branch (6.3.0) and the Still Branch (6.2.7). In Ubuntu there is a PPA that tracks the Fresh Branch (LibreOffice Fresh) and separate PPAs that track one major version of LO without crossing to a higher version in the same PPA. I suggest creating a new PPA that tracks only the Still Branch of LibreOffice. Meaning, today the latest version in the still branch is 6.2.6, the last release from the 6.2.x branch is 6.2.7 and its end of life is on November 30, 2019. Afterwards the still branch will track the 6.3.x branch from the 6.3.4 release and so on. So the PPA would have: 6.2.6 ⇒ 6.2.7 (EOL) ⇒ 6.3.4 ⇒ 6.3.5 ⇒ 6.3.6 (EOL) ⇒ 6.4.4 ⇒ 6.4.5 ⇒ 6.4.6 ⇒ ... and so on. The reason why I ask this is that almost always the first three releases of a new major version of LO are buggy and have regressions. The 6.3.0 version that I'm on now is buggy, but at the same time, newer versions of LO fix bugs and UI enhancements that probably will never be backported to older branches like the one in Bionic. So tracking only the Still Branch solves this issue especially for enterprise and school users. The Still Branch PPA would target only the Ubuntu LTS releases, Xenial and Bionic, because it doesn't make sense to target the short-lived releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1843760/+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 1843819] [NEW] Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50%
Public bug reported: When the volume is set to around 50% in PulseAudio (using the Ubuntu Sound preferences screen but cross-checked by simply viewing with pavucontrol) the alsamixer volume is set to 0%. I can see the volume rise quickly as the volume is raised past 50% in the Sound preferences screen. This occurs at least for the Logitech H600 USB device: Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset] The other audio devices behave "correctly" where 0% is silent and 100% is maximum volume. This confused me because the volume was set to 50% (I'll frequently reset headset volume to 30-50% to protect my ears) and thought audio was broken at first because I wasn't getting any sound at all. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1843819 Title: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50% Status in pulseaudio package in Ubuntu: New Bug description: When the volume is set to around 50% in PulseAudio (using the Ubuntu Sound preferences screen but cross-checked by simply viewing with pavucontrol) the alsamixer volume is set to 0%. I can see the volume rise quickly as the volume is raised past 50% in the Sound preferences screen. This occurs at least for the Logitech H600 USB device: Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset] The other audio devices behave "correctly" where 0% is silent and 100% is maximum volume. This confused me because the volume was set to 50% (I'll frequently reset headset volume to 30-50% to protect my ears) and thought audio was broken at first because I wasn't getting any sound at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1843819/+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 1843817] [NEW] Weird behavior of chaning input method on webpages
Public bug reported: I'm finding a weird behaviour of changing input method "only on webpages." I need to hit hotkey (Ctrl+Space) twice to trigger the change if my courser is in text boxes "on the page." If the courser is in URL bar or search bar or anywhere firebox window itself, this phenomenon doesn't exist. I am using gcin 2.8.9 and is switching between English and traditional Chinese. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 69.0+build2-0ubuntu0.18.04.1 Uname: Linux 5.2.5-050205-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yenyung_chang 1727 F pulseaudio BuildID: 20190828152820 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:53:04 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-03-26 (170 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.108 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=69.0/20190828152820 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1843817 Title: Weird behavior of chaning input method on webpages Status in firefox package in Ubuntu: New Bug description: I'm finding a weird behaviour of changing input method "only on webpages." I need to hit hotkey (Ctrl+Space) twice to trigger the change if my courser is in text boxes "on the page." If the courser is in URL bar or search bar or anywhere firebox window itself, this phenomenon doesn't exist. I am using gcin 2.8.9 and is switching between English and traditional Chinese. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 69.0+build2-0ubuntu0.18.04.1 Uname: Linux 5.2.5-050205-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yenyung_chang 1727 F pulseaudio BuildID: 20190828152820 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:53:04 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-03-26 (170 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.108 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=69.0/20190828152820 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10
[Desktop-packages] [Bug 1843764] Re: sane-backends ftbfs in eoan (armhf)
Indeed. That was merely input to the desktop team and not an objection to the bug. :) -- 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/1843764 Title: sane-backends ftbfs in eoan (armhf) Status in sane-backends package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441263700/buildlog_ubuntu-eoan-armhf .sane-backends_1.0.27-3.2ubuntu2_BUILDING.txt.gz dpkg-gensymbols: warning: debian/libsane/DEBIAN/symbols doesn't match completely debian/libsane.symbols.armhf --- debian/libsane.symbols.armhf (libsane_1.0.27_armhf) +++ dpkg-gensymbolsHF3hxU 2019-09-09 11:12:09.992951725 + @@ -4304,7 +4304,7 @@ sanei_constrain_value@Base 1.0.25 sanei_debug_msg@Base 1.0.25 sanei_debug_mustek@Base 1.0.25 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_debug_sanei_pa4s2@Base 1.0.25 @@ -5390,7 +5390,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25 sanei_pp_outb_data@Base 1.0.25 - sanei_pp_outb_epp@Base 1.0.25 +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 sanei_pp_release@Base 1.0.25 sanei_pp_set_datadir@Base 1.0.25 sanei_pp_setmode@Base 1.0.25 @@ -5452,59 +5452,6 @@ sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_init_debug@Base 1.0.25 -libsane-qcam.so.1 libsane #MINVER# - md5_buffer@Base 1.0.27 - md5_finish_ctx@Base 1.0.27 - md5_init_ctx@Base 1.0.27 - md5_process_block@Base 1.0.27 - md5_process_bytes@Base 1.0.27 - md5_read_ctx@Base 1.0.27 - md5_stream@Base 1.0.27 - sane_cancel@Base 1.0.25 - sane_close@Base 1.0.25 - sane_control_option@Base 1.0.25 - sane_exit@Base 1.0.25 - sane_get_devices@Base 1.0.25 - sane_get_option_descriptor@Base 1.0.25 - sane_get_parameters@Base 1.0.25 - sane_get_select_fd@Base 1.0.25 - sane_init@Base 1.0.25 - sane_open@Base 1.0.25 - sane_qcam_cancel@Base 1.0.25 - sane_qcam_close@Base 1.0.25 - sane_qcam_control_option@Base 1.0.25 - sane_qcam_exit@Base 1.0.25 - sane_qcam_get_devices@Base 1.0.25 - sane_qcam_get_option_descriptor@Base 1.0.25 - sane_qcam_get_parameters@Base 1.0.25 - sane_qcam_get_select_fd@Base 1.0.25 - sane_qcam_init@Base 1.0.25 - sane_qcam_open@Base 1.0.25 - sane_qcam_read@Base 1.0.25 - sane_qcam_set_io_mode@Base 1.0.25 - sane_qcam_start@Base 1.0.25 - sane_read@Base 1.0.25 - sane_set_io_mode@Base 1.0.25 - sane_start@Base 1.0.25 - sane_strstatus@Base 1.0.25 - sanei_check_value@Base 1.0.25 - sanei_config_get_paths@Base 1.0.25 - sanei_config_get_string@Base 1.0.25 - sanei_config_open@Base 1.0.25 - sanei_config_read@Base 1.0.25 - sanei_config_skip_whitespace@Base 1.0.25 - sanei_configure_attach@Base 1.0.25 - sanei_constrain_value@Base 1.0.25 - sanei_debug_msg@Base 1.0.25 - sanei_debug_qcam@Base 1.0.25 - sanei_debug_sanei_config@Base 1.0.25 - sanei_debug_sanei_debug@Base 1.0.25 - sanei_debug_sanei_pio@Base 1.0.25 - sanei_init_debug@Base 1.0.25 - sanei_pio_close@Base 1.0.25 - sanei_pio_open@Base 1.0.25 - sanei_pio_read@Base 1.0.25 - sanei_pio_write@Base 1.0.25 libsane-ricoh.so.1 libsane #MINVER# md5_buffer@Base 1.0.27 md5_finish_ctx@Base 1.0.27 @@ -7142,7 +7089,7 @@ sanei_constrain_value@Base 1.0.24 sanei_debug_dll@Base 1.0.25 sanei_debug_msg@Base 1.0.24 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_access@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.24 sanei_debug_sanei_debug@Base 1.0.24 @@ -7204,7 +7151,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25 sanei_pp_outb_data@Base 1.0.25 - sanei_pp_outb_epp@Base 1.0.25 +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 sanei_pp_release@Base 1.0.25 sanei_pp_set_datadir@Base 1.0.25 sanei_pp_setmode@Base 1.0.25 dh_makeshlibs: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1843764/+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 1843793] Re: wpasupplicant 2.9 on eoan breaks wifi connections on arm64, reversion to 2.6-21ubuntu3.2 fixes.
If we can find something in wpa's log (however one gets them) and an upstream fix for that, that would be great. If you can, I suggest you try to git bisect the upstream repository from 2.6 to 2.9 and see what commit breaks it. Please note that custom kernels are not supported, and we can't be sure it's a kernel or a wpa issue, so we'll probably have to wait for official rpi4 support if we can't figure out the cause and fix this way. ** Changed in: wpa (Ubuntu) Status: New => Incomplete -- 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/1843793 Title: wpasupplicant 2.9 on eoan breaks wifi connections on arm64, reversion to 2.6-21ubuntu3.2 fixes. Status in wpa package in Ubuntu: Incomplete Bug description: Summary: Connecting from a RPI4 running on arm64 eoan-server- preinstalled image with current "upstream" raspberry pi foundation kernel 4.19.71 to a WPA2 protected access point (Unifi nanoHD). The wifi connection drops out after ~ ten minutes. Reverting wpasupplicant to disco version keeps that from happening. Running on arm64 eoan build with kernel from raspberry pi folks ( 4.19.71-v8-g6de367fd7 ) on a rpi4. lsb_release -rd Description:Ubuntu Eoan Ermine (development branch) Release:19.10 With wpasupplicant 2.9, wifi comes up on boot, but then drops out shortly thereafter. Reverting wpasupplicant to 2.6-21ubuntu3.2 keeps the wifi connection from dropping out. wireless driver: [41385.982747] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [41386.000633] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 Logs using journalctl -xe NM_CONNECTION=f7f9f91f-001a-46b5-9acc- 038db489a0c8 + NM_DEVICE=wlan0 This is what I get with wpasupplicant 2.9: Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.2749] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/7) Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3032] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'ex Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3937] sup-iface[0x55b0b8faf0,wlan0]: supports 5 scan SSIDs Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3957] device (wlan0): supplicant interface state: starting -> ready Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3974] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys- Sep 12 12:09:55 rpi4 NetworkManager[25218]: [1568304595.9790] device (wlan0): supplicant interface state: ready -> scanning Sep 12 12:09:58 rpi4 NetworkManager[25218]: [1568304598.7770] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:01 rpi4 NetworkManager[25218]: [1568304601.9310] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:04 rpi4 NetworkManager[25218]: [1568304604.7332] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5964] device (wlan0): Activation: starting connection 'Manhattan' (f7f9f91f-001a-46b5-9acc-038db489a Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5975] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'manage Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6018] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6027] device (wlan0): Activation: (wifi) access point 'Manhattan' has security, but secrets are requ Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6028] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6115] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6126] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6139] device (wlan0): Activation: (wifi) connection 'Manhattan' has security, and secrets exist. No Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6690] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.4907] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.6313] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:21 rpi4 NetworkManager[25218]: [1568304621.4490] device (wlan0):
[Desktop-packages] [Bug 1843718] Re: I can change password of one administrator from other
Oh thank you for considering my question Sorry for the inconvenience caused -- 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/1843718 Title: I can change password of one administrator from other Status in gnome-control-center package in Ubuntu: New Bug description: I don't know even this is a bug.But I have to tell you that I can change the one administrator from other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1843718/+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 1843793] Re: wpasupplicant 2.9 on eoan breaks wifi connections on arm64, reversion to 2.6-21ubuntu3.2 fixes.
I'm not sure the NM log is very useful, a wpa supplicant log would probably be helpful, but no idea on gathering that. ** No longer affects: wpasupplicant (Ubuntu) -- 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/1843793 Title: wpasupplicant 2.9 on eoan breaks wifi connections on arm64, reversion to 2.6-21ubuntu3.2 fixes. Status in wpa package in Ubuntu: Incomplete Bug description: Summary: Connecting from a RPI4 running on arm64 eoan-server- preinstalled image with current "upstream" raspberry pi foundation kernel 4.19.71 to a WPA2 protected access point (Unifi nanoHD). The wifi connection drops out after ~ ten minutes. Reverting wpasupplicant to disco version keeps that from happening. Running on arm64 eoan build with kernel from raspberry pi folks ( 4.19.71-v8-g6de367fd7 ) on a rpi4. lsb_release -rd Description:Ubuntu Eoan Ermine (development branch) Release:19.10 With wpasupplicant 2.9, wifi comes up on boot, but then drops out shortly thereafter. Reverting wpasupplicant to 2.6-21ubuntu3.2 keeps the wifi connection from dropping out. wireless driver: [41385.982747] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [41386.000633] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 Logs using journalctl -xe NM_CONNECTION=f7f9f91f-001a-46b5-9acc- 038db489a0c8 + NM_DEVICE=wlan0 This is what I get with wpasupplicant 2.9: Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.2749] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/7) Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3032] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'ex Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3937] sup-iface[0x55b0b8faf0,wlan0]: supports 5 scan SSIDs Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3957] device (wlan0): supplicant interface state: starting -> ready Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3974] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys- Sep 12 12:09:55 rpi4 NetworkManager[25218]: [1568304595.9790] device (wlan0): supplicant interface state: ready -> scanning Sep 12 12:09:58 rpi4 NetworkManager[25218]: [1568304598.7770] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:01 rpi4 NetworkManager[25218]: [1568304601.9310] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:04 rpi4 NetworkManager[25218]: [1568304604.7332] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5964] device (wlan0): Activation: starting connection 'Manhattan' (f7f9f91f-001a-46b5-9acc-038db489a Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5975] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'manage Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6018] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6027] device (wlan0): Activation: (wifi) access point 'Manhattan' has security, but secrets are requ Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6028] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6115] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6126] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6139] device (wlan0): Activation: (wifi) connection 'Manhattan' has security, and secrets exist. No Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6690] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.4907] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.6313] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:21 rpi4 NetworkManager[25218]: [1568304621.4490] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:21 rpi4 NetworkManager[25218]: [1568304621.9910] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:24 rpi4 NetworkManager[25218]: [1568304624.8102] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12
[Desktop-packages] [Bug 1843718] Re: I can change password of one administrator from other
AFAIK that's not a bug. As a superuser you can do basically everything. But to get a second opinion specifically for the settings GUI, I change the affected package to gnome-control-center. ** Package changed: ubuntu-docs (Ubuntu) => gnome-control-center (Ubuntu) -- 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/1843718 Title: I can change password of one administrator from other Status in gnome-control-center package in Ubuntu: New Bug description: I don't know even this is a bug.But I have to tell you that I can change the one administrator from other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1843718/+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 1843718] [NEW] I can change password of one administrator from other
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: I don't know even this is a bug.But I have to tell you that I can change the one administrator from other user. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- I can change password of one administrator from other https://bugs.launchpad.net/bugs/1843718 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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 1843793] Re: wpasupplicant 2.29 breaks wifi connections, reversion to 2.6-21ubuntu3.2 fixes.
** Description changed: Running on arm64 eoan build with kernel from raspberry pi folks ( 4.19.71-v8-g6de367fd7 ) on a rpi4. lsb_release -rd Description:Ubuntu Eoan Ermine (development branch) Release:19.10 - - With wpasupplicant 2.29, wifi comes up on boot, but then drops out shortly thereafter. + With wpasupplicant 2.9, wifi comes up on boot, but then drops out + shortly thereafter. Reverting wpasupplicant to 2.6-21ubuntu3.2 keeps the wifi connection from dropping out. Have "wifi.scan-rand-mac-address=no" set in /etc/NetworkManager/NetworkManager.conf as per many troubleshooting threads. wireless driver: [41385.982747] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [41386.000633] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 + Logs using journalctl -xe NM_CONNECTION=f7f9f91f-001a-46b5-9acc- + 038db489a0c8 + NM_DEVICE=wlan0 - Logs using journalctl -xe NM_CONNECTION=f7f9f91f-001a-46b5-9acc-038db489a0c8 + NM_DEVICE=wlan0 - - This is what I get with wpasupplicant 2.29: + This is what I get with wpasupplicant 2.9: Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.2749] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/7) Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3032] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'ex Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3937] sup-iface[0x55b0b8faf0,wlan0]: supports 5 scan SSIDs Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3957] device (wlan0): supplicant interface state: starting -> ready Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3974] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys- Sep 12 12:09:55 rpi4 NetworkManager[25218]: [1568304595.9790] device (wlan0): supplicant interface state: ready -> scanning Sep 12 12:09:58 rpi4 NetworkManager[25218]: [1568304598.7770] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:01 rpi4 NetworkManager[25218]: [1568304601.9310] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:04 rpi4 NetworkManager[25218]: [1568304604.7332] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5964] device (wlan0): Activation: starting connection 'Manhattan' (f7f9f91f-001a-46b5-9acc-038db489a Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5975] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'manage Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6018] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6027] device (wlan0): Activation: (wifi) access point 'Manhattan' has security, but secrets are requ Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6028] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6115] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6126] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6139] device (wlan0): Activation: (wifi) connection 'Manhattan' has security, and secrets exist. No Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6690] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.4907] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.6313] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:21 rpi4 NetworkManager[25218]: [1568304621.4490] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:21 rpi4 NetworkManager[25218]: [1568304621.9910] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:24 rpi4 NetworkManager[25218]: [1568304624.8102] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:25 rpi4 NetworkManager[25218]: [1568304625.8531] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:28 rpi4 NetworkManager[25218]: [1568304628.6735] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:28 rpi4 NetworkManager[25218]: [1568304628.9667] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:40 rpi4
[Desktop-packages] [Bug 1843764] Re: sane-backends ftbfs in eoan (armhf)
yes, and now it ftbfs. https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20190906-eoan.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1843764 Title: sane-backends ftbfs in eoan (armhf) Status in sane-backends package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441263700/buildlog_ubuntu-eoan-armhf .sane-backends_1.0.27-3.2ubuntu2_BUILDING.txt.gz dpkg-gensymbols: warning: debian/libsane/DEBIAN/symbols doesn't match completely debian/libsane.symbols.armhf --- debian/libsane.symbols.armhf (libsane_1.0.27_armhf) +++ dpkg-gensymbolsHF3hxU 2019-09-09 11:12:09.992951725 + @@ -4304,7 +4304,7 @@ sanei_constrain_value@Base 1.0.25 sanei_debug_msg@Base 1.0.25 sanei_debug_mustek@Base 1.0.25 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_debug_sanei_pa4s2@Base 1.0.25 @@ -5390,7 +5390,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25 sanei_pp_outb_data@Base 1.0.25 - sanei_pp_outb_epp@Base 1.0.25 +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 sanei_pp_release@Base 1.0.25 sanei_pp_set_datadir@Base 1.0.25 sanei_pp_setmode@Base 1.0.25 @@ -5452,59 +5452,6 @@ sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_init_debug@Base 1.0.25 -libsane-qcam.so.1 libsane #MINVER# - md5_buffer@Base 1.0.27 - md5_finish_ctx@Base 1.0.27 - md5_init_ctx@Base 1.0.27 - md5_process_block@Base 1.0.27 - md5_process_bytes@Base 1.0.27 - md5_read_ctx@Base 1.0.27 - md5_stream@Base 1.0.27 - sane_cancel@Base 1.0.25 - sane_close@Base 1.0.25 - sane_control_option@Base 1.0.25 - sane_exit@Base 1.0.25 - sane_get_devices@Base 1.0.25 - sane_get_option_descriptor@Base 1.0.25 - sane_get_parameters@Base 1.0.25 - sane_get_select_fd@Base 1.0.25 - sane_init@Base 1.0.25 - sane_open@Base 1.0.25 - sane_qcam_cancel@Base 1.0.25 - sane_qcam_close@Base 1.0.25 - sane_qcam_control_option@Base 1.0.25 - sane_qcam_exit@Base 1.0.25 - sane_qcam_get_devices@Base 1.0.25 - sane_qcam_get_option_descriptor@Base 1.0.25 - sane_qcam_get_parameters@Base 1.0.25 - sane_qcam_get_select_fd@Base 1.0.25 - sane_qcam_init@Base 1.0.25 - sane_qcam_open@Base 1.0.25 - sane_qcam_read@Base 1.0.25 - sane_qcam_set_io_mode@Base 1.0.25 - sane_qcam_start@Base 1.0.25 - sane_read@Base 1.0.25 - sane_set_io_mode@Base 1.0.25 - sane_start@Base 1.0.25 - sane_strstatus@Base 1.0.25 - sanei_check_value@Base 1.0.25 - sanei_config_get_paths@Base 1.0.25 - sanei_config_get_string@Base 1.0.25 - sanei_config_open@Base 1.0.25 - sanei_config_read@Base 1.0.25 - sanei_config_skip_whitespace@Base 1.0.25 - sanei_configure_attach@Base 1.0.25 - sanei_constrain_value@Base 1.0.25 - sanei_debug_msg@Base 1.0.25 - sanei_debug_qcam@Base 1.0.25 - sanei_debug_sanei_config@Base 1.0.25 - sanei_debug_sanei_debug@Base 1.0.25 - sanei_debug_sanei_pio@Base 1.0.25 - sanei_init_debug@Base 1.0.25 - sanei_pio_close@Base 1.0.25 - sanei_pio_open@Base 1.0.25 - sanei_pio_read@Base 1.0.25 - sanei_pio_write@Base 1.0.25 libsane-ricoh.so.1 libsane #MINVER# md5_buffer@Base 1.0.27 md5_finish_ctx@Base 1.0.27 @@ -7142,7 +7089,7 @@ sanei_constrain_value@Base 1.0.24 sanei_debug_dll@Base 1.0.25 sanei_debug_msg@Base 1.0.24 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_access@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.24 sanei_debug_sanei_debug@Base 1.0.24 @@ -7204,7 +7151,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25 sanei_pp_outb_data@Base 1.0.25 - sanei_pp_outb_epp@Base 1.0.25 +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 sanei_pp_release@Base 1.0.25 sanei_pp_set_datadir@Base 1.0.25 sanei_pp_setmode@Base 1.0.25 dh_makeshlibs: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1843764/+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 1843797] [NEW] Bogus error message when opening or extracting a RAR archive if unrar is not installed
Public bug reported: Description The bug on the latest version of File Roller on Ubuntu 19.10 Eoan Ermine has been confusing users about getting bogus and confusing error messages like one of them containing invalid characters if unrar is not installed on the system. I have downloaded a .rar file to my Downloads folder, and tried to extract it by Right click > Extract Here without unrar, but got bogus error messages like invalid characters, "Fatal Error", or "Extraction not performed". This will continue until I have installed unrar, which made the extraction work properly. Not only does it happen on extraction, but also happens on opening archives, which makes rar files useless until the utility is installed. Expected action: The error message should say anything about unrar not being installed, and possibly provide a confirmation if they want to install it or not. Actual action: Users are confused with bogus error messages until unrar is installed. To be even more clear, I have provided screenshots in the attachments. Ubuntu version: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 File Roller version: file-roller: Installed: 3.32.1-1 Candidate: 3.32.1-1 Version table: *** 3.32.1-1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: file-roller 3.32.1-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 19:44:42 2019 InstallationDate: Installed on 2019-07-21 (53 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Bogus1.png" https://bugs.launchpad.net/bugs/1843797/+attachment/5288364/+files/Bogus1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1843797 Title: Bogus error message when opening or extracting a RAR archive if unrar is not installed Status in file-roller package in Ubuntu: New Bug description: Description The bug on the latest version of File Roller on Ubuntu 19.10 Eoan Ermine has been confusing users about getting bogus and confusing error messages like one of them containing invalid characters if unrar is not installed on the system. I have downloaded a .rar file to my Downloads folder, and tried to extract it by Right click > Extract Here without unrar, but got bogus error messages like invalid characters, "Fatal Error", or "Extraction not performed". This will continue until I have installed unrar, which made the extraction work properly. Not only does it happen on extraction, but also happens on opening archives, which makes rar files useless until the utility is installed. Expected action: The error message should say anything about unrar not being installed, and possibly provide a confirmation if they want to install it or not. Actual action: Users are confused with bogus error messages until unrar is installed. To be even more clear, I have provided screenshots in the attachments. Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 File Roller version: file-roller: Installed: 3.32.1-1 Candidate: 3.32.1-1 Version table: *** 3.32.1-1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: file-roller 3.32.1-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 19:44:42 2019 InstallationDate: Installed on 2019-07-21 (53 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1843797/+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 1843797] Re: Bogus error message when opening or extracting a RAR archive if unrar is not installed
** Attachment added: "Bogus3.png" https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1843797/+attachment/5288369/+files/Bogus3.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1843797 Title: Bogus error message when opening or extracting a RAR archive if unrar is not installed Status in file-roller package in Ubuntu: New Bug description: Description The bug on the latest version of File Roller on Ubuntu 19.10 Eoan Ermine has been confusing users about getting bogus and confusing error messages like one of them containing invalid characters if unrar is not installed on the system. I have downloaded a .rar file to my Downloads folder, and tried to extract it by Right click > Extract Here without unrar, but got bogus error messages like invalid characters, "Fatal Error", or "Extraction not performed". This will continue until I have installed unrar, which made the extraction work properly. Not only does it happen on extraction, but also happens on opening archives, which makes rar files useless until the utility is installed. Expected action: The error message should say anything about unrar not being installed, and possibly provide a confirmation if they want to install it or not. Actual action: Users are confused with bogus error messages until unrar is installed. To be even more clear, I have provided screenshots in the attachments. Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 File Roller version: file-roller: Installed: 3.32.1-1 Candidate: 3.32.1-1 Version table: *** 3.32.1-1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: file-roller 3.32.1-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 19:44:42 2019 InstallationDate: Installed on 2019-07-21 (53 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1843797/+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 1843797] Re: Bogus error message when opening or extracting a RAR archive if unrar is not installed
** Attachment added: "Bogus2.png" https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1843797/+attachment/5288368/+files/Bogus2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1843797 Title: Bogus error message when opening or extracting a RAR archive if unrar is not installed Status in file-roller package in Ubuntu: New Bug description: Description The bug on the latest version of File Roller on Ubuntu 19.10 Eoan Ermine has been confusing users about getting bogus and confusing error messages like one of them containing invalid characters if unrar is not installed on the system. I have downloaded a .rar file to my Downloads folder, and tried to extract it by Right click > Extract Here without unrar, but got bogus error messages like invalid characters, "Fatal Error", or "Extraction not performed". This will continue until I have installed unrar, which made the extraction work properly. Not only does it happen on extraction, but also happens on opening archives, which makes rar files useless until the utility is installed. Expected action: The error message should say anything about unrar not being installed, and possibly provide a confirmation if they want to install it or not. Actual action: Users are confused with bogus error messages until unrar is installed. To be even more clear, I have provided screenshots in the attachments. Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 File Roller version: file-roller: Installed: 3.32.1-1 Candidate: 3.32.1-1 Version table: *** 3.32.1-1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: file-roller 3.32.1-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 19:44:42 2019 InstallationDate: Installed on 2019-07-21 (53 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1843797/+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 1843798] [NEW] 19.10 Eoan default wallpapers
Public bug reported: Attached will be the Eoan default wallpapers. One in colour, one in black and white. Both 4096 x 2304. ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Assignee: Will Cooke (willcooke) Status: New ** Changed in: ubuntu-wallpapers (Ubuntu) Assignee: (unassigned) => Will Cooke (willcooke) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1843798 Title: 19.10 Eoan default wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Attached will be the Eoan default wallpapers. One in colour, one in black and white. Both 4096 x 2304. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1843798/+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 1843793] [NEW] wpasupplicant 2.29 breaks wifi connections, reversion to 2.6-21ubuntu3.2 fixes.
Public bug reported: Running on arm64 eoan build with kernel from raspberry pi folks ( 4.19.71-v8-g6de367fd7 ) on a rpi4. lsb_release -rd Description:Ubuntu Eoan Ermine (development branch) Release:19.10 With wpasupplicant 2.29, wifi comes up on boot, but then drops out shortly thereafter. Reverting wpasupplicant to 2.6-21ubuntu3.2 keeps the wifi connection from dropping out. Have "wifi.scan-rand-mac-address=no" set in /etc/NetworkManager/NetworkManager.conf as per many troubleshooting threads. wireless driver: [41385.982747] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [41386.000633] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 Logs using journalctl -xe NM_CONNECTION=f7f9f91f-001a-46b5-9acc-038db489a0c8 + NM_DEVICE=wlan0 This is what I get with wpasupplicant 2.29: Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.2749] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/7) Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3032] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'ex Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3937] sup-iface[0x55b0b8faf0,wlan0]: supports 5 scan SSIDs Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3957] device (wlan0): supplicant interface state: starting -> ready Sep 12 12:09:49 rpi4 NetworkManager[25218]: [1568304589.3974] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys- Sep 12 12:09:55 rpi4 NetworkManager[25218]: [1568304595.9790] device (wlan0): supplicant interface state: ready -> scanning Sep 12 12:09:58 rpi4 NetworkManager[25218]: [1568304598.7770] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:01 rpi4 NetworkManager[25218]: [1568304601.9310] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:04 rpi4 NetworkManager[25218]: [1568304604.7332] device (wlan0): supplicant interface state: scanning -> inactive Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5964] device (wlan0): Activation: starting connection 'Manhattan' (f7f9f91f-001a-46b5-9acc-038db489a Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.5975] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'manage Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6018] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6027] device (wlan0): Activation: (wifi) access point 'Manhattan' has security, but secrets are requ Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6028] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6115] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6126] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6139] device (wlan0): Activation: (wifi) connection 'Manhattan' has security, and secrets exist. No Sep 12 12:10:15 rpi4 NetworkManager[25218]: [1568304615.6690] device (wlan0): supplicant interface state: inactive -> scanning Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.4907] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:18 rpi4 NetworkManager[25218]: [1568304618.6313] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:21 rpi4 NetworkManager[25218]: [1568304621.4490] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:21 rpi4 NetworkManager[25218]: [1568304621.9910] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:24 rpi4 NetworkManager[25218]: [1568304624.8102] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:25 rpi4 NetworkManager[25218]: [1568304625.8531] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:28 rpi4 NetworkManager[25218]: [1568304628.6735] device (wlan0): supplicant interface state: scanning -> disconnected Sep 12 12:10:28 rpi4 NetworkManager[25218]: [1568304628.9667] device (wlan0): supplicant interface state: disconnected -> scanning Sep 12 12:10:40 rpi4 NetworkManager[25218]: [1568304640.9264] device (wlan0): Activation: (wifi) association took too long, failing activation Sep 12 12:10:40 rpi4 NetworkManager[25218]: [1568304640.9266] device (wlan0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'man Sep 12 12:10:40 rpi4 NetworkManager[25218]:
[Desktop-packages] [Bug 1843796] [NEW] ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available
Public bug reported: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux- modules-nvidia package is available. Currently, we do not deal with this kind of failure i.e. when no linux- modules-nvidia package is available for the kernel in use. If no such package can be found, we need to at least attempt installing the relevant DKMS package, so that users get the required kernel modules. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1843796 Title: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available. Currently, we do not deal with this kind of failure i.e. when no linux-modules-nvidia package is available for the kernel in use. If no such package can be found, we need to at least attempt installing the relevant DKMS package, so that users get the required kernel modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1843796/+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 1843764] Re: sane-backends ftbfs in eoan (armhf)
Notes: - armhf built successfully on eoan from the same source as late as 2019-08-20 - No Ubuntu/Debian delta wrt debian/libsane.symbols.armhf -- 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/1843764 Title: sane-backends ftbfs in eoan (armhf) Status in sane-backends package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441263700/buildlog_ubuntu-eoan-armhf .sane-backends_1.0.27-3.2ubuntu2_BUILDING.txt.gz dpkg-gensymbols: warning: debian/libsane/DEBIAN/symbols doesn't match completely debian/libsane.symbols.armhf --- debian/libsane.symbols.armhf (libsane_1.0.27_armhf) +++ dpkg-gensymbolsHF3hxU 2019-09-09 11:12:09.992951725 + @@ -4304,7 +4304,7 @@ sanei_constrain_value@Base 1.0.25 sanei_debug_msg@Base 1.0.25 sanei_debug_mustek@Base 1.0.25 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_debug_sanei_pa4s2@Base 1.0.25 @@ -5390,7 +5390,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25 sanei_pp_outb_data@Base 1.0.25 - sanei_pp_outb_epp@Base 1.0.25 +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 sanei_pp_release@Base 1.0.25 sanei_pp_set_datadir@Base 1.0.25 sanei_pp_setmode@Base 1.0.25 @@ -5452,59 +5452,6 @@ sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_init_debug@Base 1.0.25 -libsane-qcam.so.1 libsane #MINVER# - md5_buffer@Base 1.0.27 - md5_finish_ctx@Base 1.0.27 - md5_init_ctx@Base 1.0.27 - md5_process_block@Base 1.0.27 - md5_process_bytes@Base 1.0.27 - md5_read_ctx@Base 1.0.27 - md5_stream@Base 1.0.27 - sane_cancel@Base 1.0.25 - sane_close@Base 1.0.25 - sane_control_option@Base 1.0.25 - sane_exit@Base 1.0.25 - sane_get_devices@Base 1.0.25 - sane_get_option_descriptor@Base 1.0.25 - sane_get_parameters@Base 1.0.25 - sane_get_select_fd@Base 1.0.25 - sane_init@Base 1.0.25 - sane_open@Base 1.0.25 - sane_qcam_cancel@Base 1.0.25 - sane_qcam_close@Base 1.0.25 - sane_qcam_control_option@Base 1.0.25 - sane_qcam_exit@Base 1.0.25 - sane_qcam_get_devices@Base 1.0.25 - sane_qcam_get_option_descriptor@Base 1.0.25 - sane_qcam_get_parameters@Base 1.0.25 - sane_qcam_get_select_fd@Base 1.0.25 - sane_qcam_init@Base 1.0.25 - sane_qcam_open@Base 1.0.25 - sane_qcam_read@Base 1.0.25 - sane_qcam_set_io_mode@Base 1.0.25 - sane_qcam_start@Base 1.0.25 - sane_read@Base 1.0.25 - sane_set_io_mode@Base 1.0.25 - sane_start@Base 1.0.25 - sane_strstatus@Base 1.0.25 - sanei_check_value@Base 1.0.25 - sanei_config_get_paths@Base 1.0.25 - sanei_config_get_string@Base 1.0.25 - sanei_config_open@Base 1.0.25 - sanei_config_read@Base 1.0.25 - sanei_config_skip_whitespace@Base 1.0.25 - sanei_configure_attach@Base 1.0.25 - sanei_constrain_value@Base 1.0.25 - sanei_debug_msg@Base 1.0.25 - sanei_debug_qcam@Base 1.0.25 - sanei_debug_sanei_config@Base 1.0.25 - sanei_debug_sanei_debug@Base 1.0.25 - sanei_debug_sanei_pio@Base 1.0.25 - sanei_init_debug@Base 1.0.25 - sanei_pio_close@Base 1.0.25 - sanei_pio_open@Base 1.0.25 - sanei_pio_read@Base 1.0.25 - sanei_pio_write@Base 1.0.25 libsane-ricoh.so.1 libsane #MINVER# md5_buffer@Base 1.0.27 md5_finish_ctx@Base 1.0.27 @@ -7142,7 +7089,7 @@ sanei_constrain_value@Base 1.0.24 sanei_debug_dll@Base 1.0.25 sanei_debug_msg@Base 1.0.24 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_access@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.24 sanei_debug_sanei_debug@Base 1.0.24 @@ -7204,7 +7151,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25 sanei_pp_outb_data@Base 1.0.25 - sanei_pp_outb_epp@Base 1.0.25 +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 sanei_pp_release@Base 1.0.25 sanei_pp_set_datadir@Base 1.0.25 sanei_pp_setmode@Base 1.0.25 dh_makeshlibs: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1843764/+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 1843419] Re: gnome-shell's alt-f2 r (refresh) kills non-gnome apps
Refreshing gnome-shell settings using tweaks allows me to refresh gnome- shell (alt-f2 r enter) without it killing Firefox, etc. Killing gnome- shell manually, through terminal, though still kills Firefox, but not gnome-terminal. -- 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/1843419 Title: gnome-shell's alt-f2 r (refresh) kills non-gnome apps Status in gnome-shell package in Ubuntu: Confirmed Bug description: Pressing alt-f2 then r refreshes gnome-shell as expected (though now windows have black borders) but it kills apps like Firefox, but not Feedreader, nautilus, nor, gnome-terminal (those are what I tested). I expect that it should not kill any apps like in the old gnome-shell. This is useful since when gnome-shell hangs, I kill it and it refreshes. Now I can't do that without killing the other apps also. Thank you for looking into this bug. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 10 19:10:52 2019 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (1442 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-26 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843419/+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 1817428] Re: gnome-control-center applications tab would be nice if it has search
With gnome-control-center 3.34.0.1 I see there's a search button now. ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- 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/1817428 Title: gnome-control-center applications tab would be nice if it has search Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Hello, I noticed that the gnome-control-center Applications tab doesn't have search. It would easier to find the application you want to modify if it had a search feature. Thank you for taking time in implementing this feature. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu3 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 24 02:46:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (1244 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-02-16 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817428/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Just for the record, this still breaks upgrades from 19.04 (I updated today) because dkms tries to build things (nvidia and virtualbox here) for the 19.04 kernel and fails. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+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 1843764] [NEW] sane-backends ftbfs in eoan (armhf)
Public bug reported: https://launchpadlibrarian.net/441263700/buildlog_ubuntu-eoan-armhf .sane-backends_1.0.27-3.2ubuntu2_BUILDING.txt.gz dpkg-gensymbols: warning: debian/libsane/DEBIAN/symbols doesn't match completely debian/libsane.symbols.armhf --- debian/libsane.symbols.armhf (libsane_1.0.27_armhf) +++ dpkg-gensymbolsHF3hxU 2019-09-09 11:12:09.992951725 + @@ -4304,7 +4304,7 @@ sanei_constrain_value@Base 1.0.25 sanei_debug_msg@Base 1.0.25 sanei_debug_mustek@Base 1.0.25 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_debug_sanei_pa4s2@Base 1.0.25 @@ -5390,7 +5390,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25 sanei_pp_outb_data@Base 1.0.25 - sanei_pp_outb_epp@Base 1.0.25 +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 sanei_pp_release@Base 1.0.25 sanei_pp_set_datadir@Base 1.0.25 sanei_pp_setmode@Base 1.0.25 @@ -5452,59 +5452,6 @@ sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_init_debug@Base 1.0.25 -libsane-qcam.so.1 libsane #MINVER# - md5_buffer@Base 1.0.27 - md5_finish_ctx@Base 1.0.27 - md5_init_ctx@Base 1.0.27 - md5_process_block@Base 1.0.27 - md5_process_bytes@Base 1.0.27 - md5_read_ctx@Base 1.0.27 - md5_stream@Base 1.0.27 - sane_cancel@Base 1.0.25 - sane_close@Base 1.0.25 - sane_control_option@Base 1.0.25 - sane_exit@Base 1.0.25 - sane_get_devices@Base 1.0.25 - sane_get_option_descriptor@Base 1.0.25 - sane_get_parameters@Base 1.0.25 - sane_get_select_fd@Base 1.0.25 - sane_init@Base 1.0.25 - sane_open@Base 1.0.25 - sane_qcam_cancel@Base 1.0.25 - sane_qcam_close@Base 1.0.25 - sane_qcam_control_option@Base 1.0.25 - sane_qcam_exit@Base 1.0.25 - sane_qcam_get_devices@Base 1.0.25 - sane_qcam_get_option_descriptor@Base 1.0.25 - sane_qcam_get_parameters@Base 1.0.25 - sane_qcam_get_select_fd@Base 1.0.25 - sane_qcam_init@Base 1.0.25 - sane_qcam_open@Base 1.0.25 - sane_qcam_read@Base 1.0.25 - sane_qcam_set_io_mode@Base 1.0.25 - sane_qcam_start@Base 1.0.25 - sane_read@Base 1.0.25 - sane_set_io_mode@Base 1.0.25 - sane_start@Base 1.0.25 - sane_strstatus@Base 1.0.25 - sanei_check_value@Base 1.0.25 - sanei_config_get_paths@Base 1.0.25 - sanei_config_get_string@Base 1.0.25 - sanei_config_open@Base 1.0.25 - sanei_config_read@Base 1.0.25 - sanei_config_skip_whitespace@Base 1.0.25 - sanei_configure_attach@Base 1.0.25 - sanei_constrain_value@Base 1.0.25 - sanei_debug_msg@Base 1.0.25 - sanei_debug_qcam@Base 1.0.25 - sanei_debug_sanei_config@Base 1.0.25 - sanei_debug_sanei_debug@Base 1.0.25 - sanei_debug_sanei_pio@Base 1.0.25 - sanei_init_debug@Base 1.0.25 - sanei_pio_close@Base 1.0.25 - sanei_pio_open@Base 1.0.25 - sanei_pio_read@Base 1.0.25 - sanei_pio_write@Base 1.0.25 libsane-ricoh.so.1 libsane #MINVER# md5_buffer@Base 1.0.27 md5_finish_ctx@Base 1.0.27 @@ -7142,7 +7089,7 @@ sanei_constrain_value@Base 1.0.24 sanei_debug_dll@Base 1.0.25 sanei_debug_msg@Base 1.0.24 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_access@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.24 sanei_debug_sanei_debug@Base 1.0.24 @@ -7204,7 +7151,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25 sanei_pp_outb_data@Base 1.0.25 - sanei_pp_outb_epp@Base 1.0.25 +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 sanei_pp_release@Base 1.0.25 sanei_pp_set_datadir@Base 1.0.25 sanei_pp_setmode@Base 1.0.25 dh_makeshlibs: failing due to earlier errors ** Affects: sane-backends (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ee-incoming ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed ** Changed in: sane-backends (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ee-incoming -- 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/1843764 Title: sane-backends ftbfs in eoan (armhf) Status in sane-backends package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441263700/buildlog_ubuntu-eoan-armhf .sane-backends_1.0.27-3.2ubuntu2_BUILDING.txt.gz dpkg-gensymbols: warning: debian/libsane/DEBIAN/symbols doesn't match completely debian/libsane.symbols.armhf --- debian/libsane.symbols.armhf (libsane_1.0.27_armhf) +++ dpkg-gensymbolsHF3hxU 2019-09-09 11:12:09.992951725 + @@ -4304,7 +4304,7 @@ sanei_constrain_value@Base 1.0.25 sanei_debug_msg@Base 1.0.25 sanei_debug_mustek@Base 1.0.25 - sanei_debug_sanei_ab306@Base 1.0.25 +#MISSING: 1.0.27# sanei_debug_sanei_ab306@Base 1.0.25 sanei_debug_sanei_config@Base 1.0.25 sanei_debug_sanei_debug@Base 1.0.25 sanei_debug_sanei_pa4s2@Base 1.0.25 @@ -5390,7 +5390,7 @@ sanei_pp_outb_addr@Base 1.0.25 sanei_pp_outb_ctrl@Base 1.0.25
[Desktop-packages] [Bug 1843763] [NEW] [SRU] libreoffice 6.2.7 for disco
Public bug reported: [Impact] * LibreOffice 6.2.7 is in its seventh bugfix release of the 6.2 line. For a list of fixed bugs compared to 6.2.6 see: https://wiki.documentfoundation.org/Releases/6.2.7/RC1#List_of_fixed_bugs (that's a total of 32 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 32 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: High Assignee: Marcus Tomlinson (marcustomlinson) Status: New ** Affects: libreoffice-l10n (Ubuntu) Importance: High Assignee: Marcus Tomlinson (marcustomlinson) Status: New ** Affects: libreoffice (Ubuntu Disco) Importance: High Assignee: Marcus Tomlinson (marcustomlinson) Status: New ** Affects: libreoffice-l10n (Ubuntu Disco) Importance: High Assignee: Marcus Tomlinson (marcustomlinson) Status: New ** Also affects: libreoffice-l10n (Ubuntu) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: libreoffice-l10n (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice (Ubuntu Disco) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice-l10n (Ubuntu Disco) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice-l10n (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Disco) Importance: Undecided => High ** Changed in: libreoffice-l10n (Ubuntu) Importance: Undecided => High ** Changed in: libreoffice-l10n (Ubuntu Disco) Importance: Undecided => High -- 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/1843763 Title: [SRU] libreoffice 6.2.7 for disco Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in libreoffice source package in Disco: New Status in libreoffice-l10n source package in Disco: New Bug description: [Impact] * LibreOffice 6.2.7 is in its seventh bugfix release of the 6.2 line. For a list of fixed bugs compared to 6.2.6 see: https://wiki.documentfoundation.org/Releases/6.2.7/RC1#List_of_fixed_bugs (that's a total of 32 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 32 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1843763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1843760] [NEW] Please add a PPA to track only the Still Branch across major versions of LibreOffice
Public bug reported: Upstream LibreOffice provides two branches of LibreOffice, the Fresh Branch (6.3.0) and the Still Branch (6.2.7). In Ubuntu there is a PPA that tracks the Fresh Branch (LibreOffice Fresh) and separate PPAs that track one major version of LO without crossing to a higher version in the same PPA. I suggest creating a new PPA that tracks only the Still Branch of LibreOffice. Meaning, today the latest version in the still branch is 6.2.6, the last release from the 6.2.x branch is 6.2.7 and its end of life is on November 30, 2019. Afterwards the still branch will track the 6.3.x branch from the 6.3.4 release and so on. So the PPA would have: 6.2.6 ⇒ 6.2.7 (EOF) ⇒ 6.3.4 ⇒ 6.3.5 ⇒ 6.3.6 (EOF) ⇒ 6.4.4 ⇒ 6.4.5 ⇒ 6.4.6 ⇒ ... and so on. The reason why I ask this is that almost always the first three releases of a new major version of LO are buggy and have regressions. The 6.3.0 version that I'm on now is buggy, but at the same time, newer versions of LO fix bugs and UI enhancements that probably will never be backported to older branches like the one in Bionic. So tracking only the Still Branch solves this issue especially for enterprise and school users. The Still Branch PPA would target only the Ubuntu LTS releases, Xenial and Bionic, because it doesn't make sense to target the short-lived releases. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1843760 Title: Please add a PPA to track only the Still Branch across major versions of LibreOffice Status in libreoffice package in Ubuntu: New Bug description: Upstream LibreOffice provides two branches of LibreOffice, the Fresh Branch (6.3.0) and the Still Branch (6.2.7). In Ubuntu there is a PPA that tracks the Fresh Branch (LibreOffice Fresh) and separate PPAs that track one major version of LO without crossing to a higher version in the same PPA. I suggest creating a new PPA that tracks only the Still Branch of LibreOffice. Meaning, today the latest version in the still branch is 6.2.6, the last release from the 6.2.x branch is 6.2.7 and its end of life is on November 30, 2019. Afterwards the still branch will track the 6.3.x branch from the 6.3.4 release and so on. So the PPA would have: 6.2.6 ⇒ 6.2.7 (EOF) ⇒ 6.3.4 ⇒ 6.3.5 ⇒ 6.3.6 (EOF) ⇒ 6.4.4 ⇒ 6.4.5 ⇒ 6.4.6 ⇒ ... and so on. The reason why I ask this is that almost always the first three releases of a new major version of LO are buggy and have regressions. The 6.3.0 version that I'm on now is buggy, but at the same time, newer versions of LO fix bugs and UI enhancements that probably will never be backported to older branches like the one in Bionic. So tracking only the Still Branch solves this issue especially for enterprise and school users. The Still Branch PPA would target only the Ubuntu LTS releases, Xenial and Bionic, because it doesn't make sense to target the short-lived releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1843760/+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 1843737] Re: gnome-keyring ftbfs in eoan
Thanks, I'm looking at that one ** Changed in: gnome-keyring (Ubuntu) Status: Confirmed => In Progress -- 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/1843737 Title: gnome-keyring ftbfs in eoan Status in gnome-keyring package in Ubuntu: In Progress Bug description: https://launchpadlibrarian.net/441262649/buildlog_ubuntu-eoan-amd64 .gnome-keyring_3.31.91-1ubuntu2_BUILDING.txt.gz Testsuite summary for gnome-keyring 3.31.91 # TOTAL: 636 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 636 === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1843737/+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 1843744] [NEW] libdbusmenu ftbfs in eoan
Public bug reported: https://launchpadlibrarian.net/441262368/buildlog_ubuntu-eoan- amd64.libdbusmenu_16.04.1+18.10.20180917-0ubuntu1_BUILDING.txt.gz /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../libdbusmenu-glib -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -Werror -Wno-error=deprecated-declarations -DG_LOG_DOMAIN="\"LIBDBUSMENU-GLIB\"" -g -O2 -fdebug-prefix-map=/<>/libdbusmenu-16.04.1+18.10.20180917=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libdbusmenu_glib_la-defaults.lo `test -f 'defaults.c' || echo '../../../libdbusmenu-glib/'`defaults.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../libdbusmenu-glib -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -Werror -Wno-error=deprecated-declarations -DG_LOG_DOMAIN=\"LIBDBUSMENU-GLIB\" -g -O2 -fdebug-prefix-map=/<>/libdbusmenu-16.04.1+18.10.20180917=. -fstack-protector-strong -Wformat -Werror=format-security -c ../../../libdbusmenu-glib/defaults.c -fPIC -DPIC -o .libs/libdbusmenu_glib_la-defaults.o ../../../libdbusmenu-glib/defaults.c: In function ‘dbusmenu_defaults_class_init’: ../../../libdbusmenu-glib/defaults.c:67:2: warning: ‘g_type_class_add_private’ is deprecated [-Wdeprecated-declarations] 67 | g_type_class_add_private (klass, sizeof (DbusmenuDefaultsPrivate)); | ^~~~ In file included from /usr/include/glib-2.0/gobject/gobject.h:24, from /usr/include/glib-2.0/gobject/gbinding.h:29, from /usr/include/glib-2.0/glib-object.h:23, from ../../../libdbusmenu-glib/defaults.h:33, from ../../../libdbusmenu-glib/defaults.c:35: /usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here 1308 | void g_type_class_add_private (gpointer g_class, | ^~~~ ../../../libdbusmenu-glib/defaults.c: In function ‘dbusmenu_defaults_init’: ../../../libdbusmenu-glib/defaults.c:77:13: error: G_ADD_PRIVATE [-Werror] 77 | self->priv = DBUSMENU_DEFAULTS_GET_PRIVATE(self); | ^~~ cc1: all warnings being treated as errors make[5]: *** [Makefile:712: libdbusmenu_glib_la-defaults.lo] Error 1 ** Affects: libdbusmenu (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ee-incoming ** Changed in: libdbusmenu (Ubuntu) Status: New => Confirmed ** Changed in: libdbusmenu (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libdbusmenu in Ubuntu. https://bugs.launchpad.net/bugs/1843744 Title: libdbusmenu ftbfs in eoan Status in libdbusmenu package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441262368/buildlog_ubuntu-eoan- amd64.libdbusmenu_16.04.1+18.10.20180917-0ubuntu1_BUILDING.txt.gz /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../libdbusmenu-glib -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -Werror -Wno-error=deprecated-declarations -DG_LOG_DOMAIN="\"LIBDBUSMENU-GLIB\"" -g -O2 -fdebug-prefix-map=/<>/libdbusmenu-16.04.1+18.10.20180917=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libdbusmenu_glib_la-defaults.lo `test -f 'defaults.c' || echo '../../../libdbusmenu-glib/'`defaults.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../libdbusmenu-glib -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -Werror -Wno-error=deprecated-declarations -DG_LOG_DOMAIN=\"LIBDBUSMENU-GLIB\" -g -O2 -fdebug-prefix-map=/<>/libdbusmenu-16.04.1+18.10.20180917=. -fstack-protector-strong -Wformat -Werror=format-security -c ../../../libdbusmenu-glib/defaults.c -fPIC -DPIC -o .libs/libdbusmenu_glib_la-defaults.o ../../../libdbusmenu-glib/defaults.c: In function ‘dbusmenu_defaults_class_init’: ../../../libdbusmenu-glib/defaults.c:67:2: warning: ‘g_type_class_add_private’ is deprecated [-Wdeprecated-declarations] 67 | g_type_class_add_private (klass, sizeof (DbusmenuDefaultsPrivate)); | ^~~~ In file included from /usr/include/glib-2.0/gobject/gobject.h:24, from /usr/include/glib-2.0/gobject/gbinding.h:29, from /usr/include/glib-2.0/glib-object.h:23, from ../../../libdbusmenu-glib/defaults.h:33, from ../../../libdbusmenu-glib/defaults.c:35:
[Desktop-packages] [Bug 1843750] [NEW] libsecret ftbfs in eoan
Public bug reported: https://launchpadlibrarian.net/441262252/buildlog_ubuntu-eoan- amd64.libsecret_0.18.8-1_BUILDING.txt.gz Testsuite summary for libsecret 0.18.8 # TOTAL: 198 # PASS: 13 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 185 == ** Affects: libsecret (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ee-incoming ** Changed in: libsecret (Ubuntu) Status: New => Confirmed ** Changed in: libsecret (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1843750 Title: libsecret ftbfs in eoan Status in libsecret package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441262252/buildlog_ubuntu-eoan- amd64.libsecret_0.18.8-1_BUILDING.txt.gz Testsuite summary for libsecret 0.18.8 # TOTAL: 198 # PASS: 13 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 185 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1843750/+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 1795021] Re: gsd-xsettings high memory usage
…and could this issue be related to this one? https://bugzilla.redhat.com/show_bug.cgi?id=1668808 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1795021 Title: gsd-xsettings high memory usage Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: gsd-xsettings is using ~700MB of memory. I think there could be some memory leak because I don't remember it ever happening before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Sep 28 18:42:46 2018 InstallationDate: Installed on 2017-08-21 (403 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795021/+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 1842643] Re: [ffe] Update to 1.44.6
Feel free then, I'm just really unsure personally about us being able to fix regressions, but if you think that is an OK risk then fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: New Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+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 1795021] Re: gsd-xsettings high memory usage
I'm having the same problem on Ubuntu 18.04.3 LTS. gsd-xsettings is the reason my system is even fully filling the SWAP. Is there any possibility to debug this? ** Bug watch added: Red Hat Bugzilla #1668808 https://bugzilla.redhat.com/show_bug.cgi?id=1668808 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1795021 Title: gsd-xsettings high memory usage Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: gsd-xsettings is using ~700MB of memory. I think there could be some memory leak because I don't remember it ever happening before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Sep 28 18:42:46 2018 InstallationDate: Installed on 2017-08-21 (403 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795021/+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 1843740] [NEW] indicator-messages ftbfs in eoan
Public bug reported: https://launchpadlibrarian.net/441262676/buildlog_ubuntu-eoan-amd64 .indicator-messages_13.10.1+18.10.20180918-0ubuntu1_BUILDING.txt.gz gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/accountsservice-1.0 -I../common -Wall -Wl,-Bsymbolic-functions -Wl,-z,defs -Wl,--as-needed -Werror -Wno-error=deprecated-declarations -DG_LOG_DOMAIN=\"Indicator-Messages\" -g -O2 -fdebug-prefix-map=/<>/indicator-messages-13.10.1+18.10.20180918=. -fstack-protector-strong -Wformat -Werror=format-security -c -o indicator_messages_service-im-accounts-service.o `test -f 'im-accounts-service.c' || echo './'`im-accounts-service.c im-accounts-service.c: In function ‘im_accounts_service_class_init’: im-accounts-service.c:54:2: warning: ‘g_type_class_add_private’ is deprecated [-Wdeprecated-declarations] 54 | g_type_class_add_private (klass, sizeof (ImAccountsServicePrivate)); | ^~~~ In file included from /usr/include/glib-2.0/gobject/gobject.h:24, from /usr/include/glib-2.0/gobject/gbinding.h:29, from /usr/include/glib-2.0/glib-object.h:23, from /usr/include/accountsservice-1.0/act/act-user-enum-types.h:7, from /usr/include/accountsservice-1.0/act/act.h:24, from im-accounts-service.c:24: /usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here 1308 | void g_type_class_add_private (gpointer g_class, | ^~~~ im-accounts-service.c: In function ‘im_accounts_service_init’: im-accounts-service.c:63:13: error: G_ADD_PRIVATE [-Werror] 63 | ImAccountsServicePrivate * priv = IM_ACCOUNTS_SERVICE_GET_PRIVATE(self); | ^~~ im-accounts-service.c: In function ‘im_accounts_service_dispose’: im-accounts-service.c:81:13: error: G_ADD_PRIVATE [-Werror] 81 | ImAccountsServicePrivate * priv = IM_ACCOUNTS_SERVICE_GET_PRIVATE(object); | ^~~ im-accounts-service.c: In function ‘user_changed’: im-accounts-service.c:107:13: error: G_ADD_PRIVATE [-Werror] 107 | ImAccountsServicePrivate * priv = IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); | ^~~ im-accounts-service.c: In function ‘security_privacy_ready’: im-accounts-service.c:138:13: error: G_ADD_PRIVATE [-Werror] 138 | ImAccountsServicePrivate * priv = IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); | ^~~ im-accounts-service.c: In function ‘on_user_manager_loaded’: im-accounts-service.c:149:13: error: G_ADD_PRIVATE [-Werror] 149 | ImAccountsServicePrivate * priv = IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); | ^~~ im-accounts-service.c: In function ‘im_accounts_service_set_draws_attention’: im-accounts-service.c:183:13: error: G_ADD_PRIVATE [-Werror] 183 | ImAccountsServicePrivate * priv = IM_ACCOUNTS_SERVICE_GET_PRIVATE(service); | ^~~ im-accounts-service.c: In function ‘im_accounts_service_get_show_on_greeter’: im-accounts-service.c:209:13: error: G_ADD_PRIVATE [-Werror] 209 | ImAccountsServicePrivate * priv = IM_ACCOUNTS_SERVICE_GET_PRIVATE(service); | ^~~ cc1: all warnings being treated as errors make[3]: *** [Makefile:622: indicator_messages_service-im-accounts-service.o] Error 1 make[3]: Leaving directory '/<>/indicator-messages-13.10.1+18.10.20180918/src' make[2]: *** [Makefile:491: all-recursive] Error 1 make[2]: Leaving directory '/<>/indicator-messages-13.10.1+18.10.20180918' make[1]: *** [Makefile:422: all] Error 2 make[1]: Leaving directory '/<>/indicator-messages-13.10.1+18.10.20180918' dh_auto_build: make -j1 returned exit code 2 make: *** [debian/rules:6: build] Error 255 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 ** Affects: indicator-messages (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ee-incoming ** Tags added: ftbfs rls-ee-incoming ** Changed in: indicator-messages (Ubuntu) Status: New => Confirmed ** Changed in: indicator-messages (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1843740 Title: indicator-messages ftbfs in eoan Status in indicator-messages package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441262676/buildlog_ubuntu-eoan-amd64 .indicator-messages_13.10.1+18.10.20180918-0ubuntu1_BUILDING.txt.gz gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
[Desktop-packages] [Bug 1843736] [NEW] gnome-initial-setup ftbfs in eoan
Public bug reported: https://launchpadlibrarian.net/441262595/buildlog_ubuntu-eoan-amd64 .gnome-initial-setup_3.33.91-1ubuntu2_BUILDING.txt.gz Could not generate cargs for cheese: CMake binary for MachineChoice.HOST is not cached CMake binary missing from cross or native file, or env var undefined. Trying a default CMake fallback at cmake Trying CMake binary cmake for machine MachineChoice.HOST at [None] Did not find CMake 'cmake' Found CMake: NO No CMake binary for machine MachineChoice.HOST not found. Giving up. Run-time dependency cheese found: NO meson.build:47:0: ERROR: Could not generate cargs for cheese: dh_auto_configure: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled -Dsoftware-sources=disabled -Dvendor-conf-file=/usr/lib/gnome-initial-setup/vendor.conf returned exit code 1 ** Affects: gnome-initial-setup (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ee-incoming ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Confirmed ** Changed in: gnome-initial-setup (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1843736 Title: gnome-initial-setup ftbfs in eoan Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441262595/buildlog_ubuntu-eoan-amd64 .gnome-initial-setup_3.33.91-1ubuntu2_BUILDING.txt.gz Could not generate cargs for cheese: CMake binary for MachineChoice.HOST is not cached CMake binary missing from cross or native file, or env var undefined. Trying a default CMake fallback at cmake Trying CMake binary cmake for machine MachineChoice.HOST at [None] Did not find CMake 'cmake' Found CMake: NO No CMake binary for machine MachineChoice.HOST not found. Giving up. Run-time dependency cheese found: NO meson.build:47:0: ERROR: Could not generate cargs for cheese: dh_auto_configure: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled -Dsoftware-sources=disabled -Dvendor-conf-file=/usr/lib/gnome-initial-setup/vendor.conf returned exit code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1843736/+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 1843733] [NEW] fftw3 ftbfs in eoan (armhf only)
Public bug reported: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' ** Affects: fftw3 (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ee-incoming ** Changed in: fftw3 (Ubuntu) Status: New => Confirmed ** Changed in: fftw3 (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) Status in fftw3 package in Ubuntu: Confirmed Bug description: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1843733/+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 1843737] [NEW] gnome-keyring ftbfs in eoan
Public bug reported: https://launchpadlibrarian.net/441262649/buildlog_ubuntu-eoan-amd64 .gnome-keyring_3.31.91-1ubuntu2_BUILDING.txt.gz Testsuite summary for gnome-keyring 3.31.91 # TOTAL: 636 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 636 === ** Affects: gnome-keyring (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ee-incoming ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ee-incoming -- 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/1843737 Title: gnome-keyring ftbfs in eoan Status in gnome-keyring package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441262649/buildlog_ubuntu-eoan-amd64 .gnome-keyring_3.31.91-1ubuntu2_BUILDING.txt.gz Testsuite summary for gnome-keyring 3.31.91 # TOTAL: 636 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 636 === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1843737/+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 1843728] [NEW] bolt ftbfs in eoan (test failures)
Public bug reported: seen in the recent eoan test rebuild, all architectures Ok: 39 Expected Fail: 0 Fail: 2 Unexpected Pass: 0 Skipped: 0 Timeout: 0 dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 make[1]: *** [debian/rules:21: override_dh_auto_test] Error 255 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build] Error 2 ** Affects: bolt (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-ee-incoming ** Tags added: ftbfs rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1843728 Title: bolt ftbfs in eoan (test failures) Status in bolt package in Ubuntu: New Bug description: seen in the recent eoan test rebuild, all architectures Ok: 39 Expected Fail: 0 Fail: 2 Unexpected Pass: 0 Skipped: 0 Timeout: 0 dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 make[1]: *** [debian/rules:21: override_dh_auto_test] Error 255 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1843728/+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 1842643] Re: [ffe] Update to 1.44.6
I'm unsure we have someone in the team/around who knows enough about font rendering to weigh in. I would go forward now with the update because I feel like it's a safer road for the LTS to land changes earlier than later, that time we get one buffer nonLTS cycle to get feedback sort out issues (also based on the fact that even if there are bugs they aren't obvious on a default installation and we can still fix special cases between now and release or in a SRU) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: New Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+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 1843730] [NEW] dee ftbfs in eoan (all architectures)
Public bug reported: https://launchpadlibrarian.net/441262638/buildlog_ubuntu-eoan- amd64.dee_1.2.7+17.10.20170616-4ubuntu1_BUILDING.txt.gz deprecated glib/gtk symbols ** Affects: dee (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ee-incoming ** Tags added: ftbfs rls-ee-incoming ** Changed in: dee (Ubuntu) Status: New => Confirmed ** Changed in: dee (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dee in Ubuntu. Matching subscriptions: dp-dee https://bugs.launchpad.net/bugs/1843730 Title: dee ftbfs in eoan (all architectures) Status in dee package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441262638/buildlog_ubuntu-eoan- amd64.dee_1.2.7+17.10.20170616-4ubuntu1_BUILDING.txt.gz deprecated glib/gtk symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1843730/+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 1843499] Re: [eoan] Wayland session misses non-GNOME apps theming
seems duplicate of : https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1843107 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1843499 Title: [eoan] Wayland session misses non-GNOME apps theming Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Running GS 3.34 from proposed (or 3.33.92 too), the GNOME or Ubuntu sessions miss non-GNOME apps theming. I use Adwaita, it runs Yaru (if installed...) and picks up wrong fonts. Examples of such apps : wxMaxima, Thunderbird, Firefox. Running X session, all is fine. But here too there's something fishy : when I switch from a Wayland session to a X session, the first login sees Synaptic tell me that I run a Wayland session and that I cannot apply changes (etc.). The consecutively second login in a X session does not experience this bug. This behaviour began with 3.33.92 updates of gdm, gnome-session and gnome-settings-daemon some days ago. Upstream GNOME bugs tells me to report in Ubuntu bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1843499/+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 1843499] Re: [eoan] Wayland session misses non-GNOME apps theming
https://gitlab.gnome.org/GNOME/mutter/issues/771 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #771 https://gitlab.gnome.org/GNOME/mutter/issues/771 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1843499 Title: [eoan] Wayland session misses non-GNOME apps theming Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Running GS 3.34 from proposed (or 3.33.92 too), the GNOME or Ubuntu sessions miss non-GNOME apps theming. I use Adwaita, it runs Yaru (if installed...) and picks up wrong fonts. Examples of such apps : wxMaxima, Thunderbird, Firefox. Running X session, all is fine. But here too there's something fishy : when I switch from a Wayland session to a X session, the first login sees Synaptic tell me that I run a Wayland session and that I cannot apply changes (etc.). The consecutively second login in a X session does not experience this bug. This behaviour began with 3.33.92 updates of gdm, gnome-session and gnome-settings-daemon some days ago. Upstream GNOME bugs tells me to report in Ubuntu bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1843499/+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 1843499] Re: [eoan] Wayland session misses non-GNOME apps theming
** Changed in: gnome-settings-daemon Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1843499 Title: [eoan] Wayland session misses non-GNOME apps theming Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Running GS 3.34 from proposed (or 3.33.92 too), the GNOME or Ubuntu sessions miss non-GNOME apps theming. I use Adwaita, it runs Yaru (if installed...) and picks up wrong fonts. Examples of such apps : wxMaxima, Thunderbird, Firefox. Running X session, all is fine. But here too there's something fishy : when I switch from a Wayland session to a X session, the first login sees Synaptic tell me that I run a Wayland session and that I cannot apply changes (etc.). The consecutively second login in a X session does not experience this bug. This behaviour began with 3.33.92 updates of gdm, gnome-session and gnome-settings-daemon some days ago. Upstream GNOME bugs tells me to report in Ubuntu bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1843499/+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 1843698] Re: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()
** Changed in: gnome-software Status: Unknown => New -- 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/1843698 Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() Status in GNOME Software: New Status in gnome-software package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-software/issues/792 --- I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 07:57:24 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 PC (0x7f565aa3fcc4) ok source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! destination "%ymm5" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384 g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1843698/+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 1843703] Re: gnome-shell crashed with SIGSEGV in async_get_property_finish()
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 + + --- + I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 - () - () at /lib/x86_64-linux-gnu/libc.so.6 - () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 + __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 + () + () at /lib/x86_64-linux-gnu/libc.so.6 + () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1599 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 Importance: Unknown Status: Unknown ** Description changed: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 --- I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. + + Also crashed _usr_lib_gnome-session_gnome-session-binary.1000 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** No longer affects: gnome-shell ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #780 https://gitlab.gnome.org/GNOME/mutter/issues/780 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/mutter/issues/780 Importance: Unknown Status: Unknown ** Description changed: - https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 + https://gitlab.gnome.org/GNOME/mutter/issues/780 --- I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. Also crashed _usr_lib_gnome-session_gnome-session-binary.1000 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline:
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
The attachment "nvidia suspend patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09
[Desktop-packages] [Bug 1843499] Re: [eoan] Wayland session misses non-GNOME apps theming
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #447 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/447 ** Also affects: gnome-settings-daemon via https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/447 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1843499 Title: [eoan] Wayland session misses non-GNOME apps theming Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Running GS 3.34 from proposed (or 3.33.92 too), the GNOME or Ubuntu sessions miss non-GNOME apps theming. I use Adwaita, it runs Yaru (if installed...) and picks up wrong fonts. Examples of such apps : wxMaxima, Thunderbird, Firefox. Running X session, all is fine. But here too there's something fishy : when I switch from a Wayland session to a X session, the first login sees Synaptic tell me that I run a Wayland session and that I cannot apply changes (etc.). The consecutively second login in a X session does not experience this bug. This behaviour began with 3.33.92 updates of gdm, gnome-session and gnome-settings-daemon some days ago. Upstream GNOME bugs tells me to report in Ubuntu bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1843499/+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 1843499] Re: [eoan] Wayland session misses non-GNOME apps theming
Ok I had time to do some bisects. The faulty upgrade is from this correct one : gnome-settings-daemon 3.33.90-1ubuntu2 The versions >= 3.33.92 suffer this bug. ** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843499 Title: [eoan] Wayland session misses non-GNOME apps theming Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Running GS 3.34 from proposed (or 3.33.92 too), the GNOME or Ubuntu sessions miss non-GNOME apps theming. I use Adwaita, it runs Yaru (if installed...) and picks up wrong fonts. Examples of such apps : wxMaxima, Thunderbird, Firefox. Running X session, all is fine. But here too there's something fishy : when I switch from a Wayland session to a X session, the first login sees Synaptic tell me that I run a Wayland session and that I cannot apply changes (etc.). The consecutively second login in a X session does not experience this bug. This behaviour began with 3.33.92 updates of gdm, gnome-session and gnome-settings-daemon some days ago. Upstream GNOME bugs tells me to report in Ubuntu bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1843499/+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 1843698] Re: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()
https://gitlab.gnome.org/GNOME/gnome-software/issues/792 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-software/issues/792 + + --- + I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 07:57:24 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: - gnome-software-plugin-flatpak 3.30.6-2ubuntu10 - gnome-software-plugin-snap3.30.6-2ubuntu10 + gnome-software-plugin-flatpak 3.30.6-2ubuntu10 + gnome-software-plugin-snap3.30.6-2ubuntu10 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: - Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 - PC (0x7f565aa3fcc4) ok - source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! - destination "%ymm5" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 + PC (0x7f565aa3fcc4) ok + source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! + destination "%ymm5" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: - __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384 - g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 - () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so + __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384 + g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 + () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #792 https://gitlab.gnome.org/GNOME/gnome-software/issues/792 ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/issues/792 Importance: Unknown Status: Unknown -- 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/1843698 Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-software/issues/792 --- I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 07:57:24 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 PC (0x7f565aa3fcc4) ok source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! destination "%ymm5" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software
[Desktop-packages] [Bug 1843697] Re: gnome-shell crashed with SIGSEGV in meta_get_stage_for_display()
*** This bug is a duplicate of bug 1843512 *** https://bugs.launchpad.net/bugs/1843512 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1843512, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1843697/+attachment/5288247/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1843697/+attachment/5288249/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1843697/+attachment/5288254/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1843697/+attachment/5288255/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1843697/+attachment/5288256/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1843697/+attachment/5288259/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1843697/+attachment/5288260/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1843512 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843697 Title: gnome-shell crashed with SIGSEGV in meta_get_stage_for_display() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashed with SIGSEGV in meta_get_stage_for_display() ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 14:00:06 2019 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-20 (265 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181214) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_get_stage_for_display () from /lib/x86_64-linux-gnu/libmutter-5.so.0 meta_stage_is_focused () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /usr/lib/gnome-shell/libgnome-shell.so g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_get_stage_for_display() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843697/+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 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
Patch is supposed to go into nvidia-dkms-435 /usr/src/nvidia-435.21/patch has to be included into dkms.conf ** Patch added: "nvidia suspend patch" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288262/+files/nvidia-suspend.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago)
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "dmesg echo processors pm_trace" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288242/+files/dmesg_8_processors_pm_trace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage:
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "dmesg echo none pm_trace" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288244/+files/dmesg_10_none_pm_trace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage:
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "dmesg echo core pm_trace" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288243/+files/dmesg_9_core_pm_trace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage:
[Desktop-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Confirmed Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "suspend_stats" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288245/+files/suspend_stats -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-430
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "wakeup" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288246/+files/wakeup -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-430 UpgradeStatus: No
[Desktop-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
I have exactly the same problem described in the title since 2018-11-27, when I bought this laptop. My configuration: HP Elitebook 840 G1 Ubuntu 18.04 The same issue does not hit Windows, which I dual boot with. -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Confirmed Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "dmesg echo platform pm_trace" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288241/+files/dmesg_7_platform_pm_trace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage:
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "dmesg echo wakeup pm_trace" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288238/+files/dmesg_4_wakeup_pm_trace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage:
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "dmesg echo devices pm_trace" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288240/+files/dmesg_6_devices_pm_trace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage:
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
** Attachment added: "dmesg echo freeze pm_trace" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+attachment/5288239/+files/dmesg_5_freeze_pm_trace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage:
[Desktop-packages] [Bug 1843695] [NEW] Freeze after suspend to RAM nvidia kernel 5.0.0.x
Public bug reported: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-430 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kernel nvidia ** Attachment added: "dmesg after reboot from freeze resume STD" https://bugs.launchpad.net/bugs/1843695/+attachment/5288234/+files/dmesg_pm_trace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in
[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
** Changed in: gnome-settings-daemon (Fedora) Status: In Progress => Won't Fix -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Unknown Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: Won't Fix Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+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 1841826] Re: Going to sleep instead of logging in while lid closed & external display
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/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-shell package in Ubuntu: Confirmed Bug description: I have the above described problem, which seems to be very similar to bug #1716160 - laptop is in docking station and 2 monitors are connected (HDMI, DVI) - If the lid is closed and I boot the laptop I can input my credentials in the login screen and after hitting ENTER the laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841826/+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 1843682] [NEW] Cannot open Libreoffice attachments (e.g. .xlsx) in Evolution
Public bug reported: 1) ~$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Disco Dingo 2) libreoffice 6.3.0.4 (Snap package) 3) I expect Libreoffice to open my attachment when I double-click it. 4) I receive the error: Access to /home/nikolaj/.cache/evolution/tmp/.xlsx was denied. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Description changed: - 1) - ~$ lsb_release -rd + 1) ~$ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 - 2) - libreoffice 6.3.0.4 (Snap package) + 2) libreoffice 6.3.0.4 (Snap package) 3) I expect Libreoffice to open my attachment when I double-click it. 4) I receive the error: Access to /home/nikolaj/.cache/evolution/tmp/.xlsx was denied. ** Description changed: 1) ~$ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 + Disco Dingo 2) libreoffice 6.3.0.4 (Snap package) 3) I expect Libreoffice to open my attachment when I double-click it. 4) I receive the error: Access to /home/nikolaj/.cache/evolution/tmp/.xlsx was denied. -- 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/1843682 Title: Cannot open Libreoffice attachments (e.g. .xlsx) in Evolution Status in libreoffice package in Ubuntu: New Bug description: 1) ~$ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 Disco Dingo 2) libreoffice 6.3.0.4 (Snap package) 3) I expect Libreoffice to open my attachment when I double-click it. 4) I receive the error: Access to /home/nikolaj/.cache/evolution/tmp/.xlsx was denied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1843682/+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 1766192] Re: [snap] cannot save file under $HOME
I cannot open attachments in Evolution using Libreoffice in Disco. I receive the error: Access to /home/user/.cache/evolution/tmp/.xlsx was denied. -- 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/1766192 Title: [snap] cannot save file under $HOME Status in snapd: Triaged Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: (this was initially reported on the forum: https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032) When trying to save a file under $HOME (not a subdirectory), the user is presented with an error dialog: --- Error --- Error saving the document Untitled 1: Object not accessible. The object cannot be accessed due to insufficient user rights. [OK] This is because libreoffice tries to create a lock file of the form: "$HOME/.~lock.Untitled 1.odt", and the home interface doesn't allow writing hidden files (those with a filename that starts with a dot) under $HOME. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" DESKTOP_SESSION=ubuntu GTK_MODULES=gail:atk-bridge HOME=/home/osomon/snap/libreoffice/59 LANG=fr_FR.UTF-8 LC_MONETARY=fr_FR.UTF-8 LC_NAME=fr_FR.UTF-8 LC_NUMERIC=fr_FR.UTF-8 LC_TIME=fr_FR.UTF-8 LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu::/snap/libreoffice/59/lib:/snap/libreoffice/59/usr/lib:/snap/libreoffice/59/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa PATH=/snap/libreoffice/59/usr/sbin:/snap/libreoffice/59/usr/bin:/snap/libreoffice/59/sbin:/snap/libreoffice/59/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games SNAP=/snap/libreoffice/59 SNAP_ARCH=amd64 SNAP_COMMON=/var/snap/libreoffice/common SNAP_DATA=/var/snap/libreoffice/59 SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void SNAP_NAME=libreoffice SNAP_REEXEC= SNAP_REVISION=59 SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common SNAP_USER_DATA=/home/osomon/snap/libreoffice/59 SNAP_VERSION=6.0.3.2 TEMPDIR=/tmp TMPDIR=/run/user/1000/snap.libreoffice XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg XDG_CURRENT_DESKTOP=ubuntu:GNOME XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice XDG_SESSION_DESKTOP=ubuntu XDG_SESSION_TYPE=x11 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1766192/+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 1292398] Re: Second screen position isn't saved from one session to another
I am seeing this problem on Disco Dingo using Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+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
