[Desktop-packages] [Bug 1815694] Re: GLib-CRITICAL and does not start
you also need this package https://packages.ubuntu.com/bionic/adwaita- icon-theme-full -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1815694 Title: GLib-CRITICAL and does not start Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Confirmed Bug description: 1) I try: /snap/bin/inkscape 2) but terminal showed me: ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Mint-Y (gtk-icon-theme-error-quark, 0) Emergency save activated! (inkscape:6503): GLib-CRITICAL **: 02:12:42.305: g_path_get_dirname: assertion 'file_name != NULL' failed Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Gtk-Message: 02:12:42.314: GtkDialog mapped without a transient parent. This is discouraged. 3) Application does not start 4) I use: Linux Mint 19, Cinnamon, 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1815694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801898] Re: Only one of two external (displayport) displays is working without hotplug
I think this bug can be closed. Some upstream update (not sure which) made it work as it should. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801898 Title: Only one of two external (displayport) displays is working without hotplug Status in xorg-server package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in one of my two external displays will not be activated without hotplugging the other external display. The display settings app shows the second display as inactive, and when trying to activate it the settings app states that some hardware limitation stops it from being possible to apply the change. The laptop lid is closed, the internal laptop display is not active. Hotplugging the other external display solves the problem - after hotplug both external displays are active. This makes the bug annoying but workaroundable. I am not sure if this bug belongs to the Xorg package or the linux package. Hardware: Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two external displays connected through displayport (via docking station). $ sudo lspci -v 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 6000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu8 Candidate: 1:7.7+19ubuntu8 Version table: *** 1:7.7+19ubuntu8 500 500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy linux-image-4.18.0-10-generic linux-image-4.18.0-10-generic: Installed: 4.18.0-10.11 Candidate: 4.18.0-10.11 Version table: *** 4.18.0-10.11 500 500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-10-24 10:23:47,912 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroRelease: Ubuntu 18.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: hsize = 2 vsize = 2 GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] InstallationDate: Installed on 2016-06-06 (883 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 2356FW4 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/vg_avin-lv_root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic ubuntu Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-24 (14 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356FW4 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: R9TW1K9 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2356FW4:pvrThinkPadT430s:rvnLENOVO:rn2356FW4:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2356FW4 dmi.product.sku: LENOVO_MT_2356 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache
** Description changed:
[Impact]
- A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
+ A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
+ Source Package :
+ https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
- Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
+ Can we get this fix merged in current LTS 18.04 as "-updates"
+
+ [Test app]
+
+ To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
+ And run a small test app with this piece of code.
+ void *handle = dlopen("libGLX.so.0", 2);
+ glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
+ glXGetProcAddressARB("glXAllocateMemoryMESA");
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1816004
Title:
GLVND: AARCH64 : Fix address passed to clear cache
Status in libglvnd package in Ubuntu:
New
Bug description:
[Impact]
A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
Can we get this fix merged in current LTS 18.04 as "-updates"
[Test app]
To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
And run a small test app with this piece of code.
void *handle = dlopen("libGLX.so.0", 2);
glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
glXGetProcAddressARB("glXAllocateMemoryMESA");
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
I uploaded these changes for bionic and cosmic. Just waiting on sru
approval now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
mono playback
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
In Progress
Status in pulseaudio source package in Cosmic:
In Progress
Status in pulseaudio source package in Disco:
Fix Released
Bug description:
[Impact]
* User is only able to get mono audio from steelseries headsets
because they provide both a stereo and mono output. PA selects the
mono output by default.
* This should be backported to stable releases because this fix is
isolated to code that only applies to the affected headsets.
Additionally other gaming headsets may be more easily enabled by adding
ATTRS{idVendor}=="", ATTRS{idProduct}=="",
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
to /lib/udev/rules.d/90-pulseaudio.rules now. Such as the Lucidsound
LS31 which I own.
* The upload fixes the bug by conditionally setting a pulseaudio
profile for the headset based on specific usb vendor and product ids
in the udev rules.
[Test Case]
1. Acquire headset.
2. Open sound settings, and click test speakers.
3. Only option available will be mono sound
[Regression Potential]
* Risk of regressions should be mitigated to those who own the
headset. In which case it is likely that their headset is already not
working.
[Other Info]
* All patches originate from upstream pulseaudio, and are documented as
such including the shas.
* I will be pursuing enabling other similar headsets in the coming weeks.
* I plan to work with upstream pulseaudio to enable my own headset and to
also make the headset templates backported here more generic.
Original Description -
There is not stereo playback only mono playback
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio
/dev/snd/controlC1: kaj1755 F pulseaudio
/dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio
/dev/snd/controlC0: kaj1755 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 21:30:50 2018
InstallationDate: Installed on 2018-03-08 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET35W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS2AV00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS2AV00
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815883] Re: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
*** This bug is a duplicate of bug 1814949 *** https://bugs.launchpad.net/bugs/1814949 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1815883 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Crashes when I click on details then cannot launch it again. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 10:52:25 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2014-07-15 (1675 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f192395232d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f192395232d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-03-24 (326 days ago) UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816004] [NEW] GLVND: AARCH64 : Fix address passed to clear cache
Public bug reported: [Impact] A new fix has been merged to NVIDIA libglvnd repo at https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e We need to include it in bionic. It would be ok to just include this fix even without updating to the latest glvnd version. This change fixes a crash seen in some GLX apps while calling glXGetProcAddress. Source Package : https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2 ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Package changed: vulkan (Ubuntu) => libglvnd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1816004 Title: GLVND: AARCH64 : Fix address passed to clear cache Status in libglvnd package in Ubuntu: New Bug description: [Impact] A new fix has been merged to NVIDIA libglvnd repo at https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e We need to include it in bionic. It would be ok to just include this fix even without updating to the latest glvnd version. This change fixes a crash seen in some GLX apps while calling glXGetProcAddress. Source Package : https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816000] Re: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
I have also tried opening it through the terminal but it gives me a segmentation fault (Core Dumped) and have also tried reinstalling using sudo apt install --reinstall gnome-control-center. -- 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/1816000 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() Status in gnome-control-center package in Ubuntu: Invalid Bug description: I tried opening my settings App in my favorites and it would not load. I would then get an "Ubuntu has experienced an internal error" window to report the problem. I am using Ubuntu 19.04 with the most recent updates. 1:3.31.90-1ubuntu1 500 is the version of the package of gnome-control-center. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 22:14:06 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-01-17 (28 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd2ecb1632d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7fd2ecb1632d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2019-02-11 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816004] [NEW] GLVND: AARCH64 : Fix address passed to clear cache
You have been subscribed to a public bug: [Impact] A new fix has been merged to NVIDIA libglvnd repo at https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e We need to include it in bionic. It would be ok to just include this fix even without updating to the latest glvnd version. This change fixes a crash seen in some GLX apps while calling glXGetProcAddress. Source Package : https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2 ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New -- GLVND: AARCH64 : Fix address passed to clear cache https://bugs.launchpad.net/bugs/1816004 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd 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 1816000] Re: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
** Information type changed from Private to Public -- 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/1816000 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() Status in gnome-control-center package in Ubuntu: Invalid Bug description: I tried opening my settings App in my favorites and it would not load. I would then get an "Ubuntu has experienced an internal error" window to report the problem. I am using Ubuntu 19.04 with the most recent updates. 1:3.31.90-1ubuntu1 500 is the version of the package of gnome-control-center. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 22:14:06 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-01-17 (28 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd2ecb1632d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7fd2ecb1632d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2019-02-11 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2
** Also affects: libcdio (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888053 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1750264 Title: program 'cd-paranoia' is missing from package in 1.0.0-2 Status in libcdio package in Ubuntu: Invalid Status in libcdio-paranoia package in Ubuntu: Confirmed Status in libcdio package in Debian: Unknown Bug description: apt show libcdio-utils: Description: sample applications based on the CDIO libraries This package contains a collection of small libcdio-based tools: * cd-drive show CD-ROM drive characteristics * cd-info show information about a CD or CD-image * cd-paranoia an audio CD ripper * cd-read read information from a CD or CD-image * cdda-player a simple curses-based audio CD player * iso-info show information about an ISO 9660 image * iso-read read portions of an ISO 9660 image * mmc-tool issue low-level commands to a CD drive cd-paranoia is missing from package. This breaks abcde 'optional' functionality which is in fact the most common used, since the original cdparanoia (separate program) is abandoned since 10 years. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 libcdio-utils: Installiert: 1.0.0-2 Installationskandidat: 1.0.0-2 Versionstabelle: *** 1.0.0-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcdio-utils 1.0.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Feb 18 18:18:55 2018 ProcEnviron: TERM=qterminal PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801161] Re: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- 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/1801161 Title: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Status in libreoffice package in Ubuntu: Expired Bug description: Using LibreOffice Calc I was editing a filter on a pivot table and all LibreOffice windows hung. What appeared in /var/log/syslog was: Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown sequence number while processing queue Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry about that. Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Nov 1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice-calc 1:6.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 13:39:03 2018 InstallationDate: Installed on 2018-10-29 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808664] Re: pulse udio is not starting automatically at boot
[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/1808664 Title: pulse udio is not starting automatically at boot Status in pulseaudio package in Ubuntu: Expired Bug description: Pulseaudio is not getting loaded at the time of boot and it has to be manually started each time ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-42-generic. ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: murtyvonna 2094 F pulseaudio /dev/snd/controlC0: murtyvonna 2094 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 34' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,1043841b,00100302 HDA:80862806,80860101,0010' Controls : 65 Simple ctrls : 24 Card1.Amixer.info: Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-:00:14.0-1, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0825' Controls : 3 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined Capture channels: Mono Limits: Capture 0 - 15 Mono: Capture 0 [0%] [8.00dB] [on] CurrentDesktop: ubuntu:GNOME Date: Sun Dec 16 08:19:23 2018 InstallationDate: Installed on 2018-08-06 (131 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1808664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697481] Re: totem-video-thumbnailer crashed with signal 5 in g_malloc()
*** This bug is a duplicate of bug 1697234 *** https://bugs.launchpad.net/bugs/1697234 my desktop os is Ubuntu 16.04.5 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1697481 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Every time I open a folder with MTS video files the video thumbnailer crashes. It would be ok, if it just failed gracefully. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Jun 12 16:58:17 2017 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2016-09-09 (275 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS /tmp/.gnome_desktop_thumbnail.59DG1Y Signal: 5 SourcePackage: gstreamer1.0 StacktraceTop: g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_buffer_new_allocate () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: lxd sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1697481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697481] Re: totem-video-thumbnailer crashed with signal 5 in g_malloc()
*** This bug is a duplicate of bug 1697234 ***
https://bugs.launchpad.net/bugs/1697234
I have same problem,
I figured
~/.cache/upstart/update-notifier-crash-_var_crash__usr_bin_totem-video-thumbnailer.1000.crash.log
like below:
2019. 02. 15. (금) 11:41:51 KST crash report /var/crash/_usr_bin_totem-
video-thumbnailer.1000.crash detected
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget
'GtkSpinner': out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget
'GtkAlignment': out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget
'GtkOverlay': out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget 'GtkBox':
out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget 'GtkBox':
out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget 'GtkBox':
out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget 'GtkWindow': out
of memory
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1697481
Title:
totem-video-thumbnailer crashed with signal 5 in g_malloc()
Status in gstreamer1.0 package in Ubuntu:
Confirmed
Bug description:
Every time I open a folder with MTS video files the video thumbnailer
crashes. It would be ok, if it just failed gracefully.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Jun 12 16:58:17 2017
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2016-09-09 (275 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256
file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS
/tmp/.gnome_desktop_thumbnail.59DG1Y
Signal: 5
SourcePackage: gstreamer1.0
StacktraceTop:
g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
gst_buffer_new_allocate () from
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
Title: totem-video-thumbnailer crashed with signal 5 in g_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: lxd sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1697481/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.77-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-390 (390.77-0ubuntu0.18.04.2) bionic; urgency=medium * debian/rules.defs: - Add support for xserver-xorg-core-hwe-18.04 (LP: #1815579). -- Alberto Milone Thu, 14 Feb 2019 16:14:57 +0100 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04
[Desktop-packages] [Bug 1815579] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-340 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
This bug was fixed in the package nvidia-graphics-drivers-340 - 340.107-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-340 (340.107-0ubuntu0.18.04.2) bionic; urgency=medium * Add support for xserver-xorg-core-hwe-18.04 (LP: #1815579). -- Alberto Milone Thu, 14 Feb 2019 16:48:59 +0100 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04
[Desktop-packages] [Bug 1815957] [NEW] SynPS/2 Synaptics TouchPad: Read error 19
Public bug reported: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1815957/+attachment/5238744/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: New Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Triaged
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Triaged
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815938] Re: 'Developer' and 'Uploader' fields are mixed for snaps
That's a snapd issue mostly, see https://forum.snapcraft.io/t /implication-of-the-word-developer/3960 ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Triaged -- 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/1815938 Title: 'Developer' and 'Uploader' fields are mixed for snaps Status in gnome-software package in Ubuntu: Triaged Bug description: Steps: 1. Start gnome-software 2. Search for GNOME Web 3. Select the snap package 4. Look at the 'Developer' field, where it shows 'Jeremy Bicha' ⇒ Jeremy is not the 'Developer', he is the 'Uploader'. 5. Go back and select the deb package 6. Look at the 'Developer' field, where it shows 'The GNOME Project' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 18:16:23 2019 InstallationDate: Installed on 2018-11-29 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.8 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815339]
Created attachment 16882 patch Patch to fix this and Bug 699713 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1815339 Title: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26 Status in GS-GPL: Unknown Status in ghostscript package in Ubuntu: Triaged Bug description: I have an issue with Ghostscript and printing. I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 6"x4"), it does not print anything, however I still able to print A4 paper size. I use Ubuntu 18.04 and Gutenprint 5.3.1. The printing fail with message: [Job 143] Start rendering... [Job 143] Processing page 1... [Job 143] Unable to open the initial device, quitting. [Job 143] Rendering completed ... [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1. ... [Job 143] printer-state-message="Filter failed" [Job 143] printer-state-reasons=none The message "Unable to open the initial device, quitting" comes from Ghostscript. When I downgrade Ghostscript to 9.22, I am again able to print 4"x6" paper size. To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1 libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1 I found similar issue for HP printer at Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=908205 System info: Description: Ubuntu 18.04.1 LTS Release: 18.04 ghostscript: Installed: 9.26~dfsg+0-0ubuntu0.18.04.4 Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4 Versions: *** 9.26~dfsg+0-0ubuntu0.18.04.4 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 9.22~dfsg+1-0ubuntu1 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages cups: Installed: 2.2.7-1ubuntu2.3 Candidate: 2.2.7-1ubuntu2.3 Versions: *** 2.2.7-1ubuntu2.3 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.2.7-1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.2.7-1ubuntu2 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1815339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815947] Re: video
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815947 Title: video Status in xorg package in Ubuntu: Incomplete Bug description: beside_only_pixel_mousebl_nettv_no_lon_same_se_al_?_n_wh_cr_tsp ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: /dev/sda1: clean, 323551/19144704 files, 17190727/76570112 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 14 19:14:04 2019 DistUpgraded: 2018-06-22 23:29:57,626 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G92 [GeForce GTS 250] [10b0:0401] NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G92 [GeForce GTS 250] [1043:82fb] InstallationDate: Installed on 2018-06-17 (242 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=sl PATH=(custom, no user) LANG=sl_SI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=0bbe53b3-055a-45b3-9588-a717e2462ba9 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-06-22 (236 days ago) dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 0703 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision0703:bd08/09/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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:
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
Nope, see previous posts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 383435] Re: Firefox lags when scrolling
I experienced lag, while scrolling, after force-enabling hardware acceleration and using AMD's GPU on Fedora also. -- 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/383435 Title: Firefox lags when scrolling Status in firefox package in Ubuntu: Confirmed Status in firefox package in Fedora: New Bug description: Binary package hint: firefox-3.0 Scrolling lags badly in Firefox. It's not a consistent problem, but seems to build the longer I keep the browser open. After a day or so, I can spin my scroll wheel ten clicks... Wait... Nothing happens... Start to wonder if it's hung... And then the ten scroll events happen. The delay is very inconsistent, which from a usability standpoint is worse. Instead of just knowing it lags, it has feel like I mistakenly tried to scroll with the wrong window focused. My guess is that there's some garbage collection or something that happens periodically, and if I scroll during it, it has to wait until the *whatever* job is done. I keep saying scrolling here because it's the most obvious case, but I'm pretty sure all browser operations freeze during the lag time. This started under 8.10, and seemed to get better when I first switched to 9.04, but it's happening all the time again now. When it gets really bad, Flash videos start having problems too where they'll freeze for several seconds, much like the scrolling freezes. Clicking links to open pages also seems to be affected, again having some sporadic lag. Sadly, Firefox on my old P3-600 with 8.04 feels more responsive than on 9.04 on my Athlon64-5200. If I exit when it's really bad, Firefox consumes 100% CPU for 10 to 20 seconds after the window closes, but before the process exits. The time seems to be related to how much trouble I'm having with the lag. It'd be awfully interesting to know what it's cleaning up during that time, but I don't know how to find out. I have a workaround that seems to make it somewhat better: kill firefox, delete localstore.rdf, restart. This seems to work better than just restarting, but it's really hard to do side by side comparisons, since it takes a while to build up to the nasty lag. I've gone through many gyrations of deleting my profile and reimporting my bookmarks, disabling plugins, and removing Flash, all to no avail. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0.10+nobinonly-0ubuntu0.9.04.1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/383435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 383435] Re: Firefox lags when scrolling
The bug remains. ** Package changed: firefox-3.0 (Ubuntu) => firefox (Ubuntu) ** Also affects: firefox (Fedora) Importance: Undecided Status: New -- 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/383435 Title: Firefox lags when scrolling Status in firefox package in Ubuntu: Confirmed Status in firefox package in Fedora: New Bug description: Binary package hint: firefox-3.0 Scrolling lags badly in Firefox. It's not a consistent problem, but seems to build the longer I keep the browser open. After a day or so, I can spin my scroll wheel ten clicks... Wait... Nothing happens... Start to wonder if it's hung... And then the ten scroll events happen. The delay is very inconsistent, which from a usability standpoint is worse. Instead of just knowing it lags, it has feel like I mistakenly tried to scroll with the wrong window focused. My guess is that there's some garbage collection or something that happens periodically, and if I scroll during it, it has to wait until the *whatever* job is done. I keep saying scrolling here because it's the most obvious case, but I'm pretty sure all browser operations freeze during the lag time. This started under 8.10, and seemed to get better when I first switched to 9.04, but it's happening all the time again now. When it gets really bad, Flash videos start having problems too where they'll freeze for several seconds, much like the scrolling freezes. Clicking links to open pages also seems to be affected, again having some sporadic lag. Sadly, Firefox on my old P3-600 with 8.04 feels more responsive than on 9.04 on my Athlon64-5200. If I exit when it's really bad, Firefox consumes 100% CPU for 10 to 20 seconds after the window closes, but before the process exits. The time seems to be related to how much trouble I'm having with the lag. It'd be awfully interesting to know what it's cleaning up during that time, but I don't know how to find out. I have a workaround that seems to make it somewhat better: kill firefox, delete localstore.rdf, restart. This seems to work better than just restarting, but it's really hard to do side by side comparisons, since it takes a while to build up to the nasty lag. I've gone through many gyrations of deleting my profile and reimporting my bookmarks, disabling plugins, and removing Flash, all to no avail. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0.10+nobinonly-0ubuntu0.9.04.1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/383435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager
Just adding a note that this can also happen in Gnome on a system without XFCE. Commenting out: x-scheme-handler/file=exo-file-manager.desktop In the file: ~/.local/share/applications/mimeapps.list Like the Fedora note above worked. Not sure if a new ticket is needed to address the but outside of Xubuntu. Ubuntu 18.04, happened after upgrade from 16.04 -- 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/1778069 Title: [xfce] nautilus don't open files if set as default file manager Status in exo: Confirmed Status in nautilus package in Ubuntu: Invalid Status in xubuntu-default-settings package in Ubuntu: Fix Released Status in nautilus package in Debian: New Bug description: If Nautilus is set as the preferred file manager with exo-preferred- applications, it no longer opens files. It opens only directories, .desktop files and executable files. Trying to open a file, be using Enter or with double mouse click, as a text file or a video makes Nautilus window blink for a instant and nothing happens. To be able to open the files, it's needed to choose to open with another application and then choose the application. Once Nautilus is unset as the default file manager (Thunar is chosen, for example), it starts to work fine again, opening files properly. Nautilus' Debian Sid version do not have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.17.2-041702-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 21 10:55:41 2018 InstallationDate: Installed on 2017-06-13 (372 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1778069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815947] [NEW] video
Public bug reported: beside_only_pixel_mousebl_nettv_no_lon_same_se_al_?_n_wh_cr_tsp ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: /dev/sda1: clean, 323551/19144704 files, 17190727/76570112 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 14 19:14:04 2019 DistUpgraded: 2018-06-22 23:29:57,626 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G92 [GeForce GTS 250] [10b0:0401] NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G92 [GeForce GTS 250] [1043:82fb] InstallationDate: Installed on 2018-06-17 (242 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=sl PATH=(custom, no user) LANG=sl_SI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=0bbe53b3-055a-45b3-9588-a717e2462ba9 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-06-22 (236 days ago) dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 0703 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision0703:bd08/09/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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 xserver.bootTime: Wed Feb 13 18:46:13 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: [drm] Failed to open DRM device for (null): -22 open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815947 Title: video Status in xorg package in Ubuntu: New Bug description: beside_only_pixel_mousebl_nettv_no_lon_same_se_al_?_n_wh_cr_tsp ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia
[Desktop-packages] [Bug 383435] [NEW] Firefox lags when scrolling
You have been subscribed to a public bug: Binary package hint: firefox-3.0 Scrolling lags badly in Firefox. It's not a consistent problem, but seems to build the longer I keep the browser open. After a day or so, I can spin my scroll wheel ten clicks... Wait... Nothing happens... Start to wonder if it's hung... And then the ten scroll events happen. The delay is very inconsistent, which from a usability standpoint is worse. Instead of just knowing it lags, it has feel like I mistakenly tried to scroll with the wrong window focused. My guess is that there's some garbage collection or something that happens periodically, and if I scroll during it, it has to wait until the *whatever* job is done. I keep saying scrolling here because it's the most obvious case, but I'm pretty sure all browser operations freeze during the lag time. This started under 8.10, and seemed to get better when I first switched to 9.04, but it's happening all the time again now. When it gets really bad, Flash videos start having problems too where they'll freeze for several seconds, much like the scrolling freezes. Clicking links to open pages also seems to be affected, again having some sporadic lag. Sadly, Firefox on my old P3-600 with 8.04 feels more responsive than on 9.04 on my Athlon64-5200. If I exit when it's really bad, Firefox consumes 100% CPU for 10 to 20 seconds after the window closes, but before the process exits. The time seems to be related to how much trouble I'm having with the lag. It'd be awfully interesting to know what it's cleaning up during that time, but I don't know how to find out. I have a workaround that seems to make it somewhat better: kill firefox, delete localstore.rdf, restart. This seems to work better than just restarting, but it's really hard to do side by side comparisons, since it takes a while to build up to the nasty lag. I've gone through many gyrations of deleting my profile and reimporting my bookmarks, disabling plugins, and removing Flash, all to no avail. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0.10+nobinonly-0ubuntu0.9.04.1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.28-11-generic i686 ** Affects: firefox (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 -- Firefox lags when scrolling https://bugs.launchpad.net/bugs/383435 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox 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 1814125] Re: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked
seems that the bug disappears with all gnome extensions uninstalled. -- 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/1814125 Title: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu desktop (gnome-shell), no application running just activate second display in gnome tweak, let it lock itself the fan is going fast, simply moving the mouse and the fan slow down. wrote a simple script to append a top every minut in a log file, show that gnome-shell consumes 100% when locked. workaround : disabling second displaying and no more CPU usage / fan noise when locked. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 16:19:16 2019 DistUpgraded: 2018-12-30 21:42:17,971 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2018-06-08 (236 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=174e8747-a737-411b-bfaf-4e6795426fea ro quiet splash nouveau.runpm=0 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-30 (31 days ago) dmi.bios.date: 10/13/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0502 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813735] Re: dual taskbar ?
*** This bug is a duplicate of bug 1812407 *** https://bugs.launchpad.net/bugs/1812407 seems that the bug disappears with all gnome extensions uninstalled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1813735 Title: dual taskbar ? Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: when the computer stays locked for a long time (let's say, the whole night), a taskbar appears on top of the lock screen. when unlocked, it seems that there is 2 taskbars (with little margin differences, see attached screencast). config : ubuntu 18.10 standart ubuntu desktop dock configured at bottom no gnome extension activated many applications running (haven't done the test without apps running) apps are still launchable, only the margin difference is annoying. haven't tried to launch app from the lock screen, it may be a security issue. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 09:28:53 2019 DistUpgraded: 2018-10-22 03:09:20,483 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1215] InstallationDate: Installed on 2018-04-03 (300 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AB350M-Gaming 3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ea369caf-e759-4349-904a-b584e8d71d5b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-10-22 (99 days ago) dmi.bios.date: 12/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd12/25/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.1-0~c~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.1-0~c~padoka0 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1813735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
I can't reproduce the problem any more with 340 either: ~$ apt-cache policy nvidia-340 nvidia-340: Installed: 340.107-0ubuntu0.18.04.2 Candidate: 340.107-0ubuntu0.18.04.2 Version table: *** 340.107-0ubuntu0.18.04.2 400 400 http://archive.ubuntu.com/ubuntu bionic-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 340.107-0ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages 340.106-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages :~$ apt-cache policy xserver-xorg-hwe-18.04 xserver-xorg-hwe-18.04: Installed: 1:7.7+19ubuntu8~18.04.2 Candidate: 1:7.7+19ubuntu8~18.04.2 Version table: *** 1:7.7+19ubuntu8~18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
Does anyone knows if it works again with ubuntu 18.10? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815941] [NEW] Show the source field in overview for snaps and debs
Public bug reported: Upstream bug: https://gitlab.gnome.org/GNOME/gnome-software/issues/576 Currently, in the search view results, there is no way to tell whether an app is a snap or deb without opening the detailed view for the app. This can be especially helpful, when the same app is found in multiple sources. See the attached screenshot when searching for 'telegram desktop'. (Note that I have the flatpak plugin installed and added the Flathub repository.) Only the flatpak shows its source, the deb and snap do not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 18:28:03 2019 InstallationDate: Installed on 2018-11-29 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.8 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Results-no-source.png" https://bugs.launchpad.net/bugs/1815941/+attachment/5238689/+files/Results-no-source.png -- 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/1815941 Title: Show the source field in overview for snaps and debs Status in gnome-software package in Ubuntu: New Bug description: Upstream bug: https://gitlab.gnome.org/GNOME/gnome-software/issues/576 Currently, in the search view results, there is no way to tell whether an app is a snap or deb without opening the detailed view for the app. This can be especially helpful, when the same app is found in multiple sources. See the attached screenshot when searching for 'telegram desktop'. (Note that I have the flatpak plugin installed and added the Flathub repository.) Only the flatpak shows its source, the deb and snap do not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 18:28:03 2019 InstallationDate: Installed on 2018-11-29 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.8 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815172]
Just correcting a wrong comment (#2) I made: > It happens on both 32bit and 64bit installations. I asked the school that reported the issue on 64bit to check again, and they said they have a 32bit installation after all. So the problem has only been reported in 32bit installations; I don't know if it happened on 64bit. And btw everything is fixed now, thanks again to all. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815938] [NEW] 'Developer' and 'Uploader' fields are mixed for snaps
Public bug reported: Steps: 1. Start gnome-software 2. Search for GNOME Web 3. Select the snap package 4. Look at the 'Developer' field, where it shows 'Jeremy Bicha' ⇒ Jeremy is not the 'Developer', he is the 'Uploader'. 5. Go back and select the deb package 6. Look at the 'Developer' field, where it shows 'The GNOME Project' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 18:16:23 2019 InstallationDate: Installed on 2018-11-29 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.8 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1815938 Title: 'Developer' and 'Uploader' fields are mixed for snaps Status in gnome-software package in Ubuntu: New Bug description: Steps: 1. Start gnome-software 2. Search for GNOME Web 3. Select the snap package 4. Look at the 'Developer' field, where it shows 'Jeremy Bicha' ⇒ Jeremy is not the 'Developer', he is the 'Uploader'. 5. Go back and select the deb package 6. Look at the 'Developer' field, where it shows 'The GNOME Project' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 18:16:23 2019 InstallationDate: Installed on 2018-11-29 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.8 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Workaround: in ubuntu 18.4
Create an empty file /etc/NetworkManager/conf.d/10-globally-managed-devices.
Create an file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with
content:
network: {config: disabled}
Work for me,
--
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/1638842
Title:
network-manager does not manage ethernet and bluetooth interfaces when
Ubuntu 16.10 is installed using chroot/netboot method
Status in network-manager package in Ubuntu:
Won't Fix
Bug description:
Hello,
I installed Ubuntu 16.10 using a chroot. I use network-manager to
manage connections. My system is up-to-date (so I use network-manager
1.2.4-0ubuntu1).
Wifi works perfectly but I cannot connect to wired networks and using
my phone's Bluetooth connection. Corresponding devices are said to be
unmanaged by network-manager. nmcli dev outputs:
DEVICETYPE STATE CONNECTION
enp1s0ethernet unmanaged --
wlp2s0wifi disconnected --
6C:9B:02:2C:EE:2C btunmanaged --
hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged --
loloopback unmanaged --
The following command has no effect:
sudo nmcli dev set enp1s0 managed yes
I can connect to a wired connection by doing:
ifconfig enp1s0 up
dhclient enp1s0
There is nothing in the file /etc/network/interfaces.
Everything works perfectly if I downgrade network-manager to this
version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
(http://packages.ubuntu.com/xenial-updates/amd64/network-
manager/download). I had to install libreadline6 and downgrade nplan
to meet dependencies.
I don't know what to join to this bug report so please ask in case
anything is needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
Tested `sudo apt install xserver-xorg-hwe-18.04` after activating proposed in the affected machine. Now working as intended. Rebooted, checked Xorg version with `sudo X -version` (X.Org X Server 1.20.1) and run `nvidia-smi` showing driver 390.77 version and installed cards without any issues. So, this specific bug is fixed (I didn't test any further). ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04
[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed. ** Tags removed: verification-needed-bionic ** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
Yes, I understand that users will not see nemo, but the memory will :) But I get why nautilus is hard to let go. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
@Amr Ah, No. In users eye nemo won't even exist in Unity. We are only using nemo-desktop which is a separate binary to draw icons under unity, nothing else. It's difficult to remove nautilus completely as it is burried deep. It requires work on unity, unity-lens-files, hud, bamf, zeitgeist and in indicators. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815723] Re: Segmentation fault (core dumped)
*** This bug is a duplicate of bug 1814949 *** https://bugs.launchpad.net/bugs/1814949 ** This bug has been marked a duplicate of bug 1814949 gnome-control-center refuses to open if you try to open the Details panels -- 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/1815723 Title: Segmentation fault (core dumped) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Segmentation fault (core dumped) after upgrading to 3.31.90 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 11:29:40 2019 InstallationDate: Installed on 2018-02-15 (362 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2018-10-20 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
Thank you for the effort (I'm adding to my list to check why apport is
not working in that context)
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
Marco, sorry for my bad english) I installed packages from ppa:ci-train-ppa-service/3597, the problem disappeared, thanks. There is a new problem, attached a screenshot, on the right side of the window. -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815723] Re: Segmentation fault (core dumped)
*** This bug is a duplicate of bug 1814949 *** https://bugs.launchpad.net/bugs/1814949 I get the same error. Opening from the menu does nothing, using $ gnome-control-center or even $ gnome-control-center display as suggested above results in segmentation fault (core dumped). This is on a Dell XPS13 laptop running Disco Dingo dev branch. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1815723 Title: Segmentation fault (core dumped) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Segmentation fault (core dumped) after upgrading to 3.31.90 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 11:29:40 2019 InstallationDate: Installed on 2018-02-15 (362 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2018-10-20 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
It took some effort getting a backtrace (apport didn't pick it up, for
some reason, so I had to resort to systemd-corectl), but anyway, here is
is. I'll add it to the upstream bug, too.
** Attachment added: "backtrace.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+attachment/5238664/+files/backtrace.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
** Attachment added: "coredumpctl.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+attachment/5238665/+files/coredumpctl.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1815579 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04
[Desktop-packages] [Bug 1815480] Re: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
Ok, in fact I can confirm on cosmic and updating libarchive to the current disco version fixes it, https://launchpad.net/ubuntu/+source/libarchive/3.3.3-4/+build/16358983/+files/libarchive13_3.3.3-4_amd64.deb so it's fixed in the current Ubuntu serie. Could be a bug to SRU fix if someone was wanting to find the corresponding libarchive commit ** Package changed: nautilus (Ubuntu) => libarchive (Ubuntu) ** Changed in: libarchive (Ubuntu) Status: Incomplete => Fix Released -- 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/1815480 Title: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud Status in libarchive package in Ubuntu: Fix Released Bug description: For any .zip archive generated by the ownCloud software, it seems that extracting the files using Nautilus results in correctly-named directories/files to be created, but all files are actually empty (0 bytes). The archive can be extracted without issues using file-roller, unzip or 7z: $ unzip -t test.zip Archive: test.zip testing: test/OK testing: test/f1.txt OK testing: test/f2.txt OK testing: test/f3.txt OK No errors detected in compressed data of test.zip. $ unzip test Archive: test.zip creating: test/ extracting: test/f1.txt extracting: test/f2.txt extracting: test/f3.txt $ 7z x test.zip 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (306D4),ASM,AES-NI) Scanning the drive for archives: 1 file, 8656 bytes (9 KiB) Extracting archive: test.zip -- Path = test.zip Type = zip Physical Size = 8656 64-bit = + Everything is Ok Folders: 1 Files: 3 Size: 7850 Compressed: 8656 Expected behavior: Download the attached file “test.zip”, right-click the file in Nautilus and choose “Extract Here”. A directory “test” containing three non-empty files “f1.txt”, “f2.txt” and “f3.txt” should be created. Actual behavior: All three files are empty (0 bytes). Nautilus version: 1:3.26.4-0ubuntu7.1 (cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1815480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815579] Please test proposed package
Hello Leopoldo, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.77-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
Hello Leopoldo, or anyone else affected, Accepted nvidia-graphics-drivers-340 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.107-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following
[Desktop-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
Just a comment, does that mean that two file managers will always be run in the background? If so, why not just use nemo and drop nautilus completely? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771943] Re: nautilus accessing samba shares doesn't use cached credentials
Upstream posted a potential fix https://gitlab.gnome.org/GNOME/gvfs/merge_requests/34 Would you be able to rebuild a pacakge with that change to test it? If not we can build/provide one for testing, let us know -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1771943 Title: nautilus accessing samba shares doesn't use cached credentials Status in gvfs package in Ubuntu: Triaged Bug description: I don't know if the bug is in nautilus or other package but accessing samba shares in a samba domain membership authentication using winbind, nautilus doesn't try to use cached credentials to access network shares. Before the upgrade to ubuntu bionic (18.04) all works as expected. I have configured winbind bind module for samba authentication on a samba server and all seems works flawless. I have enabled winbind offline logon (in smb.conf) and cached credentials (in /etc/security/pam_winbind.conf). Offline logon seems to work but when I access samba shares, nautilus ask me for a username and password even if I log on using a valid domain account and this valid account can access the samba share. If you need some more info please ask me Have a great day Piviul ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 08:19:06 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'855x550+65+24'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2012-05-17 (2191 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-05-03 (15 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1771943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584388] Re: network manager doesn't parse openvpn argument with IP and port on the same line correctly network-manager-openvpn
Is that still an issue in Ubuntu 18.04? ** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager-openvpn (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1584388 Title: network manager doesn't parse openvpn argument with IP and port on the same line correctly network-manager-openvpn Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: When importing an OpenVPN configuration that contains a remote with an IP and port on the same line, for example: remote 1.2.3.4 1234 the port is not interpreted correctly after import (instead it imports the configuration with port 1194 instead). Description: Ubuntu 16.04 LTS Release: 16.04 network-manager-openvpn: Installed: 1.1.93-1ubuntu1 Candidate: 1.1.93-1ubuntu1 Version table: *** 1.1.93-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1584388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager
No, this does not affect 18.04, and likely does not affect later versions either. (Likely due to updated OVPN libraries and such?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1769991 Title: [16.04] Unable to import OpenVPN configuration into Network Manager Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- An example configuration that fails to import is as follows (with some critical components excluded, like a proper remote address, or a proper x509 name); this is a config that otherwise works with a Sophos XG Firewall-based SSL VPN system client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend. Note that the same configuration made by hand in the new VPN window works fine, but the import function fails. (Which is a pretty severe bug) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 14:59:54 2018 InstallationDate: Installed on 2016-12-20 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789092] Re: network-manager-openvpn fails if path contains a blank
Could also be https://bugzilla.gnome.org/show_bug.cgi?id=795601 , does https://launchpad.net/ubuntu/+source/network-manager- applet/1.8.10-2ubuntu2 fixes the issue? ** Bug watch added: GNOME Bug Tracker #795601 https://bugzilla.gnome.org/show_bug.cgi?id=795601 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1789092 Title: network-manager-openvpn fails if path contains a blank Status in network-manager-openvpn package in Ubuntu: Triaged Bug description: Ubuntu 18.04 OpenVPN Fails to start after import config from file, ie myfile.opvn CAUSE Folder path contains a blank: ~/owncloud/openvpn/My Settings/myfile.opvn WORKAROUND Renamed folder to ~/owncloud/openvpn/MySettings/myfile.opvn INSTALLED STEPS sudo apt-get install network-manager-openvpn openvpn sudo service network-manager restart sudo apt-get install openvpn network-manager-openvpn network-manager-openvpn-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1789092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager
This does however still affect 16.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1769991 Title: [16.04] Unable to import OpenVPN configuration into Network Manager Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- An example configuration that fails to import is as follows (with some critical components excluded, like a proper remote address, or a proper x509 name); this is a config that otherwise works with a Sophos XG Firewall-based SSL VPN system client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend. Note that the same configuration made by hand in the new VPN window works fine, but the import function fails. (Which is a pretty severe bug) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 14:59:54 2018 InstallationDate: Installed on 2016-12-20 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager
Is that still an issue in 18.04? ** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager-openvpn (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1769991 Title: [16.04] Unable to import OpenVPN configuration into Network Manager Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- An example configuration that fails to import is as follows (with some critical components excluded, like a proper remote address, or a proper x509 name); this is a config that otherwise works with a Sophos XG Firewall-based SSL VPN system client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend. Note that the same configuration made by hand in the new VPN window works fine, but the import function fails. (Which is a pretty severe bug) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 14:59:54 2018 InstallationDate: Installed on 2016-12-20 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806246] Re: Unable to turn off 2 and more openvpn-connections via Network Manager
What UI element do you use to turn those off? The gnome-shell menu should list each VPN with its own item having an 'off' action no? ** Changed in: network-manager-openvpn (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1806246 Title: Unable to turn off 2 and more openvpn-connections via Network Manager Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: Have some openvpn-connections. If started 2 or more connection and try to stop all connections, will stoped only last started connection. And first started connection unable to stop from GUI. Also unable to stop definite connection, only last started. Forced to use nmcli. Ubuntu 18.04. network-manager-1.10.6 network-manager-gnome-1.8.10 network-manager-openvpn-1.8.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1806246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789092] Re: network-manager-openvpn fails if path contains a blank
That's known upstream, https://gitlab.gnome.org/GNOME/NetworkManager- openvpn/issues/4 ** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => High ** Changed in: network-manager-openvpn (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1789092 Title: network-manager-openvpn fails if path contains a blank Status in network-manager-openvpn package in Ubuntu: Triaged Bug description: Ubuntu 18.04 OpenVPN Fails to start after import config from file, ie myfile.opvn CAUSE Folder path contains a blank: ~/owncloud/openvpn/My Settings/myfile.opvn WORKAROUND Renamed folder to ~/owncloud/openvpn/MySettings/myfile.opvn INSTALLED STEPS sudo apt-get install network-manager-openvpn openvpn sudo service network-manager restart sudo apt-get install openvpn network-manager-openvpn network-manager-openvpn-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1789092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796652] Re: nm-openvpn can't find ca.crt file when it's on a directory with a non-ASCII character
That looks similar to https://gitlab.gnome.org/GNOME/NetworkManager- openvpn/issues/4 ** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => High ** Changed in: network-manager-openvpn (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1796652 Title: nm-openvpn can't find ca.crt file when it's on a directory with a non- ASCII character Status in network-manager-openvpn package in Ubuntu: Triaged Bug description: nm-openvpn don't work when the ca.crt file is in a directory with a non ASCII name : nm-openvpn[30376]: Options error: --ca fails with '/home/username/T%C3%A9l%C3%A9chargements/config- 256bit/config/ca.crt': No such file or directory (errno=2) It's working when ca.crt is in /home/username directory surprisingly, no problem with the .opvn files which are in the same directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1796652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815125] Re: constant video freezes in firefox with x-x-v-amdgpu 18.1.0
I've tested it on a 'vega 8 mobile' laptop with glxgears. Without the fix the session would freeze periodically, after installing the update and restarting gnome-shell things work fine. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1815125 Title: constant video freezes in firefox with x-x-v-amdgpu 18.1.0 Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Bug description: [Impact] There are constant video freezes in firefox (e.g. on youtube) with xf86-video-amdgpu-18.1.0, which is included in the HWE stack in 18.04.2 https://bugs.freedesktop.org/show_bug.cgi?id=107992 [Test case] test firefox with youtube on radeon [Regression potential] it's a single commit from upstream 1.6.7, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1815125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => Critical ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Confirmed => Triaged ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided => Critical ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04
[Desktop-packages] [Bug 1800542] Re: OpenVPN connection not stable after upgrade to 18.10 (udp, ipv6)
Could you get a debug log as described on https://wiki.gnome.org/Projects/NetworkManager/Debugging #Debugging_NetworkManager-openvpn ? ** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => High ** Changed in: network-manager-openvpn (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1800542 Title: OpenVPN connection not stable after upgrade to 18.10 (udp, ipv6) Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: After upgrade to Ubuntu 18.10, my connection to my employer's VPN server has become unstable. The server provides both ipv4 and ipv6 endpoints. Since I have global ipv6 at home, my client defaults to connecting over ipv6. The connection consistently drops after only a few minutes of being connected. If I force the connection to use ipv4 (by hard-coding the host resolution in /etc/hosts), the connection is stable. If I use ipv6 and force proto-tcp=yes, the connection is stable. If I use the default ipv6 and udp, the connection is not stable. Using tcp for VPNs is suboptimal. Hard-coding addresses in /etc/hosts is suboptimal. This may be a bug in openvpn rather than in network-manager-openvpn, but I'm starting here. It's possible there are pathMTU issues involved, but I reproduced this same problem when I was on a different network from my home network (though I did not confirm, when I had access to this other network, that it was ipv6-enabled). I will work on getting more details about both sides of the network to try to debug this. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2010-09-24 (2957 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: network-manager-openvpn 1.8.6-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (11 days ago) UserGroups: adm admin cdrom dialout docker libvirt libvirtd lpadmin lxd mythtv plugdev sambashare sbuild src sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1800542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806246] Re: Unable to turn off 2 and more openvpn-connections via Network Manager
** Package changed: network-manager (Ubuntu) => network-manager-openvpn (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1806246 Title: Unable to turn off 2 and more openvpn-connections via Network Manager Status in network-manager-openvpn package in Ubuntu: New Bug description: Have some openvpn-connections. If started 2 or more connection and try to stop all connections, will stoped only last started connection. And first started connection unable to stop from GUI. Also unable to stop definite connection, only last started. Forced to use nmcli. Ubuntu 18.04. network-manager-1.10.6 network-manager-gnome-1.8.10 network-manager-openvpn-1.8.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1806246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809614] Re: Lubuntu 18.04 ICS not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1809614 Title: Lubuntu 18.04 ICS not working Status in network-manager package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.1 Candidate: 1.10.6-2ubuntu1.1 Version table: *** 1.10.6-2ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ICS does NOT work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
Reported upstream also on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/124
, they might have a clue even without the backtrace
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740869] Re: is not responding window is constantly showing when debugging a program
Same issue. Ubuntu 18.04.1 + Visual Code while debugging OpenGL app. Please increase the priority. -- 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/1740869 Title: is not responding window is constantly showing when debugging a program Status in mutter package in Ubuntu: Confirmed Bug description: Mentioned window about no responding program is showing and stealing focus when I try to debug a Java program in Eclipse. When I click on Wait, it disappears for a moment and opens again. This renders Ubuntu 17.10 with Gnome 3 nearly useless for program debugging. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 2 14:22:56 2018 InstallationDate: Installed on 2017-12-04 (28 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772919] Re: pam-gnome-keyring.so reveals user’s password credential as a plaintext form
** Also affects: gnome-keyring (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-keyring (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: gnome-keyring (Ubuntu) Status: New => Fix Released ** Changed in: gnome-keyring (Ubuntu Trusty) Status: New => Confirmed ** Changed in: gnome-keyring (Ubuntu Xenial) Status: New => Confirmed -- 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/1772919 Title: pam-gnome-keyring.so reveals user’s password credential as a plaintext form Status in gnome-keyring package in Ubuntu: Fix Released Status in gnome-keyring source package in Trusty: Confirmed Status in gnome-keyring source package in Xenial: Confirmed Bug description: When I perform memory dump of session-child process, user’s login credential, including user accounts and their password, is revealed as a plaintext form. In ‘pam_sm_authenticate’ function, user’s password is stored in the heap memory of ‘pam_handle->data” to perform unlock the keyring in later. After unlocking the keyring, the pam module does not free/overwrite the memory area though the password is no longer used. We thus could find user’s login credentials. This raises concerns over the credential being misused for illegal behavior, such as acquiring user’s session key. It would be better to clean the heap memory. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 23 22:53:12 2018 InstallationDate: Installed on 2018-04-20 (32 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) upstart.gnome-keyring-ssh.log: grep: /home/sungjungk/.config/autostart/gnome-keyring-ssh.desktop: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1772919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
** Description changed: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0 Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu - ExtraDebuggingInterest: No + ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 -- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak Status in xorg package in Ubuntu: New Bug description: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is
[Desktop-packages] [Bug 1771943] Re: nautilus accessing samba shares doesn't use cached credentials
Il 14/02/19 11:20, Sebastien Bacher ha scritto:> Upstream comment > > 'smbc_new_context() calls smbc_setOptionUseCCache(context, True) if > LIBSMBCLIENT_NO_CCACHE environemnt variable is not defined. I suppose it > is not defined in your system, but can you please confirm it?is it correct to > test if there is such a variable set in the user environment? This command $ env | grep SMB; echo $? 1 answers your question? > [...] > I am not sure how exactly is ccache authentication handled, but first > iteration uses smbc_setOptionFallbackAfterKerberos (smb_context, > op_backend->user != NULL). I wonder if it helps to specify the username > in the URI, e.g. gio mount smb://username@server/share?' there is no difference with or without the username from the command gio mount... in both cases ask me a password and if I press return without typing a password or I press Ctrl-c the share is correctly mounted... If you need some more infos or do you want to suggest me something else please let me know Piviul -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1771943 Title: nautilus accessing samba shares doesn't use cached credentials Status in gvfs package in Ubuntu: Triaged Bug description: I don't know if the bug is in nautilus or other package but accessing samba shares in a samba domain membership authentication using winbind, nautilus doesn't try to use cached credentials to access network shares. Before the upgrade to ubuntu bionic (18.04) all works as expected. I have configured winbind bind module for samba authentication on a samba server and all seems works flawless. I have enabled winbind offline logon (in smb.conf) and cached credentials (in /etc/security/pam_winbind.conf). Offline logon seems to work but when I access samba shares, nautilus ask me for a username and password even if I log on using a valid domain account and this valid account can access the samba share. If you need some more info please ask me Have a great day Piviul ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 08:19:06 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'855x550+65+24'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2012-05-17 (2191 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-05-03 (15 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1771943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
I'm sorry, what you mean by "layout"? -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667208] Re: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
Note that when using python{,3}-selenium, the default path can be
overridden like that:
from selenium import webdriver
driver =
webdriver.Chrome(executable_path="/usr/lib/chromium-browser/chromedriver")
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1667208
Title:
Ubuntu's selenium hardcodes a path that is valid for Debian, but not
for Ubuntu
Status in chromium-browser package in Ubuntu:
Confirmed
Status in python-selenium package in Ubuntu:
Invalid
Bug description:
Hi.
The package python{,3}-selenium uses a hardcoded path of
'/usr/lib/chromium/chromedriver' when instantiating a Chrome
webdriver.
That path is correct for Debian (in particular, it was directly
inherited from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=805733#5), but since Ubuntu uses chromium-
browser instead of Debian's chromium naming. The package chromium-
chromedriver in Ubuntu installs the webdriver at '/usr/lib/chromium-
browser/chromedriver'.
There needs to be a synchronization between the selenium Python module
and the webdriver package.
Thanks,
Rogério Brito.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: python3-selenium 2.53.2+dfsg1-1
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 23 01:38:24 2017
Dependencies:
InstallationDate: Installed on 2016-12-11 (73 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64
(20161012.1)
PackageArchitecture: all
SourcePackage: python-selenium
UpgradeStatus: Upgraded to zesty on 2017-01-31 (23 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667208/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764995] Re: Full text search in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
*** This bug is a duplicate of bug 1767817 *** https://bugs.launchpad.net/bugs/1767817 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1764995 Title: Full text search in nautilus 3.26.3 doesn't work (Ubuntu 18.04) Status in nautilus package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) nautilus: Installed: 1:3.26.3-0ubuntu3 Jelölt:1:3.26.3-0ubuntu3 Verziótáblázat: *** 1:3.26.3-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) I upgraded to Ubuntu 18.04 in one of my computers and made a brand new installation of Ubuntu 18.04 on another computer. In the latter I used minimal installation. I installed tracker too. When tracker finished building the index database I tried to search for something in nautilus. Full text search didn't work, I just got hits for the file names (fts is on). Command line search is working (tracker search ) The problem is the same in both computers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1764995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815894] Re: the modem itself is recognized by modem-manger but fail to connect to Internet (USB Modem HUAWEL E173)
please your help if there is any solution -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1815894 Title: the modem itself is recognized by modem-manger but fail to connect to Internet (USB Modem HUAWEL E173) Status in modemmanager package in Ubuntu: New Bug description: modem manger not working with usb modem Huawei E173 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 12:52:34 2019 InstallationDate: Installed on 2018-10-18 (118 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1815894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
Did anyone manage to get a clue on where is that problem coming from? Ubuntu? Nautilus? Gnome? and how to solve it? It is very annoying! I have Ubuntu 18.04.2 LTS Nautilus 3.26.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815894] [NEW] the modem itself is recognized by modem-manger but fail to connect to Internet (USB Modem HUAWEL E173)
Public bug reported: modem manger not working with usb modem Huawei E173 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 12:52:34 2019 InstallationDate: Installed on 2018-10-18 (118 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: modemmanager (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 modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1815894 Title: the modem itself is recognized by modem-manger but fail to connect to Internet (USB Modem HUAWEL E173) Status in modemmanager package in Ubuntu: New Bug description: modem manger not working with usb modem Huawei E173 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 12:52:34 2019 InstallationDate: Installed on 2018-10-18 (118 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1815894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
In the mean time, could `widget.content.gtk-theme-override` be set to `Adwaita` by default? This would fix the issue (except for the settings page), and Adwaita is always present on systems with GTK+. I opened https://bugzilla.mozilla.org/show_bug.cgi?id=1527048 for this change, everyone please go comment on that bug :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
So I think it would be useful to know, for the current round of complaints, are the problems the result of: 1. Firefox incorrectly gets data out of the GTK theme, so that its default appearance for controls doesn't match the native one, or 2. Firefox gets the data out of the theme correctly, but then web pages override one but not both of color and background (while assuming that color is dark and background is light), leading to an unreadable result We've had both problems in the past, and it would be useful to know which of them is happening in the set of problems that have spiked in the past few months. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
David: The problem here is point 2. Just setting `widget.content.gtk- theme-override` to `Adwaita` by default would fix this for web pages, but the General -> Startup section of the Settings page still looks wrong (white text on a white background), along with a couple of other spots in Settings, despite setting this pref. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
I use this extension as a workaround: [fix-dark-theme-input- boxes](https://addons.mozilla.org/en-US/firefox/addon/fix-dark-theme- input-boxes/) ([source](https://gitlab.com/Roboe/userscripts/tree/master /fix-dark-theme-input-boxes/)) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263] Re: Bad Firefox integration with dark themes
** Bug watch added: Mozilla Bugzilla #1527048 https://bugzilla.mozilla.org/show_bug.cgi?id=1527048 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu1
---
pulseaudio (1:12.2-2ubuntu1) disco; urgency=medium
* Add steelseries headset support. This provides sufficient support to
enable the Steelseries Arctis 5 and 7 Gaming Headsets (LP: #1758736).
-- Dave Chiluk Tue, 12 Feb 2019 00:50:27 -0600
** Changed in: pulseaudio (Ubuntu Disco)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
mono playback
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
In Progress
Status in pulseaudio source package in Cosmic:
In Progress
Status in pulseaudio source package in Disco:
Fix Released
Bug description:
[Impact]
* User is only able to get mono audio from steelseries headsets
because they provide both a stereo and mono output. PA selects the
mono output by default.
* This should be backported to stable releases because this fix is
isolated to code that only applies to the affected headsets.
Additionally other gaming headsets may be more easily enabled by adding
ATTRS{idVendor}=="", ATTRS{idProduct}=="",
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
to /lib/udev/rules.d/90-pulseaudio.rules now. Such as the Lucidsound
LS31 which I own.
* The upload fixes the bug by conditionally setting a pulseaudio
profile for the headset based on specific usb vendor and product ids
in the udev rules.
[Test Case]
1. Acquire headset.
2. Open sound settings, and click test speakers.
3. Only option available will be mono sound
[Regression Potential]
* Risk of regressions should be mitigated to those who own the
headset. In which case it is likely that their headset is already not
working.
[Other Info]
* All patches originate from upstream pulseaudio, and are documented as
such including the shas.
* I will be pursuing enabling other similar headsets in the coming weeks.
* I plan to work with upstream pulseaudio to enable my own headset and to
also make the headset templates backported here more generic.
Original Description -
There is not stereo playback only mono playback
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio
/dev/snd/controlC1: kaj1755 F pulseaudio
/dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio
/dev/snd/controlC0: kaj1755 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 21:30:50 2018
InstallationDate: Installed on 2018-03-08 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET35W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS2AV00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS2AV00
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815890] Re: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
*** This bug is a duplicate of bug 1814949 *** https://bugs.launchpad.net/bugs/1814949 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 #1814949, 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/1815890/+attachment/5238603/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1815890/+attachment/5238605/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1815890/+attachment/5238609/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1815890/+attachment/5238610/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1815890/+attachment/5238611/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1815890/+attachment/5238612/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1815890/+attachment/5238613/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1814949 gnome-control-center refuses to open if you try to open the Details panels ** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1815890 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() Status in gnome-control-center package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 11:29:38 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2014-07-15 (1675 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: gnome-control-center sound SegvAnalysis: Segfault happened at: 0x7f796021732d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f796021732d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-03-24 (326 days ago) UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815752] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815752 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I installed new kernel from xenial-proposed and this happened. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.104-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 318706/1281120 files, 2426738/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-143-generic Date: Wed Feb 13 12:18:21 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv-linux.h:2161:9: error: too many arguments to function ‘get_user_pages’ GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1179 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.104-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 13 12:57:38 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1815752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815752] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build
Hello. There is a similar raport about failed 'nvidia_304' module build on latest '-proposed' v4.4.0-143-generic kernel: ✗ https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-304/+bug/1815858 Mentioned issue happened on both: amd64 and i385/i686 architectures. Best regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815752 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I installed new kernel from xenial-proposed and this happened. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.104-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 318706/1281120 files, 2426738/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-143-generic Date: Wed Feb 13 12:18:21 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv-linux.h:2161:9: error: too many arguments to function ‘get_user_pages’ GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1179 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.104-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 13 12:57:38 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1815752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771943] Re: nautilus accessing samba shares doesn't use cached credentials
Upstream comment 'smbc_new_context() calls smbc_setOptionUseCCache(context, True) if LIBSMBCLIENT_NO_CCACHE environemnt variable is not defined. I suppose it is not defined in your system, but can you please confirm it? smbclient --kerberos --use-ccache doesn't work as it forces kerberos to be used, however gvfs uses smbc_setOptionFallbackAfterKerberos (op_backend->smb_context, 1), which I suppose should fallback to ccache as well. It would be nice to confirm that downgrade of samba/gvfs package solves the problem, to figure out where is the regression. In theory, we could break something by the commit a0aec329, but it is 4 years old. I am not sure how exactly is ccache authentication handled, but first iteration uses smbc_setOptionFallbackAfterKerberos (smb_context, op_backend->user != NULL). I wonder if it helps to specify the username in the URI, e.g. gio mount smb://username@server/share?' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1771943 Title: nautilus accessing samba shares doesn't use cached credentials Status in gvfs package in Ubuntu: Triaged Bug description: I don't know if the bug is in nautilus or other package but accessing samba shares in a samba domain membership authentication using winbind, nautilus doesn't try to use cached credentials to access network shares. Before the upgrade to ubuntu bionic (18.04) all works as expected. I have configured winbind bind module for samba authentication on a samba server and all seems works flawless. I have enabled winbind offline logon (in smb.conf) and cached credentials (in /etc/security/pam_winbind.conf). Offline logon seems to work but when I access samba shares, nautilus ask me for a username and password even if I log on using a valid domain account and this valid account can access the samba share. If you need some more info please ask me Have a great day Piviul ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 08:19:06 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'855x550+65+24'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2012-05-17 (2191 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-05-03 (15 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1771943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815883] Re: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
*** This bug is a duplicate of bug 1814949 *** https://bugs.launchpad.net/bugs/1814949 ** Information type changed from Private to Public -- 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/1815883 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() Status in gnome-control-center package in Ubuntu: New Bug description: Crashes when I click on details then cannot launch it again. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 10:52:25 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2014-07-15 (1675 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f192395232d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f192395232d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-03-24 (326 days ago) UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628032] Re: evolution-calendar-factory-subprocess crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
The issue saw not report since 17.10 according to the error tracker, closing ** Changed in: evolution-data-server (Ubuntu) Status: Confirmed => Fix Released ** Information type changed from Private to Public -- 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/1628032 Title: evolution-calendar-factory-subprocess crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in evolution-data-server package in Ubuntu: Fix Released Bug description: This is an automatic bug report. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: evolution-data-server 3.21.91-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 17:21:52 2016 ExecutablePath: /usr/lib/evolution/evolution-calendar-factory-subprocess InstallationDate: Installed on 2015-08-05 (418 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/evolution/evolution-calendar-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2625x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2625/3 ProcEnviron: LANG=ru_RU.UTF-8 LANGUAGE=ru PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f3ad07f085c : movzbl 0x14(%rax),%edx PC (0x7f3ad07f085c) ok source "0x14(%rax)" (0x55ac0014) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: evolution-calendar-factory-subprocess crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1628032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685037] Re: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver
*** This bug is a duplicate of bug 1667208 *** https://bugs.launchpad.net/bugs/1667208 and looks really similar to 1685037 ** This bug has been marked a duplicate of bug 1667208 Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1685037 Title: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver Status in chromium-browser package in Ubuntu: Fix Released Status in python-selenium package in Ubuntu: Fix Released Bug description: In Xenial this package suggests two other packgages: chromedriver and firefoxdriver. These packgages are not available in Xenial. Only Chromium-chromedriver is. Unfortunately, python-selenium does not provide webdrivers, so they have to be installed separately. Why aren’t they available? This greatly hampers the usefulness of python-selenium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1685037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685037] Re: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver
*** This bug is a duplicate of bug 1667208 *** https://bugs.launchpad.net/bugs/1667208 This is ongoing to be fixed in disco, feel free to convert in an SRU. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released ** Changed in: python-selenium (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1685037 Title: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver Status in chromium-browser package in Ubuntu: Fix Released Status in python-selenium package in Ubuntu: Fix Released Bug description: In Xenial this package suggests two other packgages: chromedriver and firefoxdriver. These packgages are not available in Xenial. Only Chromium-chromedriver is. Unfortunately, python-selenium does not provide webdrivers, so they have to be installed separately. Why aren’t they available? This greatly hampers the usefulness of python-selenium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1685037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667208] Re: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
This will be fixed in chromium itself, to behave how Debian does
** Package changed: python-selenium (Ubuntu) => chromium (Ubuntu)
** Package changed: chromium (Ubuntu) => chromium-browser (Ubuntu)
** Also affects: python-selenium (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-selenium (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1667208
Title:
Ubuntu's selenium hardcodes a path that is valid for Debian, but not
for Ubuntu
Status in chromium-browser package in Ubuntu:
Confirmed
Status in python-selenium package in Ubuntu:
Invalid
Bug description:
Hi.
The package python{,3}-selenium uses a hardcoded path of
'/usr/lib/chromium/chromedriver' when instantiating a Chrome
webdriver.
That path is correct for Debian (in particular, it was directly
inherited from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=805733#5), but since Ubuntu uses chromium-
browser instead of Debian's chromium naming. The package chromium-
chromedriver in Ubuntu installs the webdriver at '/usr/lib/chromium-
browser/chromedriver'.
There needs to be a synchronization between the selenium Python module
and the webdriver package.
Thanks,
Rogério Brito.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: python3-selenium 2.53.2+dfsg1-1
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 23 01:38:24 2017
Dependencies:
InstallationDate: Installed on 2016-12-11 (73 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64
(20161012.1)
PackageArchitecture: all
SourcePackage: python-selenium
UpgradeStatus: Upgraded to zesty on 2017-01-31 (23 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667208/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801494] Re: dock missing
Same here. Everytime I resume my session after lock, I lose the Dock. Reenabling the extension in Tweaks didn't do anything. Dock still is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1801494 Title: dock missing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.1 Candidate: 0.9.1ubuntu18.04.1 Version table: *** 0.9.1ubuntu18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 4) dock is there 5) dock is not there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667208] [NEW] Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
You have been subscribed to a public bug:
Hi.
The package python{,3}-selenium uses a hardcoded path of
'/usr/lib/chromium/chromedriver' when instantiating a Chrome webdriver.
That path is correct for Debian (in particular, it was directly
inherited from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=805733#5), but since Ubuntu uses chromium-browser
instead of Debian's chromium naming. The package chromium-chromedriver
in Ubuntu installs the webdriver at '/usr/lib/chromium-
browser/chromedriver'.
There needs to be a synchronization between the selenium Python module
and the webdriver package.
Thanks,
Rogério Brito.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: python3-selenium 2.53.2+dfsg1-1
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 23 01:38:24 2017
Dependencies:
InstallationDate: Installed on 2016-12-11 (73 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitecture: all
SourcePackage: python-selenium
UpgradeStatus: Upgraded to zesty on 2017-01-31 (23 days ago)
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug zesty
--
Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
https://bugs.launchpad.net/bugs/1667208
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser 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 1815881] Re: Installation fails if update-notifier is missing
II fact that's not an issue in 18.10, it was created in Debian by dropping the exit 0 call ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu) 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/1815881 Title: Installation fails if update-notifier is missing Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact THe postinst doesn't handle update-notifier not being installed * Test case - remove update-notifier - install evolution-data-server The installation should not error out in the postinst * Regression potential The change is only to add a || true to the update-notifier command in the postinst, it shouldn't impact on anything (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911603) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers
** Description changed: + * Impact + Evolution doesn't work with Kopano IMAP servers: + + * Test case + Configure an account on a Kopano IMAP server and try to use it from evolution + + * Regression potential + The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly + + - + 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. -- 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/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact Evolution doesn't work with Kopano IMAP servers: * Test case Configure an account on a Kopano IMAP server and try to use it from evolution * Regression potential The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly - 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815881] [NEW] Installation fails if update-notifier is missing
Public bug reported: * Impact THe postinst doesn't handle update-notifier not being installed * Test case - remove update-notifier - install evolution-data-server The installation should not error out in the postinst * Regression potential The change is only to add a || true to the update-notifier command in the postinst, it shouldn't impact on anything (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911603) ** Affects: evolution-data-server (Ubuntu) Importance: Low Status: 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/1815881 Title: Installation fails if update-notifier is missing Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact THe postinst doesn't handle update-notifier not being installed * Test case - remove update-notifier - install evolution-data-server The installation should not error out in the postinst * Regression potential The change is only to add a || true to the update-notifier command in the postinst, it shouldn't impact on anything (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911603) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers
The fix is in the current disco version and being SRUed to 18.10 ** Changed in: evolution-data-server (Ubuntu) Status: Fix Committed => 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/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Bug description: 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815882] [NEW] Update evolution-data-server to 3.30.5
Public bug reported: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. ** Affects: evolution-data-server (Ubuntu) Importance: High Status: Fix Released ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => High ** Changed in: evolution-data-server (Ubuntu) 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/1815882 Title: Update evolution-data-server to 3.30.5 Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 704789]
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103 -- 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/704789 Title: [Upstream] Calc makes cells protected when it shouldn't Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Calc via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/704789/+attachment/3075997/+files/Test%20case.ods -O example.ods && localc --nologo example.ods open www.ubuntu.com in a web browser, copy "Fast, secure and stylishly simple," into A1, then try to delete the pasted text and it is deleted. 4) What happens instead is the text isn't deleted and the cell becomes protected. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openoffice.org-calc 1:3.2.1-7ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-25.43-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 Architecture: i386 Date: Tue Jan 18 16:02:24 2011 ProcEnviron: LANGUAGE=pl_PL:pl:en_GB:en PATH=(custom, no user) LANG=pl_PL.utf8 SHELL=/bin/bash SourcePackage: openoffice.org --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 DistroRelease: Ubuntu 11.10 Package: libreoffice-calc 1:3.4.5-0ubuntu1 PackageArchitecture: i386 ProcEnviron: LANGUAGE=pl_PL:pl:en_GB:en PATH=(custom, user) LANG=pl_PL.UTF-8 SHELL=/bin/bash Tags: oneiric Uname: Linux 3.3.0-030300-generic i686 UpgradeStatus: Upgraded to oneiric on 2011-10-18 (180 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/704789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
