Same here on my Ubuntu 24.04.1:
$ sudo bpftrace
bpftrace: error while loading shared libraries: libLLVM-18.so.18.1: cannot open
shared object file: No such file or directory
$ apt-show-versions | grep -i bpftrace
bpftrace:amd64/noble-updates 0.20.2-1ubuntu4.2 uptodate
Indeed problem gone after
FWIW / Workaround:
Uninstalled arp-scan
From https://github.com/royhills/arp-scan, made and installe arp-scan, and it's
working:
sander@xubuntu:~$ sudo arp-scan --localnet --interface=wlp2s0 | head -4
Interface: wlp2s0, type: EN10MB, MAC: 84:4b:f5:47:70:6d, IPv4: 192.168.178.31
Target list from
The same problem on another system (xubuntu 24.04):
sander@xubuntu:~$ sudo arp-scan --localnet --interface=wlp2s0 | head -4
Interface: wlp2s0, type: EN10MB, MAC: 84:4b:f5:47:70:6d, IPv4: 192.168.178.31
WARNING: Cannot open MAC/Vendor file ieee-oui.txt: Permission denied
WARNING: Cannot open MAC/V
Public bug reported:
Ubuntu 24.04, fully updated
Running arp-scan with sudo, results in the errors below and no OUI
resolving, if the current directory is not owned or not writable by
root.
Also in Debian:
https://groups.google.com/g/linux.debian.bugs.dist/c/Fh4m_uTbUGQ
A bug, a feature, or a P
Me too. I did the things below. I'll now test if the flicerking is gone.
Interesting quote above: "running on battery also seems to worsen the
problem slightly.". I normally use my laptop on power, but on battery
for the past days. So that might be reason I only noticed it now.
sander@witje:~$
That second paragraph should read:
And that message was already in the first dmesg ... so the i8042 driver
already KNEW something was fishy, and hinted what I should do ... ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Interesting ... triggered by "[ 0.278602] i8042: PNP: PS/2 appears to
have AUX port disabled, if this is incorrect please boot with
i8042.nopnp", I just tried i8042.nopnp as only option in GRUB, and that
works too: keyboard works immediatly.
And that message was already in the first dmesg ... so t
Only i8042.direct ... not good. Keyboard not working for x seconds
Only i8042.dumbkbd ... yes, works! Keyboard working immediatly.
So my /etc/default/grub now contains:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd"
And stuff from dmesg:
sander@zwart2204:~$ sudo dmesg | grep i8042
[
Out of curiosity:
The manual work (adding the line to GRUB): is that how it should be, or
a bug (something Ubuntu should take care of)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976396
Title:
Ah, SOLVED, like this:
Triggered by your remarks, I found
https://unix.stackexchange.com/a/656183, which says:
RUB_CMDLINE_LINUX_DEFAULT="atkbd.reset i8042.reset i8042.nomux quiet splash".
If this doesn't work, follow the same process but try
GRUB_CMDLINE_LINUX_DEFAULT="i8042.direct i8042.dumbk
I tried "i8042.noaux=1", but no change: after boot and after resume:
touchpad works immediatly, but keyboard takes 25-45 seconds.
dmesg included
** Attachment added: "dmesg "i8042.noaux=1""
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+attachment/5594428/+files/dmesg.i8042.no
Thanks for replying.
See included dmesg. I generated it with the following command ...
hopefully OK
sudo dmesg -T > dmesg_after_suspend_and_resume.txt
Snippet from dmesg:
[wo jun 1 11:38:40 2022] i8042: [28649] 65 -> i8042 (parameter)
[wo jun 1 11:38:40 2022] i8042: [28649] ab <- i8042 (inte
Still there in current Ubuntu 22.04 (fresh install, fully updated)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960893
Title:
i915 gives trace in dmesg
To manage notifications about this bug go t
Ah, it seems to happen after a fresh boot too: the login is there, mouse
is working, but keyboard not. It takes 20 - 30 seconds before keyboard
is working.
Snippet from dmesg (leaving out wlo1 stuff):
...
[di mei 31 20:09:47 2022] skl_hda_dsp_generic skl_hda_dsp_generic:
hda_dsp_hdmi_build_contr
Public bug reported:
Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at
all.
Newish HP laptop (so recent hardware)
Problem: After resuming from suspend, the laptop's keyboard is not
working for about 30 seconds (the laptop's touchpad is working at once).
Looking at dme
Public bug reported:
[1.904158] kernel: [ cut here ]
[1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x)
[1.904176] kernel: WARNING: CPU: 3 PID: 328 at
drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0
[i915]
[1.9
Public bug reported:
Unstable Wifi
Sometimes most Wifi AP's (including my own) or not seen
dmesg filled with
[di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command
[di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command
[di feb 15 06:44:54 2022] rtw_8
I bumped into the same: disk full.
After inspection:
/var/log/syslog 20GB
/var/log/syslog.1 60GB
... removing /var/log/syslog.1 same some disk space free, but
/var/log/syslog keep on growing, so I'm going to reboot.
Jan 16 08:57:24 brixit gnome-shell[1788]: The offending callback was
SourceFun
FWIW: On Ubuntu 18.04 no problem:
sander@brixit:~$ execstack -s /tmp/ls
sander@brixit:~$
sander@brixit:~$ execstack -q /tmp/ls
X /tmp/ls
So it seems Ubuntu 20.04 specific?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
On Ubuntu 20.04, I have the same problem:
$ execstack -s hello
execstack: dso.c:877: reopen_dso: Assertion `dso->shdr[j].sh_size == 0' failed.
Aborted (core dumped)
sander@witte2004:~/hello-world$ gcc -o hello hello.c
sander@witte2004:~/hello-world$ ./hello
Hello, world!
sander@witte2004:~/he
And same same with /usr/bin/ls :
sander@witte2004:~/hello-world$ cp /usr/bin/ls /tmp/
sander@witte2004:~/hello-world$ ll /tmp/ls
-rwxr-xr-x 1 sander sander 142144 jun 8 20:43 /tmp/ls*
sander@witte2004:~/hello-world$ execstack -s /tmp/ls
execstack: dso.c:877: reopen_dso: Assertion `dso->shdr[j]
*** This bug is a duplicate of bug 1713238 ***
https://bugs.launchpad.net/bugs/1713238
@oliverubuntu: Thank you, that worked for me on Ubuntu 17.10!
/usr/bin/gufw-pkexec: line 13: 15373 Segmentation fault (core
dumped) python3 ${LOCATIONS[${i}]} $1
sander@sammie-1710:~$ echo $XDG_SESSIO
Yes, that solved it for me after activating "proposed" on artful, with
xdg-utils (1.1.1-1ubuntu3)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721948
Title:
gvfs-open/xdg-open shows message about
** Changed in: golang-1.7 (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647764
Title:
golang in ubuntu-lxc / lxd-stable still on 1.6
To manage notific
OK, that will work. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647764
Title:
golang in ubuntu-lxc / lxd-stable still on 1.6
To manage notifications about this bug go to:
https://bugs
Public bug reported:
Go (golang) in ubuntu-lxc / lxd-stable is still on version 1.6, whereas
Go 1.7 was released on Aug 15, 2016.
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxd-stable/+packages says
"ubuntu-lxc-bot 2016-03-22" ... so is that bot not updating golang anymore?
** Affec
@Hansen ... I did that, did a reboot, did a suspend/resume (arrows
appeared), and the logging is 1997 lines long. Can you advice what to do
with that logging?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
@Joakim: Ah, OK, I now understand. Thanks.
However: I have the beam symbol, but it's now grey (like: no signal), and no
Wifi networks visible. :-(
After a "sudo systemctl restart network-manager.service" the beam signal
shortly becomes an empty pizza slice, then the Up-Down-arrow, and greyed bea
FWIW2:
I only have Wifi. No fixed ethernet. Maybe that is part of the problem?
Maybe the indicator assumes the first ethernet is always fixed ethernet,
and puts that symbol on it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
I have the same problem with a fresh install of Ubuntu 16.10 / yakkety
on my HP Stream 13.
The workaround "sudo systemctl restart network-manager.service" works
for me: it removes the up-down-arrow, and gives back the beam symbol
showing the available wifi networks.
I have no file /etc/systemd/sy
Public bug reported:
Installed miredo via Package Manager, and I got this report.
Afterwards ifconfig does show a teredo interface (with 2001:0:...
address), but it's not working:
$ ping6 www.google.com
connect: Network is unreachable
Restarting the miredo service does not solve that.
Problem
This happens on my Ubuntu 15.04 with VLC 2.2.0.
AFAIK Patch provided here: http://sourceforge.net/p/pupnp/bugs/108/#624e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318262
Title:
ui freezes afte
dmesg with drm-debu and flip switch problem
** Attachment added: "dmesg with drm-debu and flip switch problem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+attachment/4396622/+files/dmesg.with-flip-problem-and-drm-debug.txt
--
You received this bug notification because you a
The attachment contains the complete dmesg with drm turned on.
Snippet from around the flip message:
[ 7538.988560] [drm:valleyview_update_wm] Setting FIFO watermarks - A:
plane=111, cursor=2, B: plane=2, cursor=2, SR: plane=60, cursor=2
[ 7538.988565] [drm:intel_set_memory_cxsr] memory self-ref
drm.debug=0xe added kernel command line:
$ dmesg | head
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.19.0-16-generic (buildd@komainu) (gcc version
4.9.2 (Ubuntu 4.9.2
FWIW:
The latest change to btscanner 2.1 was made in 2005. The maintainer
seems to be gone. So maybe better to remove btscanner from the Ubuntu
repositories?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Still happens on Ubuntu 15.04 with btscanner 2.0 after pressing "b"
$ btscanner
*** buffer overflow detected ***: btscanner terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x78c4e)[0x7fa095fc8c4e]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7fa096068e8c]
/lib/
Ouch. I had looked for a BIOS upgrade, but I had not been able to find
it. Thank you for your work.
I just upgraded to F.06 (now: "DMI: Hewlett-Packard HP Stream Notebook
PC 13/802A, BIOS F.06 01/06/2015"), and I'll monitor the effect.
Thanks again.
--
You received this bug notification because
Thanks.
Full computer name: HP Stream 13, HP 13-c000nd-N2840 aka HP 13-c000nd.
There is no sticker on the computer, but an imprint saying "Model
13-c000nd". Is that enough information?
There is no Memtest86+ in the Grub boot menu and I can't add it, so I ran
Memtst86+ (V6.0.0 Free) from a USB s
Public bug reported:
Just a warning, but maybe to useful to report what dmesg is telling me:
[ 4653.114802] sdhci: Timeout waiting for Buffer Read Ready interrupt during
tuning procedure, falling back to fixed sampling clock
[ 4653.116957] [ cut here ]
[ 4653.116995] WAR
Public bug reported:
The below logging is shown in dmesg. I'm not sure if it's a
kernel/software or a hardware problem.
[za apr 4 13:07:54 2015] ACPI Error: [PMIN] Namespace lookup failure,
AE_NOT_FOUND (20141107/psargs-359)
[za apr 4 13:07:54 2015] ACPI Error: Method parse/execution failed
Still (again?) happening with 3.19.0-12-generic
[ 5578.584172] [ cut here ]
[ 5578.584230] WARNING: CPU: 0 PID: 15321 at
/build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:9713
intel_check_page_flip+0xda/0xf0 [i915]()
[ 5578.584233] Kicking stuck page flip:
The error occured twice in the last 24 hours:
$ cat /var/log/kern.log | grep -i flip
Mar 2 23:13:04 superstreamer kernel: [ 3283.556389] WARNING: CPU: 0 PID: 0 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698
intel_check_page_flip+0xe6/0xf0 [i915]()
Mar 2 23:13:04 superstre
I never close the lid immediately after booting, so in my case that
cannot have been the cause.
So far I have not found a correlation between the intel drm flip error
and things I did. Sometimes the error occurs after an hour, sometimes
not for two days. Now it is even 5 days ago:
$ cat /var/log/
FWIW: I searched for "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic
update failure on pipe A (start=76355 end=76356)" and found this source
code on http://lists.freedesktop.org/archives/intel-
gfx/2014-February/040161.html doing the "Atomic update failure on pipe":
115 static void intel_pipe_
FWIW: 12 seconds before the described problem, there is this line in
dmesg:
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe
A (start=76355 end=76356)
which I can't find on Google.
More from dmesg:
$ dmesg | grep "Linux version"
[0.00] Linux version 3.19.0-994-ge
After 24 hours of use, still no slub.c error message in dmesg.
$ dmesg | grep -i slub
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] Linux version 3.18.0-13-generic (root@gloin) (gcc version
4.9.2 (Ubuntu 4.9.2-10ubuntu5) ) #14 SMP Tue Feb 17 11:13:29 UTC
After the autoremove & purge, reboot into 3.19, and a fresh install of
your kernel debs, things look better:
sander@superstreamer:~$ dmesg | grep -i -e "Linux version" -e slub
[0.00] Linux version 3.18.0-13-generic (root@gloin) (gcc version 4.9.2
(Ubuntu 4.9.2-10ubuntu5) ) #14 SMP Tue Feb
Rebooted, and same result
sander@superstreamer:~$ uname -a
Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
sander@superstreamer:~$
sander@superstreamer:~$ dpkg -l | grep -e linux-image- -e "^|"
| Status=Not/Inst/Conf-files/Unpacke
Thanks.
Current situtation:
sander@superstreamer:~$ uptime && dmesg | grep -i -e "Linux version" -e slub
22:22:32 up 2:59, 1 user, load average: 1,74, 0,90, 0,70
[0.00] Linux version 3.18.0-13-generic (buildd@komainu) (gcc version
4.9.2 (Ubuntu 4.9.2-10ubuntu5) ) #14-Ubuntu SMP Fri F
OK, now running that new kernel. Well, at least I think it is, but it
says:
$ uname -a
Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
Made on Feb 6? Can that be right? There was no sign of
"3.18.0-13.14~lp1418286v1" in my Grub menu
Thanks! I'll do that tonight.
Question: should I install all four debs, so also the linux-image-extra?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418286
Title:
kernel BUG at /build/buildd/linux
full dmesg
** Attachment added: "dmesg-3.18.0-13-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+attachment/4319682/+files/dmesg-3.18.0-13-generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Ouch, it's still there in 3.18.0-13-generic:
sander@superstreamer:~$ uname -a
Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
sander@superstreamer:~$
sander@superstreamer:~$ dmesg | grep -i slub
[0.00] SLUB: HWalign=64, Ord
Running "3.19.0-994-generic #201502112105" from http://kernel.ubuntu.com
/~kernel-ppa/mainline/drm-intel-nightly/2015-02-12-vivid/ and now dmesg
shows a warning in a different line of intel_display.c:
[ 2702.807816] WARNING: CPU: 0 PID: 3 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_disp
I'm now running "3.19.0-999-generic #201502092105" which also shows
[ 930.448104] WARNING: CPU: 0 PID: 0 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9713
intel_check_page_flip+0xe6/0xf0 [i915]()
I'll now try the kernel you pointed to. BRB
--
You received this bug notificati
Solved by installing the kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/daily/2015-02-10-vivid/ leading to "3.19.0-999-generic
#201502092105"
According to https://bugzilla.kernel.org/show_bug.cgi?id=92981 the
kernel on http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ was
buil
FWIW:
I'm now running the latest 3.18 (3.18.0-13-generic) which arrived today
(Feb 10), and no more slub.c messages in dmesg.
So ... was it solved in 3.18.0-13-generic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
These seem the same bug reports on Redhat, since january
https://bugzilla.redhat.com/show_bug.cgi?id=1190511
https://bugzilla.redhat.com/show_bug.cgi?id=1181071
https://bugzilla.redhat.com/show_bug.cgi?id=1184161
https://bugzilla.redhat.com/show_bug.cgi?id=1183209
** Bug watch added: Red Hat Bug
Public bug reported:
Running Vivid with kernel 3.19 (debs from http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.19-vivid/), I get the warning below in dmesg.
I can't use "ubuntu-bug linux" because I get "It appears you are
currently running a mainline kernel. It would be better to report this
b
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+attachment/4316320/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420290
T
FWIW:
I also installed the lowlatency version of kernel 3.19, and that dmesg
doesn't show the lines "Request for unknown module key 'Magrathea:
Glacier signing key:"
sander@superstreamer:~$ uname -a
Linux superstreamer 3.19.0-031900-lowlatency #201502091451 SMP PREEMPT Mon Feb
9 14:58:45 UTC 201
I just installed kernel 3.19 on vivid (source: http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.19-vivid/), and dmesg shows 129 lines with
Request for unknown module key 'Magrathea: Glacier signing key:
007271576a09d86ef244371b0633e47abb75b89d' err -11
So ... is this a regression bug? Or somethi
@myself:
It was a noob thing indeed:
I had
linux-headers-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb
linux-image-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb
and needed the "all.deb" file too:
linux-headers-3.19.0-031900rc7_3.19.0-031900rc7.201502020035
I've installed v3.19-rc7-vivid (thus now running
3.19.0-031900rc7-generic) and the dmesg message is gone now. Good!
FWIW: with
linux-headers-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb
linux-image-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb
I did
sudo
Happens on my system too. I did a fresh install of Vivid daily two days
ago (Feb 3), did a update/upgrade today (Feb 5), and after the reboot
dmesg shows:
[ 11.252422] [ cut here ]
[ 11.252475] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
[ 11.252526] inva
In the meantime, I decided 14.04 was unusable.for me.
So I've done a fresh install of Vivid (15.04-to-be) daily version. That has
linux kernel 3.18, right? In one hour of usage, I've not seen the error message
in dmesg.
TBC
--
You received this bug notification because you are a member of Ub
Second reboot worked. I did some extensive disk writing (around 1GB),
got the read-only problem, and dmesg says:
[ 962.226687] sdhci: Timeout waiting for Buffer Read Ready interrupt during
tuning procedure, falling back to fixed sampling clock
[ 972.262988] mmc0: Timeout waiting for hardware i
I logged off, restarted, and the Ubuntu boot GUI says "/" needs to be
fixed (I pressed "F") and /tmp is not (yet) ready. I did get a Ubuntu
brown screen, but no login. I'm typing this in some 'other' OS.
I'll see if I can boot into Ubuntu with another boot.
--
You received this bug notification
FWIW: the "Read-only file system" error occured again. See below.
Nothing special in dmesg nor /var/log/syslog
sander@superstream:~$ pwd
/home/sander
sander@superstream:~$ touch blabla
touch: cannot touch ‘blabla’: Read-only file system
sander@superstream:~$ mount
/dev/mmcblk0p5 on / type ext4
Public bug reported:
On my HP Stream 13 laptop with Ubuntu 14.04 LTS (fully updated) I
sometimes (once an hour?) get the error below in dmesg. It has to do
with the eMMC / eMMC reader. There is no other flash device (like a USB
key) installed or in use.
Yesterday the file system turned read-only.
*** This bug is a duplicate of bug 1408495 ***
https://bugs.launchpad.net/bugs/1408495
Workaround found:
Instead of booting the Ubuntu live CD and clicking "Install", first
clicking "Try Ubuntu" and only then clicking on the Install icon on the
desktop, worked for me.
--
You received this b
Public bug reported:
crash during install of Vivid within Virtualbox
Running on Ubuntu 14.04 LTS 64-bit
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.4
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
ApportVersion: 2.15.1-0ubuntu
Update:
After installing gdm (instead of lightdm) the problem did not occur
anymore.
So: the problem seems to be in lightdm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397319
Title:
two sequen
Public bug reported:
After resuming from sleep, I sometimes (about 50%) get a first (unusual,
ugly) login screen, then a short (<1 sec) flash showing my desktop, then
the 'normal' login screen
First login window: http://oi59.tinypic.com/ws5uo9.jpg
Second login window: http://oi57.tinypic.com/24x
I don't understand; I thought it was already fixed on 2014-07-31: "This
bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1.1"?
Since then I have not experienced it anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
When not accepting/showing input from the keyboard, there is the usual
vertical blinking line in the password box (so: 'showing' it is
accepting input there), with the word "password" in the background of
that password box.
Would it help if I post a picture of video of what goes (or: doesn't go)
o
Update:
Another workaround: change the language in the upper right corner, in my
case switch from En1 to En2. After that, the password box accepts
keyboard input and shows corresponding dots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Package changed: ubuntu => lightdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349128
Title:
Ubuntu 14.04 login screen doesn't accept keyboard input
To manage notifications about thi
Public bug reported:
Ubuntu 14.04 login screen doesn't accept keyboard input in the password
box after my system has resumed from a sleep (=lid opening), so I can't
relogin anymore
Excpected behaviour: the login screen should accept keyboard input and
show them as stars in the password box.
Work
I can't; too difficult for me. Sorry.
Close this bug report if you want to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285304
Title:
NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out
To
Public bug reported:
Disclaimer: I'm not sure if this is a bug, or a feature. If it is not a
bug, I think reporting this issue is useful anyway because it causes
long delays in apt-get install / apt-get update.
On dual-stack setups (IPv4 and IPv6), if one of the two paths is slow or
non-functiona
I can confirm James Dupin's post: gone after "sudo apt-get remove
libpam-smbpass".
See http://ubuntuforums.org/showthread.php?t=2214042 with my experience
before I saw this post.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
PS:
So that Google will find it, I'll post my exact message with a different
(line?) number:
"no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory"
HTH
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
Fixed ethernet not working, and dmesg says upon connecting the ethernet
cable.
sander@flappie:~$ uname -a
Linux flappie 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
sander@flappie:~$
sander@flappie:~$ lsb_release -a
No LSB mod
In a new setup (Sitecom router, no more Zyxel) and Ubuntu 13.10, I still
have the same problem via Wifi:
[ 1782.075212] IPv6: wlan0: IPv6 duplicate address
2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected!
[ 1813.616483] IPv6: wlan0: IPv6 duplicate address
2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 d
It is also solved in more recent version of netstat / net-tools, for
example the git version. See below.
So why not upgrade to a more recent net-tools in Ubuntu? Can the
maintainers take care of that?
Git-version:
sander@HPtje:~/git/net-tools$ ./netstat -s | grep -i octet
InOctets: 891627609
Public bug reported:
problem during install of virtualbox
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.3
ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic i686
ApportVersion: 2.0.1-0ubuntu17.4
Archite
Results from 12.04.3:
I kept the lid open with no power cord inserted. So the battery went empty.
After putting in the power cord and powering up 12.04.3 ... NO crash report. So
that's better than with 13.10 that always report a crash message.
"you want/are hibernating when you close the lid in
An interesting result:
With 13.10, when I close the laptop lid and remove the power cable, after one
night the battery will be empty and upon a fresh, powered boot I will get the
crash reported here.
With 12.04.3, with the closed lid & removed power cable, after one night the
laptop could just
OK: I just installed 12.04.3 (32-bit, not 64-bit, if that matters) on
the same machine. Fully updated.
I'll force the empty-battery and see what happens afterwards.
sander@sander12043:~$ uname -a
Linux sander12043 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 15:31:16
UTC 2013 i686 i686 i
I'm not sure, but that could very well be.
Does that change the case?
Should I just click on "ignore"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219498
Title:
[Hewlett-Packard HP ProBook 4530
Update:
Still happens with that BIOS.
[Hewlett-Packard HP ProBook 4530s] suspend/resume failure
sander@HPtje:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
68SRR Ver. F.41
05/22/2013
sander@HPtje:~$
--
You received this bug notification because you are a member of Ub
Thank you for your reply!
I did the BIOS upgrade. I'll force an empty battery occurence, and check
what Ubuntu says upon boot afterwards.
sander@HPtje:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
68SRR Ver. F.41
05/22/2013
sander@HPtje:~$
--
You received this bug n
Public bug reported:
The usual crash after a fresh boot after the battery went empty.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-4-generic 3.11.0-4.9
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
Annotation: This
Public bug reported:
Just started Ubuntu 13.10 and got this error.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-6-generic 3.10.0-6.17
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic i686
Annotation: This occured during a pre
I still get apportcheckresume crash reports on my fully updated system.
$ uname -a
Linux R540 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
So ... not solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Yes, I can confirm: happens for me on fully updated Ubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/374101
Title:
Brasero hangs at Normalizing tracks
To manage notifications about this
Seems to be related to
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/102 , which
says:
/quote
CONCLUSION:
- grub-efi 32bits always creates invalid entries.
- Installing Ubuntu32 bits on an EFI system should be blocked by Ubiquity (the
Ubuntu installer). In this case, Ubiquity should a
Also happens on 13.04 daily build, with dmesg saying:
usb-creator-gtk[411]: segfault at 4 ip 7fb5e229ed80 sp
7fff90737378 error 6 in libdbus-1.so.3.7.2[7fb5e227a000+43000]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
1 - 100 of 431 matches
Mail list logo
