Public bug reported:
When creating a SNMPv3 user this error appears:
$ /usr/bin/net-snmp-config --create-snmpv3-user -ro -A MD5 -a XX -x Y
-X DES Z
touch: cannot touch '/snmp/snmpd.conf': No such file or directory
/usr/bin/net-snmp-create-v3-user: 146: cannot create /snmp/snmpd.conf:
Public bug reported:
Kernel/Package is linux-image-5.15.0-25-generic
running:
$ modprobe -r floppy
Killed
ends in BUG: kernel NULL pointer dereference (see dmesg).
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15
Hi,
I've testet snmpd-5.9.1+dfsg-1ubuntu2.1 from jammy-proposed. Creation of
SNMNPv3 user works now.
Thanks, Sascha.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969623
Title:
Creati
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969623
Title:
Creation of SNMPv3 user broken (Jammy/22.04)
To manage
Public bug reported:
Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
Server will not start. Either directly via lightdm or via gdm/wayland
selecting Xubuntu session.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.
adding Xorg crash dump
** Attachment added: "Xorg crash dump"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+attachment/5577702/+files/_usr_lib_xorg_Xorg.126.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
*** This bug is a duplicate of bug 1967901 ***
https://bugs.launchpad.net/bugs/1967901
** This bug has been marked a duplicate of bug 1967901
[qxl] Xorg fails to start with "Screen(s) found, but none have a usable
configuration."
--
You received this bug notification because you are a me
Public bug reported:
Hello,
It happened now twice for me that after a "unattended update" the linux
kernel is missing routes which were announced via BGP. From my point of
view, the problem is that networkd is restarted(?). Which leads to a
deletion of the routes in linux kernel.
# cat /var/log
happened on jammy
** Changed in: frr (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968550
Title:
unattended updates, missing routes
To manage notificatio
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Cente
Public bug reported:
#ceph -s
...
health: HEALTH_ERR
Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
defined for '#' formats
..
# dpkg -l | grep ceph
ii ceph-base 17.1.0-0ubuntu1
amd64common ceph daemon libra
Module 'balancer' has failed: PY_SSIZE_T_CLEAN macro must be defined for
'#' formats
is affected as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964322
Title:
Module 'devicehealth' has fail
# ceph telemetry status
Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#'
formats
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964322
Title:
Module 'devicehealth' has fail
The Debian Maintainer said[1]:
"In the Debian context this was intended to be a temporary
non-intrusive solution that would not stomp over upstream, until this
had been agreed with them. My intention has always been to revert the
local SONAME bump before the next Debian release. Ubuntu will have t
Same here. KDE 4.0.3, Kubuntu 8.04. I upgraded from 7.10 with the
experimental KDE 4 packages.
--
Kplato crashed and caused the signal 6 (SIGABRT)
https://bugs.launchpad.net/bugs/218966
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same thing on a Dell Dimension 4500s with an intel 845G chipset. Between
the boot loader and the start of X, there is a blank screen. Switching
to a console will show an extremely large font, so the resolution must
be off. Also, on a shutdown, after X is closed, the screen goes blank
again.
--
In
Ok, i compiled a fixed Kernel and tried it.
The U160 is running like charme.
Thx to Chris Wilson for this Christmas present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/608907
Title:
[lucid][mave
Keep it up, can't wait to see your results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903558
Title:
Unable to boot 12.04 without 'noapic' flag enabled in GRUB
To manage notifications about this
Could you please upload the working config?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903558
Title:
Unable to boot 12.04 without 'noapic' flag enabled in GRUB
To manage notifications about this
Is v3.2-rc7-precise also broken with the stock config?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903558
Title:
Unable to boot 12.04 without 'noapic' flag enabled in GRUB
To manage notifications
Is it somehow possible to find aut which configuration options have been
used for compiling the kernel in that package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903558
Title:
Unable to boot 12.
It looks like the configuration is logged in BUILD.LOG, maybe this is a
good start to find out which options are responsible for the noapic
issue. I'm going to compare the configuration of the 3.2-rc7-precise to
the ones of 3.2.2-precise. IF there are differences I'll try to compile
3.2.5 with the
I compared the 0003-default-configs.patch files of 3.2.1-precise and
3.2.2-precise with a diff viewer. The only difference seems to be that
in the newer one CONFIG_SSB_B43_PCI_BRIDGE=y gets added. So this might
be the option that's causing the problems.
--
You received this bug notification becau
To be more specifig on my posting under #11, this is an output from
powertop after 5 minutes idling
24,0% ( 98,2) gtk-gnash
11,4% ( 46,5) [ehci_hcd:usb1, ehci_hcd:usb2, ehci_hcd:usb3, brcm80211]
5,0% ( 20,4) firefox
1,3% ( 5,3) [ahci]
1,2% ( 5,0) mc
0,5% ( 2,1) wget
0,5%
... and that is the maximum ... taken some minutes later.
https://bugs.launchpad.net/bugs/760131
Title:
Power consumption raised significantly in natty
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
es: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sascha 1385 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf080 irq 22'
Mixer n
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/52576704/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/52576705/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/52576706/BootDmesg.txt
** Att
Hi,
I tried to make a startup without loading the vesafb without success.
I attached the dmesg.
Is there any other idea for blocking the vesafb?
cu
Sascha
** Attachment added: "dmesg - try no vesafb.txt"
https://bugs.launchpad.net/ubuntu/+bug/608907/+attachment/1518739/+file
I have followed the bug-report 29647 at freedesktop.org and tried it
with the non.existing parameters.
You can see it inside the dmesg in the attachment of post #27.
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.36-020636rc2-generic
root=UUID=7c27cd01-d23e-4fd2-afb1-445ef72f3d0e ro qu
I had tested the daily build from http://cdimage.ubuntu.com/daily-
live/current/ without success. I looks like the same problem.
--
[lucid][i915] Lenovo U160 Intel i7 620UM blank screen
https://bugs.launchpad.net/bugs/608907
You received this bug notification because you are a member of Ubuntu
Bu
I made a dmesg with the latest mainline Kernel 2.6.36... with the daily
Maveric.
** Attachment added: "dmesg-2.6.36-999.txt"
https://bugs.launchpad.net/ubuntu/+bug/608907/+attachment/1509055/+files/dmesg-2.6.36-999.txt
--
[lucid][i915] Lenovo U160 Intel i7 620UM blank screen
https://bugs.lau
Hi, here is the lspci-vvnn with the new Mainline 2.6.36rc2.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+bug/608907/+attachment/1513472/+files/lspci.txt
--
[lucid][maverick][i915] Lenovo U160 Intel i7 620UM blank screen
https://bugs.launchpad.net/bugs/608907
You receiv
... and also a new dmesg with drm.debug=0xe from Mainline 2.6.36rc2
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+bug/608907/+attachment/1513474/+files/dmesg.txt
--
[lucid][maverick][i915] Lenovo U160 Intel i7 620UM blank screen
https://bugs.launchpad.net/bugs/608907
Yo
** Tags removed: needs-upstream-testing
--
[lucid][i915] Lenovo U160 blank screen on LVDS-1
https://bugs.launchpad.net/bugs/610369
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
Hi,
today I tested the Mainline Kernel 'v2.6.32.18-lucid' without success.
It looks like the same.
It also happen when I boot with the option 'i915.modeset=0 single' into
the root console and reload the module i915 with modeset=1.
Is there anything else I can do ?
Sasc
601 - 635 of 635 matches
Mail list logo
