Ok, I got it.
In my case error was thrown by libmkl_intel_thread.so, it dlopen() libiomp5.so.
This thread describes the reason:
https://software.intel.com/en-us/forums/intel-math-kernel-library/topic/402497
So I chose the wrong package, must be libmkl-rt.
--
You received this bug
Hi!
This doesn't really matter.
I'm building dlib (http://dlib.net/) with Intel MKL libraries. One of them
loads libiomp5.so dynamically and that causes "undefined symbol" error. Real
reason or error -- wrong packaging.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Recently I built a library with Intel MKL as a dependency (libmkl-dev
package). Trying to run an application threw me an error message:
"undefined symbol: omp_get_num_procs". The problem turned up to be old
and known (https://software.intel.com/en-us/forums/intel-system-
WTF??? Does this mean you want to get rid of the problem without solving
it?
There is definitely a dependency problem either in libgl1-mesa-dri:i386 or in
libllvm7:i386.
==
$ apt policy
Package files:
100
Results (using btrfs-compsize tool):
$ sudo compsize /boot/ /bin/ /usr/
Processed 240794 files, 88025 regular extents (89183 refs), 162022 inline.
Type Perc Disk Usage Uncompressed Referenced
TOTAL 50% 2.7G 5.3G 5.4G
none 100% 1.1G
Seems that btrfs ignores compression attribute if compression was set using
mount option.
So, the solution is to set compression attributes per-directory:
1) remove 'compress=zstd' from your fstab root record
2) sudo btrfs property set /boot compression lzo # ensure this dir will remain
Public bug reported:
I get the following output in console:
dmig@dmig-Inspiron-5379:~$ gedit workspace/howdy-test.py
Traceback (most recent call last):
File "/usr/lib/x86_64-linux-gnu/gedit/plugins/git/appactivatable.py", line
89, in get_repository
repo = self.__git_repos[repo_uri]
Public bug reported:
Steam client tries to install a set of i386 libraries. One of them is
libgl1-mesa-dri:i386.
But since upgrade to Ubuntu 18.10 this package got broken dependency and thus
installation fails.
>The following packages have unmet dependencies:
> libgl1-mesa-dri:i386 : Depends:
The simplest workaround for the moment:
sudo btrfs property set /boot compression lzo # ensure this dir will remain
readable by grub
sudo btrfs filesystem defragment -vr /boot # ensure /boot gets recompressed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Started experiencing this bug after Ubuntu update 18.04->18.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697229
Title:
GNOME extensions deactivated after lock unlock
To manage notifications
How to check you have this issue:
1) get provided resume script, replace
/usr/share/initramfs-tools/scripts/local-premount/resume with it
2) sudo update-initramfs -k $(uname -r) -u
3) sudo systemctl hibernate
4) edit grub menu entry, add 'debug' parameter to kernel command line, boot
5) look
Here is a fix for this bug. This makes hibernation functional for me.
** Patch added: "init.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+attachment/5134187/+files/init.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug is actually a regression. I remember hibernation was functional
around a year ago in ubuntu 17.04 with any kernel, but at some point it
became broken. Probably in 17.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I found a reason of non-functioning resume from hibernation when resume
partition/file is autodetected by intiramfs hook /usr/share/initramfs-
tools/hooks/resume.
Here is the scenario:
1) hook /usr/share/initramfs-tools/hooks/resume creates config
conf/conf.d/zz-resume-auto
Confirmation by other person
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/comments/8
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Enough guessing. Gnome bug is a different one. And it has no connection
to this bug.
In my case rfkill didn't work because keycode 88 was set to UNKNOWN by
this generic dell rule:
https://github.com/systemd/systemd/blob/c5896b6a8cfcfd1b94f25450a96a1411384f1108/hwdb/60-keyboard.hwdb#L267
My rule
Rfkill key produces 2 events: keyboard and one, that should be handled
by dell-wmi.
Hwdb record is for keyboard event. Release emulation is required, at
least for my model. Otherwise evtest shows only 1 EV_KEY event.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I found one more missing key definition: FN-Lock key - Lock icon with
'Fn' on it, it toggles Fn row behavior between F1-F12 and media keys.
I'm not sure with keycode it should have assigned, so I set it to IGNORE
in patch.
** Summary changed:
- dell_wmi: Unknown key with type 0x0010 and code
Until systemd gets updated, following file can be used. Put it to
/etc/udev/hwdb.d
** Attachment added: "my-rfkill.hwdb"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1762382/+attachment/5116245/+files/my-rfkill.hwdb
--
You received this bug notification because you are a member of
Pull request merged upstream:
https://github.com/systemd/systemd/pull/8715
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762382
Title:
scan code → meaning map
To manage notifications about this
Donal don't write such silly things. This patch is intended to fix that
behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763588
Title:
package trousers 0.3.14+fixed1-1build1 failed to
This fixes script error:
Apr 13 13:27:13 dmig-Inspiron-5379 trousers[18286]: /etc/init.d/trousers: 32:
[: /dev/tpm0: unexpected operator
** Patch added: "fix-check.patch"
https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1763588/+attachment/5113365/+files/fix-check.patch
--
You
Public bug reported:
Here is piece of install log:
Setting up trousers (0.3.14+fixed1-1build1) ...
Job for trousers.service failed because the control process exited with error
code.
See "systemctl status trousers.service" and "journalctl -xe" for details.
invoke-rc.d: initscript trousers,
Public bug reported:
I'm reporting this as duplicate of #1176536 to provide more info.
dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service
● ureadahead.service - Read required files in advance
Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor
preset:
According to
https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-wmi.c
this key isn't supported by kernel.
To add support record { KE_IGNORE, 0xe008, { KEY_RFKILL } } must be added to
array dell_wmi_keymap_type_0010. Right now it exists only in
dell_wmi_keymap_type_.
Public bug reported:
syslog contains following error messages:
Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: /etc/modprobe.d is not a
file
Apr 13 10:31:36 dmig-Inspiron-5379
Public bug reported:
udisks daemon complains about loading libbd_crypto and libbd_mdraid, but
seems to work fine.
I fixed the issue by manually installing packages libblockdev-crypto2
and libblockdev-mdraid2.
udisks should depend on these packages or doesn't complain about missing
libraries.
** Attachment added: "console output showing problem and solution"
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1763577/+attachment/5113324/+files/console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like, this key is supported by systemd, but for another model:
https://github.com/systemd/systemd/blob/master/hwdb/60-keyboard.hwdb#L321
So, new DMI match string should be added
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
RFKill key produces these messages in kernel log:
dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
This key code is a notification and should be added as KEY_IGNORE here:
https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-
wmi.c#L263
Public bug reported:
RFKILL key is unsupported on new Dell Inspiron 5379
Event: time 1523271211.046483, type 4 (EV_MSC), code 4 (MSC_SCAN), value 88
Event: time 1523271211.046483, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 2
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udev
Public bug reported:
'Add Custom Shortcut' dialog (Settings -> Keyboard -> '+' at the end of
list) never sets focus to 'Set Shortcut...' and 'Add' buttons if used
from keyboard.
Current field order is: 'Name' -> 'Command' -> 'Cancel' button.
Tab key switches focus only between these 3 fields.
@benbuntu, @darkdragon-001 see here: http://bazaar.launchpad.net
/~ubuntu-branches/ubuntu/vivid/apt-btrfs-
snapshot/vivid/view/head:/apt_btrfs_snapshot.py#L194
Author uses atime of /etc/fstab inside the snapshot to know it's creation time.
- Simplest fix would be to exclude `noatime` from mount
In my case error messages look like
Nov 18 07:50:34 kernel: do_general_protection: 14 callbacks suppressed
Nov 18 07:50:34 kernel: traps: gnome-shell[1430] general protection
ip:7f3f663c2e0d sp:7ffe9fed66d0 error:0 in libgobject-2.0.so.0.5400.1[7f3f6638
--
You received this bug notification
ubuntu-bug complains that there is not enough free memory to analyze
crash dump. I'm attaching the dump itself.
** Attachment added: "_usr_bin_gnome-shell.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730554/+attachment/5010747/+files/_usr_bin_gnome-shell.1000.crash
Public bug reported:
Steps to reproduce: launch meld as super user
dmig@dmig-tablet:~$ sudo meld
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
2017-10-20 10:50:27,383 CRITICAL
Public bug reported:
The reason was that /boot/efi partition wasn't mounted. Solved by
mounting manually and running dpkg --configure -a
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: shim-signed 1.32+0.9+1474479173.6c180c6-1ubuntu1
Uname: Linux 4.13.7-041307-generic x86_64
Some sort of workaround:
1) add udev rule /etc/udev/rules.d/90-backlight.rules:
ACTION=="add", SUBSYSTEM=="backlight", RUN+="/bin/chgrp video
/sys/class/backlight/%k/brightness"
ACTION=="add", SUBSYSTEM=="backlight", RUN+="/bin/chmod g+w
/sys/class/backlight/%k/brightness"
2) add yourself to
xbacklight output: No outputs have backlight property
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638136
Title:
xbacklight not working in ubuntu 16.10
To manage notifications about this bug go
No, that's not a workaround. Bug appeared again after several hibernate-resume
cycles.
I never seen this bug with xubuntu 15.10, kernel 4.5 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ and latest Intel graphics from
01.org. But it appeared after installing 16.04.
I'll try latest kernel
I think, I found better workaround: after I changed lightdm
configuration using 'lightdm greeter settings', I don't face this bug
anymore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568604
Title:
Public bug reported:
This occurred during apt-get dist-upgrade after clean install
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fontconfig 2.11.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Why are you guys marking the g-p-m bug invalid?
Because see previous comments.
g-s-d handles media keys. This bug is appeared, because we have a case, when
g-s-d should handle brightness keys differently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In order for this patch to apply properly, it should be applied last,
after all ubuntu patches. In you case you don't have any of them
applied.
If you got package from packages.ubuntu.com, there are 2 source files:
one http://archive.ubuntu.com/ubuntu/pool/main/g/gnome-settings-daemon
Patch 16_use_synchronous_notifications.patch -- is the one, that my patch
heavily depends on.
Also, as far, as I understand, it's incompatible with debian.
To make patch for debian, I need to understand, where to get correct
params for update_screen_cb(), to call it from
Hmm... really strange.
I made patch ubuntu 11.10, g-s-d 3.2.2-0ubuntu2.1. May be you upgraded to 12.04
already?
Actually, I should make patch for 12.04, as it's latest stable now. Will do
this bit later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I didn't write instruction:
- put the file into debian/patches/ dir
- add line 52_brightness_in_hardware.patch to 'series' file in that dir (not
sure if this step is required)
- build package as usual
This patch should be applied last, after all ubuntu/debian patches.
That's why it fails.
Here is the patch. Please review it.
** Patch added: 52_brightness_in_hardware.patch
https://bugs.launchpad.net/archlinux/+source/gnome-power-manager/+bug/527157/+attachment/3063911/+files/52_brightness_in_hardware.patch
--
You received this bug notification because you are a member of
My patch is similar to one in comment #15.
Differences are:
- it uses gsettings api (commonly used by g-s-d now)
- it doesn't break StepUp/StepDown dbus methods
- it's smaller
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
James: no, there is no need to touch kernel. You should have noticed,
that brightness control works as expected, before you login (during boot
or even on login screen).
Problem is in user-level process running during user session. We have to
find that process, than fix will be pretty simple.
See
Oh, that was about g-s-d source!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness controls skips Levels.
To manage notifications about this bug go to:
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = Invalid
** Also affects: gnome-settings-daemon
Importance: Undecided
Status: New
** Changed in: gnome-settings-daemon
Assignee: (unassigned) = Dmitriy Geels (dmig)
--
You received this bug notification because
Fix itself is pretty simple, but all that g/dconf mess confuses me.
Need to understand, how to create new key in dconf...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness
Oh yeah! #24 is really dirty one!
But it gave me a clue, how this bug should be fixed:
Patching StepUp/StepDown handlers is very bad practice, because these methods
may be called by some other applications. We need to prevent calls to these
methods depending on some parameter.
The problem
I would change status on g-p-m to 'Invalid' and assign bug to other
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness controls skips Levels.
To manage notifications
*** This bug is a duplicate of bug 655375 ***
https://bugs.launchpad.net/bugs/655375
Public bug reported:
Binary package hint: xserver-xorg-input-joystick
just crash information for bug #655375
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-input-joystick
*** This bug is a duplicate of bug 655375 ***
https://bugs.launchpad.net/bugs/655375
** This bug has been marked a duplicate of bug 655375
incorrectly initialized uinput device causes xorg crash
* You can subscribe to bug 655375 by following this link:
See duplicate. xserver-xorg-input-joystick still crashes
** Changed in: xserver-xorg-input-joystick (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655375
** Summary changed:
- zeemote bluetooth joystick causes xorg crash
+ incorrectly initialized uinput device causes xorg crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655375
Title:
incorrectly
I found the reason of this crash (and fixed it). See patch.
Looks like, that crash is caused by absmin=absmax values, which are 0.
** Patch added: zeemoted.patch
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-joystick/+bug/655375/+attachment/1770504/+files/zeemoted.patch
**
Problematic place must be somewhere in jstk_axis.c, but I don't
understand, how absmin/absmax values are passed there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655375
Title:
incorrectly
After today xserver-xorg-video-intel update, found those lines after
reboot in gdm log:
../../intel/intel_bufmgr_gem.c:1153: Error writing data to buffer 1384: (0
880640) Bad address .
../../intel/intel_bufmgr_gem.c:1153: Error writing data to buffer 1333: (0
233472) Bad address .
--
Public bug reported:
Binary package hint: xserver-xorg-input-joystick
Recently I got Zeemote JS1 bluetooth joystick and wanted to test it in
games. I connected it using this manual:
http://ubuntuforums.org/showpost.php?p=8315022postcount=2
Zeemoted connects to device successfully, device
--
zeemote bluetooth joystick causes xorg crash
https://bugs.launchpad.net/bugs/655375
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Changing bug status to address it to xorg-edgers developers
** Summary changed:
- Notification's background doesn't show completely
+ [xorg-edgers] Notification's background doesn't show completely
** Changed in: pixman (Ubuntu)
Status: Invalid = Confirmed
--
[xorg-edgers]
Public bug reported:
Binary package hint: apport
Trying to report xorg bug causes apport crash because of unresolved
function name:
d...@dmig-desktop:~$ ubuntu-bug xorg
hook /usr/share/apport/package-hooks//source_xorg.py crashed:
Traceback (most recent call last):
File
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/641232/+attachment/1597759/+files/Dependencies.txt
--
hook /usr/share/apport/package-hooks//source_xorg.py crashed
https://bugs.launchpad.net/bugs/641232
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Not sure if it's xorg or drm bug. Doesn't depend on kernel version:
reproduced on stock 10.04 kernel and all newer kernels for lucid from
http://kernel.ubuntu.com/~kernel-ppa/mainline/.
My motherboard: Asus P5B-VM
Running Ubuntu
Group permission fixed, but write permission broken:
d...@dmig-desktop:~$ ll /dev/input/
итого 0
drwxr-xr-x 2 root root 120 2010-08-23 17:27 by-id
drwxr-xr-x 2 root root 140 2010-08-23 17:27 by-path
crw-r- 1 root plugdev 13, 64 2010-08-23 17:27 event0
crw-r- 1 root plugdev 13,
** Changed in: goldendict (Ubuntu)
Status: New = Confirmed
--
goldendict doesn't start, if terminated abnormally
https://bugs.launchpad.net/bugs/553909
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Goldendict should check, whether process with id from ~/.goldendict/pid
is running and it is goldendict instance. Or goldendict should try to
write-lock existing pid file before writing to it.
--
goldendict doesn't start, if terminated abnormally
https://bugs.launchpad.net/bugs/553909
You
Currently main() has check for already running process with same PID as
in pid file, but it doesn't check, if that process is goldendict.
** Summary changed:
- goldendict doesn't start, if terminated abnormally
+ need to check process name in already-running check
--
need to check process name
Public bug reported:
Binary package hint: gwibber
After upgrade to Lucid, gwibber won't start anymore.
It crashes with backtrace:
d...@dmig-desktop:~$ gwibber
** (gwibber:29133): WARNING **: Trying to register gtype
'WnckWindowState' as enum when in fact it is of type 'GFlags'
**
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48914784/Dependencies.txt
--
gwibber crashes on start
https://bugs.launchpad.net/bugs/584159
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: gnochm
package gnochm 0.9.11-3 is not installable, because it have unresolvable
dependency on package python-gtkhtml2
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnochm (not installed)
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic
Looks like, that last update of evolution-data-server package fixed the problem.
Humberto, did it fix for you?
--
evolution doesn't receive emails from pop3 account
https://bugs.launchpad.net/bugs/562154
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Package gdm updated to 2.30.0-0ubuntu5 -- still crashes
--
gdm-session-worker crashed with SIGSEGV in filter_func()
https://bugs.launchpad.net/bugs/558451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: evolution
After launch, evolution starts downloading new emails. But progress dialog
stuck with message downloading 1 of xx messages.
Evolution
Sometimes after that evolution-data-server-2.28 crashes with assertion (apport
tells that it can't handle
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44010295/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/44010296/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/44010297/ProcStatus.txt
** Attachment
Manually obtained backtrace (using https://wiki.ubuntu.com/Backtrace)
** Attachment added: evolution-data-server-2.28-backtrace.txt
http://launchpadlibrarian.net/44013408/evolution-data-server-2.28-backtrace.txt
--
evolution doesn't receive emails from pop3 account
Segfault at 0x1 -- may be related to bug #553190
** Visibility changed to: Public
--
gdm-session-worker crashed with SIGSEGV in filter_func()
https://bugs.launchpad.net/bugs/558451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*** This bug is a duplicate of bug 558451 ***
https://bugs.launchpad.net/bugs/558451
** This bug is no longer a duplicate of bug 553190
gdm-session-worker crashes on usb device connect/disconnect
** This bug has been marked a duplicate of bug 558451
gdm-session-worker crashed with
*** This bug is a duplicate of bug 558451 ***
https://bugs.launchpad.net/bugs/558451
** This bug has been marked a duplicate of bug 558451
gdm-session-worker crashed with SIGSEGV in filter_func()
--
gdm-session-worker crashes on usb device connect/disconnect
*** This bug is a duplicate of bug 558451 ***
https://bugs.launchpad.net/bugs/558451
** This bug is no longer a duplicate of bug 553190
gdm-session-worker crashes on usb device connect/disconnect
** This bug has been marked a duplicate of bug 558451
gdm-session-worker crashed with
Just got this crash after disconnecting usb mouse.
** Summary changed:
- gdm-session-worker crashes on usb storage mount/unmount/connect/disconnect
+ gdm-session-worker crashes on usb device connect/disconnect
--
gdm-session-worker crashes on usb device connect/disconnect
I tried to get Xorg core dump with no success. Looks like, that option
NoTrapSignals has no effect.
--
[Lucid] Option NoTrapSignals ignored when debugging xserver
https://bugs.launchpad.net/bugs/532845
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I found out, what prevents gdm/Xorg from creating core dump: soft core
limit is set to 0 for these processes.
--
[Lucid] Option NoTrapSignals ignored when debugging xserver
https://bugs.launchpad.net/bugs/532845
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Got a backtrace with rebuilt hal (using instruction
https://wiki.ubuntu.com/DebuggingProgramCrash#Prior%20Ubuntu%20versions).
Xorg itself doesn't crash, gdm-session worker crashes in libhal1.so
** Also affects: hal
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
** Summary changed:
- Xorg crashes on usb storage unmount/disconnect
+ gdm-slave-worker crashes on usb storage mount/unmount/connect/disconnect
** Summary changed:
- gdm-slave-worker crashes on usb storage mount/unmount/connect/disconnect
+ gdm-session-worker crashes on usb storage
*** This bug is a duplicate of bug 553190 ***
https://bugs.launchpad.net/bugs/553190
Public bug reported:
Binary package hint: gdm
This is duplicate of bug #553190, created just to post all information
collected by ubunu-bug.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gdm
*** This bug is a duplicate of bug 553190 ***
https://bugs.launchpad.net/bugs/553190
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43235727/Dependencies.txt
** This bug has been marked a duplicate of bug 553190
gdm-session-worker crashes on usb storage
*** This bug is a duplicate of bug 553190 ***
https://bugs.launchpad.net/bugs/553190
** This bug has been marked a duplicate of bug 553190
gdm-session-worker crashes on usb storage mount/unmount/connect/disconnect
--
[lucid] gdm-session-worker segfault
Sebastien, I tried to force gdm-session-worker to produce core dump, but had no
luck.
It's /proc/pid/limits has soft core limit set to 0:
Limit Soft Limit Hard Limit Units
...
Max core file size0unlimitedbytes
...
Problem still persists after today's update.
To be sure I rolled back all xorg-edgers packages to native Lucid versions.
Crashes are still reproduced.
I'll try to obtain backtrace (running gdb from different tty hangs X, so
I need another pc).
** Changed in: xorg-server (Ubuntu)
Status:
*** This bug is a duplicate of bug 457916 ***
https://bugs.launchpad.net/bugs/457916
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43141195/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/43141196/ProcMaps.txt
** Attachment
Apport just caught this bug in Lucid beta with all packages up-to-date.
** Changed in: ubuntuone-client (Ubuntu)
Status: Fix Released = New
--
ubuntuone-syncdaemon crashed with DBusException in call_blocking()
https://bugs.launchpad.net/bugs/457916
You received this bug notification
Here is something, that may be interesting in /var/log/messages:
Apr 5 16:32:01 dmig-desktop kernel: [12408.884911] gdm-session-wor[2825]
general protection ip:7f7c8f0abe76 sp:7fffe49a50d0 error:0 in
libhal.so.1.0.0[7f7c8f0a+1]
Apr 5 16:32:02 dmig-desktop pulseaudio[18540]: pid.c:
Looks like this bug #355021 is related. Can't find package
libhal1-dbgsym for Lucid...
--
Xorg crashes on usb storage unmount/disconnect
https://bugs.launchpad.net/bugs/553190
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I mean, there is no package libhal1-dbgsym in ddebs repo
--
Xorg crashes on usb storage unmount/disconnect
https://bugs.launchpad.net/bugs/553190
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Looks like, that today's update fixed this bug. If it won't reproduce in
nearest days, I'll close this report.
--
Xorg crashes on usb storage unmount/disconnect
https://bugs.launchpad.net/bugs/553190
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
1 - 100 of 231 matches
Mail list logo
