[Bug 1776013] Re: systemd-networkd: DHCP lease lost (Ubuntu 18.04)
To fix it with cloud-init we need to create an override-file for netplan like this: /etc/netplan/99-critical-dhcp.yaml network: version: 2 ethernets: ens2: dhcp4: true critical: true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776013 Title: systemd-networkd: DHCP lease lost (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 341006] Re: ease cloning of virtual images by disabling mac address rules
This is from dmesg: [0.932308] vmxnet3 :0b:00.0 eth0: NIC Link is Up 1 Mbps [0.965537] vmxnet3 :0c:00.0 eth1: NIC Link is Up 1 Mbps [0.973137] vmxnet3 :13:00.0 eth2: NIC Link is Up 1 Mbps [0.979222] vmxnet3 :14:00.0 eth3: NIC Link is Up 1 Mbps [0.985227] vmxnet3 :1b:00.0 eth4: NIC Link is Up 1 Mbps [4.733558] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [4.733563] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [4.733565] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready [4.733568] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready [4.733570] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready [6.543452] vmxnet3 :0c:00.0 eth1: intr type 3, mode 0, 2 vectors allocated [6.543850] vmxnet3 :0c:00.0 eth1: NIC Link is Up 1 Mbps [6.545858] vmxnet3 :1b:00.0 eth4: intr type 3, mode 0, 2 vectors allocated [6.546065] vmxnet3 :1b:00.0 eth4: NIC Link is Up 1 Mbps [6.547294] vmxnet3 :13:00.0 eth2: intr type 3, mode 0, 2 vectors allocated [6.547496] vmxnet3 :13:00.0 eth2: NIC Link is Up 1 Mbps [6.548714] vmxnet3 :0b:00.0 eth0: intr type 3, mode 0, 2 vectors allocated [6.549006] vmxnet3 :0b:00.0 eth0: NIC Link is Up 1 Mbps [6.550449] vmxnet3 :14:00.0 eth3: intr type 3, mode 0, 2 vectors allocated [6.550716] vmxnet3 :14:00.0 eth3: NIC Link is Up 1 Mbps Realy wrong order? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/341006 Title: ease cloning of virtual images by disabling mac address rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/341006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 341006] Re: ease cloning of virtual images by disabling mac address rules
I know it's too old, but today i have big problem without persistent net rules. (sorry for my English) I have VMWare 5.5.0 host and Ubuntu 12.04 guest with many virtual NICs (with MACs 00:0c:29*) Today I updated kernel from 3.13.0-32 to 3.13.0-45 Rebooted VM Lost connection to my VM over one of the NIC (which is connected to internet). I connected to VMWare host (by VMware vSphere Client) and to Ubuntu guest (over LAN virtual NIC who worked) And I saw, that NICs in Ubuntu guest have correct order and matches IP- ETHnumber like before kernel update and reboot, but IP-ETH does not match MAC-VLAN bindings in VMWare, except eth0 (LAN NIC). I don't understend how it happened, as I remember, I updated kernel before many times (to 3.13.0-32) without problems. So today I am commenting line after ignore VMWare virtual interfaces to make IP-ETH-MAC match persistent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/341006 Title: ease cloning of virtual images by disabling mac address rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/341006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314245] Re: Missing r8169 firmware warning when installing Trusty kernel
To solve problem please install linux-firmware_1.127.5_all.deb from http://packages.ubuntu.com/trusty-updates/linux-firmware Why its not avaible in 12.04.5 I don't know. How we can use Trusty kernel without Trysty's linux-firmware? Need to update linux-firmware for 12.04.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314245 Title: Missing r8169 firmware warning when installing Trusty kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-trusty/+bug/1314245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314245] Re: Missing r8169 firmware warning when installing Trusty kernel
Also, if your Ubuntu host is VMware guest, then you will need to install open-vm-tools and open-vm-dkms from raring: http://packages.ubuntu.com/raring/open-vm-tools http://packages.ubuntu.com/raring/open-vm-dkms -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314245 Title: Missing r8169 firmware warning when installing Trusty kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-trusty/+bug/1314245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241612] Re: 'service ddclient stop' doesn't work
Confirm. Ubuntu 12.04.04 64-bit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241612 Title: 'service ddclient stop' doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddclient/+bug/1241612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241612] Re: 'service ddclient stop' doesn't work
Change in /etc/init.d/ddclient line NAME=ddclient to NAME=ddclient - slee -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241612 Title: 'service ddclient stop' doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddclient/+bug/1241612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252542] Re: ata failed command: WRITE FPDMA QUEUED
After updating to ubuntu kernel 3.11.0 problem gone -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252542 Title: ata failed command: WRITE FPDMA QUEUED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1252542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
Same at server HP ProLiant DL320e Gen8 v2, BIOS P80 08/28/2013 with two hard drives ST500NM0011 and ST2000NC001-1DY164 Problems only with ST2000NC001! ST500NM0011 working fine. ** Attachment added: ubuntu-bug linux https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550559/+attachment/3911747/+files/report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252542] [NEW] ata failed command: WRITE FPDMA QUEUED
Public bug reported:
Ubuntu Server 12.04.3
Kernel 3.8.0-33-generic #48~precise1-Ubuntu x64
HP ProLiant Gen8 V2
HDD Model=ST500NM0011, FwRev=SN03
HDD Model=ST2000NC001-1DY164, FwRev=CN01
HDD ST500NM0011 (on ata1) working fine (without erros).
But with ST2000NC001 (on ata2) I have problem.
Nov 17 04:25:19 gwlin1 kernel: [208881.849360] ata2.00: exception Emask 0x0
SAct 0x7fc0007f SErr 0x0 action 0x6 frozen
Nov 17 04:25:19 gwlin1 kernel: [208881.865777] ata2.00: failed command: WRITE
FPDMA QUEUED
Nov 17 04:25:19 gwlin1 kernel: [208881.874024] ata2.00: cmd
61/08:00:18:08:80/00:00:7e:00:00/40 tag 0 ncq 4096 out
Nov 17 04:25:19 gwlin1 kernel: [208881.874024] res
40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Nov 17 04:25:19 gwlin1 kernel: [208881.907389] ata2.00: status: { DRDY }
(many messages like 4 before)
Nov 17 04:25:20 gwlin1 kernel: [208882.653060] ata2: hard resetting link
Nov 17 04:25:20 gwlin1 kernel: [208882.969287] ata2: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
Nov 17 04:25:20 gwlin1 kernel: [208882.970745] ata2.00: configured for UDMA/133
Nov 17 04:25:20 gwlin1 kernel: [208882.970748] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970749] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970750] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970751] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970752] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970753] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970756] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970757] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970759] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970761] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970762] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970764] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970766] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970767] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970769] ata2.00: device reported invalid
CHS sector 0
Nov 17 04:25:20 gwlin1 kernel: [208882.970775] ata2: EH complete
Workaround is to add kernel startup parameter libata.force=2.00:noncq
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1
ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
Uname: Linux 3.8.0-33-generic x86_64
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Nov 18 21:09 seq
crw-rw---T 1 root audio 116, 33 Nov 18 21:09 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Nov 19 08:41:55 2013
HibernationDevice: RESUME=UUID=ccbdb955-a7d5-4b6e-833f-f613ab76161a
InstallationMedia: Ubuntu-Server 12.04.3 LTS Precise Pangolin - Release amd64
(20130820.2)
MachineType: HP ProLiant DL320e Gen8 v2
MarkForUpload: True
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic
root=UUID=454b668a-7eaa-4ac0-b572-e434c6429057 ro libata.force=2.00:noncq
RelatedPackageVersions:
linux-restricted-modules-3.8.0-33-generic N/A
linux-backports-modules-3.8.0-33-generic N/A
linux-firmware1.79.7
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
dmi.bios.date: 08/28/2013
dmi.bios.vendor: HP
dmi.bios.version: P80
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrP80:bd08/28/2013:svnHP:pnProLiantDL320eGen8v2:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL320e Gen8 v2
dmi.sys.vendor: HP
** Affects: linux-lts-raring (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise qa-kernel-lts-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252542
Title:
ata failed command: WRITE FPDMA QUEUED
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1252542/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
#0 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) where #0 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8f43781b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f8f46bcf53b in dump_core () at lib/fault.c:391 #3 0x7f8f46bddc01 in smb_panic (why=optimized out) at lib/util.c:1133 #4 0x7f8f46bcee88 in fault_report (sig=6) at lib/fault.c:53 #5 sig_fault (sig=6) at lib/fault.c:76 #6 signal handler called #7 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7f8f43781b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7f8f437bc39e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x7f8f437c6b96 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x7f8f45f1bb78 in gss_release_buffer () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #12 0x7f8f46c4b182 in gse_get_pac_blob (gse_ctx=optimized out, mem_ctx=0x7f8f4778a4e0, pac_blob=optimized out) at librpc/crypto/gse.c:731 #13 0x7f8f46ae21ab in gssapi_server_get_user_info (gse_ctx=0x7f8f47790030, mem_ctx=0x7f8f47786660, client_id=0x7f8f477705e8, server_info=0x7f8f47786688) at rpc_server/dcesrv_gssapi.c:127 #14 0x7f8f46ad667d in pipe_gssapi_verify_final (mem_ctx=0x7f8f47786660, gse_ctx=0x7f8f47790030, client_id=0x7f8f477705e8, session_info=0x7f8f47786688) at rpc_server/srv_pipe.c:734 #15 0x7f8f46ad806a in pipe_auth_verify_final (p=0x7f8f47786660) at rpc_server/srv_pipe.c:814 #16 0x7f8f46ada25b in api_pipe_alter_context (pkt=0x7f8f47790f30, p=0x7f8f47786660) at rpc_server/srv_pipe.c:1403 #17 process_complete_pdu (p=0x7f8f47786660) at rpc_server/srv_pipe.c:1955 #18 0x7f8f46ada94b in process_incoming_data (p=0x7f8f47786660, data=0x7f8f47792db4 \270\020\270\020, n=optimized out) at rpc_server/srv_pipe_hnd.c:218 #19 0x7f8f46adb02e in write_to_internal_pipe (n=177, data=0x7f8f47792db4 \270\020\270\020, p=0x7f8f47786660) at rpc_server/srv_pipe_hnd.c:244 #20 np_write_send (mem_ctx=optimized out, ev=0x7f8f47770520, handle=optimized out, data=optimized out, len=177) at rpc_server/srv_pipe_hnd.c:538 #21 0x7f8f468ef967 in reply_pipe_write_and_X (req=0x7f8f47792eb0) at smbd/pipes.c:322 #22 0x7f8f468f9308 in reply_write_and_X (req=0x7f8f47792eb0) at smbd/reply.c:4529 #23 0x7f8f4693bfa4 in switch_message (type=47 '/', req=0x7f8f47792eb0, size=245) at smbd/process.c:1574 #24 0x7f8f4693c3bb in construct_reply (deferred_pcd=0x0, encrypted=false, seqnum=optimized out, unread_bytes=0, size=245, inbuf=0x0, sconn=0x7f8f477705e0) at smbd/process.c:1610 #25 process_smb (sconn=0x7f8f477705e0, inbuf=optimized out, nread=245, unread_bytes=0, seqnum=optimized out, encrypted=false, deferred_pcd=0x0) at smbd/process.c:1688 #26 0x7f8f4693c7d3 in smbd_server_connection_read_handler (conn=0x7f8f477705e0, fd=24) at smbd/process.c:2317 #27 0x7f8f46bed8ae in run_events_poll (num_pfds=2, pfds=0x7f8f4777b040, pollrtn=optimized out, ev=0x7f8f47770520) at lib/events.c:286 #28 run_events_poll (ev=0x7f8f47770520, pollrtn=optimized out, pfds=0x7f8f4777b040, num_pfds=2) at lib/events.c:184 #29 0x7f8f4693df42 in smbd_server_connection_loop_once (conn=0x7f8f477705e0) at smbd/process.c:1017 #30 smbd_process (sconn=0x7f8f477705e0) at smbd/process.c:3158 #31 0x7f8f46e4b66f in smbd_accept_connection (ev=optimized out, fde=optimized out, flags=optimized out, private_data=optimized out) at smbd/server.c:511 #32 0x7f8f46bed8ae in run_events_poll (num_pfds=3, pfds=0x7f8f477732e0, pollrtn=optimized out, ev=0x7f8f47770520) at lib/events.c:286 #33 run_events_poll (ev=0x7f8f47770520, pollrtn=optimized out, pfds=0x7f8f477732e0, num_pfds=3) at lib/events.c:184 #34 0x7f8f46beda4a in s3_event_loop_once (ev=0x7f8f47770520, location=optimized out) at lib/events.c:349 #35 0x7f8f46bee5d0 in _tevent_loop_once (ev=0x7f8f47770520, location=0x7f8f470502d7 smbd/server.c:844) at ../lib/tevent/tevent.c:494 #36 0x7f8f468bc030 in smbd_parent_loop (parent=optimized out) at smbd/server.c:844 #37 main (argc=optimized out, argv=optimized out) at smbd/server.c:1326 ** Attachment removed: logs, configs https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+attachment/3470091/+files/sambaerr.tar.gz ** Changed in: samba (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
I have installed samba-dbg and dbg packages. If I can help to debug this problem, tell me what to do. Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
#0 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) where #0 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8f43781b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f8f46bcf53b in dump_core () at lib/fault.c:391 #3 0x7f8f46bddc01 in smb_panic (why=optimized out) at lib/util.c:1133 #4 0x7f8f46bcee88 in fault_report (sig=6) at lib/fault.c:53 #5 sig_fault (sig=6) at lib/fault.c:76 #6 signal handler called #7 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7f8f43781b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7f8f437bc39e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x7f8f437c6b96 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x7f8f45f1bb78 in gss_release_buffer () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #12 0x7f8f46c4b182 in gse_get_pac_blob (gse_ctx=optimized out, mem_ctx=0x7f8f4778a4e0, pac_blob=optimized out) at librpc/crypto/gse.c:731 #13 0x7f8f46ae21ab in gssapi_server_get_user_info (gse_ctx=0x7f8f47790030, mem_ctx=0x7f8f47786660, client_id=0x7f8f477705e8, server_info=0x7f8f47786688) at rpc_server/dcesrv_gssapi.c:127 #14 0x7f8f46ad667d in pipe_gssapi_verify_final (mem_ctx=0x7f8f47786660, gse_ctx=0x7f8f47790030, client_id=0x7f8f477705e8, session_info=0x7f8f47786688) at rpc_server/srv_pipe.c:734 #15 0x7f8f46ad806a in pipe_auth_verify_final (p=0x7f8f47786660) at rpc_server/srv_pipe.c:814 #16 0x7f8f46ada25b in api_pipe_alter_context (pkt=0x7f8f47790f30, p=0x7f8f47786660) at rpc_server/srv_pipe.c:1403 #17 process_complete_pdu (p=0x7f8f47786660) at rpc_server/srv_pipe.c:1955 #18 0x7f8f46ada94b in process_incoming_data (p=0x7f8f47786660, data=0x7f8f47792db4 \270\020\270\020, n=optimized out) at rpc_server/srv_pipe_hnd.c:218 #19 0x7f8f46adb02e in write_to_internal_pipe (n=177, data=0x7f8f47792db4 \270\020\270\020, p=0x7f8f47786660) at rpc_server/srv_pipe_hnd.c:244 #20 np_write_send (mem_ctx=optimized out, ev=0x7f8f47770520, handle=optimized out, data=optimized out, len=177) at rpc_server/srv_pipe_hnd.c:538 #21 0x7f8f468ef967 in reply_pipe_write_and_X (req=0x7f8f47792eb0) at smbd/pipes.c:322 #22 0x7f8f468f9308 in reply_write_and_X (req=0x7f8f47792eb0) at smbd/reply.c:4529 #23 0x7f8f4693bfa4 in switch_message (type=47 '/', req=0x7f8f47792eb0, size=245) at smbd/process.c:1574 #24 0x7f8f4693c3bb in construct_reply (deferred_pcd=0x0, encrypted=false, seqnum=optimized out, unread_bytes=0, size=245, inbuf=0x0, sconn=0x7f8f477705e0) at smbd/process.c:1610 #25 process_smb (sconn=0x7f8f477705e0, inbuf=optimized out, nread=245, unread_bytes=0, seqnum=optimized out, encrypted=false, deferred_pcd=0x0) at smbd/process.c:1688 #26 0x7f8f4693c7d3 in smbd_server_connection_read_handler (conn=0x7f8f477705e0, fd=24) at smbd/process.c:2317 #27 0x7f8f46bed8ae in run_events_poll (num_pfds=2, pfds=0x7f8f4777b040, pollrtn=optimized out, ev=0x7f8f47770520) at lib/events.c:286 #28 run_events_poll (ev=0x7f8f47770520, pollrtn=optimized out, pfds=0x7f8f4777b040, num_pfds=2) at lib/events.c:184 #29 0x7f8f4693df42 in smbd_server_connection_loop_once (conn=0x7f8f477705e0) at smbd/process.c:1017 #30 smbd_process (sconn=0x7f8f477705e0) at smbd/process.c:3158 #31 0x7f8f46e4b66f in smbd_accept_connection (ev=optimized out, fde=optimized out, flags=optimized out, private_data=optimized out) at smbd/server.c:511 #32 0x7f8f46bed8ae in run_events_poll (num_pfds=3, pfds=0x7f8f477732e0, pollrtn=optimized out, ev=0x7f8f47770520) at lib/events.c:286 #33 run_events_poll (ev=0x7f8f47770520, pollrtn=optimized out, pfds=0x7f8f477732e0, num_pfds=3) at lib/events.c:184 #34 0x7f8f46beda4a in s3_event_loop_once (ev=0x7f8f47770520, location=optimized out) at lib/events.c:349 #35 0x7f8f46bee5d0 in _tevent_loop_once (ev=0x7f8f47770520, location=0x7f8f470502d7 smbd/server.c:844) at ../lib/tevent/tevent.c:494 #36 0x7f8f468bc030 in smbd_parent_loop (parent=optimized out) at smbd/server.c:844 #37 main (argc=optimized out, argv=optimized out) at smbd/server.c:1326 ** Attachment removed: logs, configs https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+attachment/3470091/+files/sambaerr.tar.gz ** Changed in: samba (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/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
I have installed samba-dbg and dbg packages. If I can help to debug this problem, tell me what to do. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094438] [NEW] Samba crashes invalid pointer: 0x00007f0bc3de7590
Public bug reported: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Attachment added: logs, configs https://bugs.launchpad.net/bugs/1094438/+attachment/3470091/+files/sambaerr.tar.gz ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain + Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. Samba crushes after opening shared folder from windows workstation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. - Samba crushes after opening shared folder from windows workstation. + We have 2 same server with same config (differents only in hostname). + + Samba crushes after opening shared folder from windows workstation on + both servers. ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. - We have 2 same server with same config (differents only in hostname). + We have two of the same server with the same configuration (differents + only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. + + BACKTRACE: 30 stack frames: +#0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] +#1 smbd(smb_panic+0x25) [0x7f4533d61bc5] +#2 smbd(+0x409e88) [0x7f4533d52e88] +#3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] +#4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] +#5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] +#6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] +#7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] +#8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] +#9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] +#10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] +#11 smbd(+0x31167d) [0x7f4533c5a67d] +#12 smbd(+0x31306a) [0x7f4533c5c06a] +#13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] +#14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] +#15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] +#16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] +#17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] +#18 smbd(+0x176fa4) [0x7f4533abffa4] +#19 smbd(+0x1773bb) [0x7f4533ac03bb] +#20 smbd(+0x1777d3) [0x7f4533ac07d3] +#21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] +#22 smbd(smbd_process+0x812) [0x7f4533ac1f42] +#23 smbd(+0x68666f) [0x7f4533fcf66f] +#24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] +#25 smbd(+0x428a4a) [0x7f4533d71a4a] +#26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] +#27 smbd(main+0xed0) [0x7f4533a40030] +#28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] +#29 smbd(+0xf7515) [0x7f4533a40515] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). - Samba crushes after opening shared folder from windows workstation on - both servers. + Samba crushes everytime after opening shared folder from windows + workstation on both servers. - BACKTRACE: 30 stack frames: -#0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] -#1 smbd(smb_panic+0x25) [0x7f4533d61bc5] -#2 smbd(+0x409e88) [0x7f4533d52e88] -#3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] -#4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] -#5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] -#6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] -#7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] -#8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] -#9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] -#10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] -#11 smbd(+0x31167d) [0x7f4533c5a67d] -#12 smbd(+0x31306a) [0x7f4533c5c06a] -#13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] -#14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] -#15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] -#16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] -#17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] -#18 smbd(+0x176fa4) [0x7f4533abffa4] -#19 smbd(+0x1773bb) [0x7f4533ac03bb] -#20 smbd(+0x1777d3) [0x7f4533ac07d3] -#21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] -#22 smbd(smbd_process+0x812) [0x7f4533ac1f42] -#23 smbd(+0x68666f) [0x7f4533fcf66f] -#24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] -#25 smbd(+0x428a4a) [0x7f4533d71a4a] -#26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] -#27 smbd(main+0xed0) [0x7f4533a40030] -#28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] -#29 smbd(+0xf7515) [0x7f4533a40515] + BACKTRACE: 30 stack frames: + #0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] + #1 smbd(smb_panic+0x25) [0x7f4533d61bc5] + #2 smbd(+0x409e88) [0x7f4533d52e88] + #3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] + #4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] + #5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] + #6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] + #7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] + #8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] + #9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] + #10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] + #11 smbd(+0x31167d) [0x7f4533c5a67d] + #12 smbd(+0x31306a) [0x7f4533c5c06a] + #13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] + #14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] + #15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] + #16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] + #17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] + #18 smbd(+0x176fa4) [0x7f4533abffa4] + #19 smbd(+0x1773bb) [0x7f4533ac03bb] + #20 smbd(+0x1777d3) [0x7f4533ac07d3] + #21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] + #22 smbd(smbd_process+0x812) [0x7f4533ac1f42] + #23 smbd(+0x68666f) [0x7f4533fcf66f] + #24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] + #25 smbd(+0x428a4a) [0x7f4533d71a4a] + #26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] + #27 smbd(main+0xed0) [0x7f4533a40030] + #28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] + #29 smbd(+0xf7515) [0x7f4533a40515] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
samba 2:3.6.6-3ubuntu5 from quantal installed in 12.04 = no probles! No coredumps. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] [NEW] Samba crashes invalid pointer: 0x00007f0bc3de7590
Public bug reported: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Attachment added: logs, configs https://bugs.launchpad.net/bugs/1094438/+attachment/3470091/+files/sambaerr.tar.gz ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain + Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. Samba crushes after opening shared folder from windows workstation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. - Samba crushes after opening shared folder from windows workstation. + We have 2 same server with same config (differents only in hostname). + + Samba crushes after opening shared folder from windows workstation on + both servers. ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. - We have 2 same server with same config (differents only in hostname). + We have two of the same server with the same configuration (differents + only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. + + BACKTRACE: 30 stack frames: +#0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] +#1 smbd(smb_panic+0x25) [0x7f4533d61bc5] +#2 smbd(+0x409e88) [0x7f4533d52e88] +#3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] +#4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] +#5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] +#6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] +#7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] +#8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] +#9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] +#10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] +#11 smbd(+0x31167d) [0x7f4533c5a67d] +#12 smbd(+0x31306a) [0x7f4533c5c06a] +#13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] +#14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] +#15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] +#16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] +#17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] +#18 smbd(+0x176fa4) [0x7f4533abffa4] +#19 smbd(+0x1773bb) [0x7f4533ac03bb] +#20 smbd(+0x1777d3) [0x7f4533ac07d3] +#21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] +#22 smbd(smbd_process+0x812) [0x7f4533ac1f42] +#23 smbd(+0x68666f) [0x7f4533fcf66f] +#24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] +#25 smbd(+0x428a4a) [0x7f4533d71a4a] +#26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] +#27 smbd(main+0xed0) [0x7f4533a40030] +#28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] +#29 smbd(+0xf7515) [0x7f4533a40515] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). - Samba crushes after opening shared folder from windows workstation on - both servers. + Samba crushes everytime after opening shared folder from windows + workstation on both servers. - BACKTRACE: 30 stack frames: -#0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] -#1 smbd(smb_panic+0x25) [0x7f4533d61bc5] -#2 smbd(+0x409e88) [0x7f4533d52e88] -#3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] -#4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] -#5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] -#6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] -#7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] -#8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] -#9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] -#10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] -#11 smbd(+0x31167d) [0x7f4533c5a67d] -#12 smbd(+0x31306a) [0x7f4533c5c06a] -#13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] -#14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] -#15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] -#16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] -#17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] -#18 smbd(+0x176fa4) [0x7f4533abffa4] -#19 smbd(+0x1773bb) [0x7f4533ac03bb] -#20 smbd(+0x1777d3) [0x7f4533ac07d3] -#21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] -#22 smbd(smbd_process+0x812) [0x7f4533ac1f42] -#23 smbd(+0x68666f) [0x7f4533fcf66f] -#24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] -#25 smbd(+0x428a4a) [0x7f4533d71a4a] -#26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] -#27 smbd(main+0xed0) [0x7f4533a40030] -#28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] -#29 smbd(+0xf7515) [0x7f4533a40515] + BACKTRACE: 30 stack frames: + #0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] + #1 smbd(smb_panic+0x25) [0x7f4533d61bc5] + #2 smbd(+0x409e88) [0x7f4533d52e88] + #3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] + #4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] + #5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] + #6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] + #7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] + #8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] + #9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] + #10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] + #11 smbd(+0x31167d) [0x7f4533c5a67d] + #12 smbd(+0x31306a) [0x7f4533c5c06a] + #13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] + #14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] + #15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] + #16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] + #17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] + #18 smbd(+0x176fa4) [0x7f4533abffa4] + #19 smbd(+0x1773bb) [0x7f4533ac03bb] + #20 smbd(+0x1777d3) [0x7f4533ac07d3] + #21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] + #22 smbd(smbd_process+0x812) [0x7f4533ac1f42] + #23 smbd(+0x68666f) [0x7f4533fcf66f] + #24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] + #25 smbd(+0x428a4a) [0x7f4533d71a4a] + #26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] + #27 smbd(main+0xed0) [0x7f4533a40030] + #28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] + #29 smbd(+0xf7515) [0x7f4533a40515] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
samba 2:3.6.6-3ubuntu5 from quantal installed in 12.04 = no probles! No coredumps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978356] Re: squid3 gets killed at startup with dnsmasq and no networkmanager
Fixed for me: Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/978356 Title: squid3 gets killed at startup with dnsmasq and no networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/978356/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 995523] Re: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
This bug also fixed by patch in bug #978356 Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978356] Re: squid3 gets killed at startup with dnsmasq and no networkmanager
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/978356 Title: squid3 gets killed at startup with dnsmasq and no networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/978356/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 988802] Re: squid3 killed by ABRT signal. assertion failed: disk.cc377: fd = 0
This bug also fixed by patch in bug #978356 Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/988802 Title: squid3 killed by ABRT signal. assertion failed: disk.cc377: fd = 0 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/988802/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978356] Re: squid3 gets killed at startup with dnsmasq and no networkmanager
Fixed for me: Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/978356 Title: squid3 gets killed at startup with dnsmasq and no networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/978356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995523] Re: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
This bug also fixed by patch in bug #978356 Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988802] Re: squid3 killed by ABRT signal. assertion failed: disk.cc377: fd = 0
This bug also fixed by patch in bug #978356 Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988802 Title: squid3 killed by ABRT signal. assertion failed: disk.cc377: fd = 0 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/988802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978356] Re: squid3 gets killed at startup with dnsmasq and no networkmanager
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/978356 Title: squid3 gets killed at startup with dnsmasq and no networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/978356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928774] Re: Add lp-solve to dependency
** Changed in: aptitude (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/928774 Title: Add lp-solve to dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/928774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928774] [NEW] Add lp-solve to dependency
Public bug reported: Please add package lp-solve to dependency list. If package lp-solve is not installed, then dependency resolver in aptitude not working. Errors are dislpayed. Description:Ubuntu precise (development branch) Release:12.04 aptitude 0.6.4-1ubuntu5 ** Affects: aptitude (Ubuntu) Importance: Undecided Status: New ** Tags: dependency lp-solve -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/928774 Title: Add lp-solve to dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/928774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839490] Re: NUT is not shutdown UPS
I have nut version 2.6.0-1ubuntu3 upsmon forks 2 instances - yes, I have they. But why killpower is setting by unprivileded instance (nut)? I confirm, SHUTDOWNCMD is launched proper (by privileged instance). I have 3 servers on Ubuntu 11.04 with UPS APC on each. Config files,daemons are identical. Differents only in UPS. APC SmartUPS 750i (SUA750I), BackUPS CS 500 (BK500EI), BackUPS ES 550. All connected with driver = usbhid-ups. So, many info: root@gwlin:/etc/nut# ps faux | grep ups root 231 0.0 0.1 2412 556 ?SSep03 0:00 upstart-udev-bridge --daemon root 668 0.0 0.0 2412 468 ?SSep03 0:00 upstart-socket-bridge --daemon root 12368 0.0 0.1 5304 852 pts/1S+ 15:22 0:00 \_ grep --color=auto ups nut 2510 0.0 0.0 2196 444 ?Ss Sep03 5:20 /lib/nut/usbhid-ups -a ippon nut 2512 0.0 0.0 2128 456 ?Ss Sep03 0:53 /sbin/upsd root 2514 0.0 0.1 2108 568 ?Ss Sep03 0:00 /sbin/upsmon nut 2516 0.0 0.1 2108 576 ?SSep03 0:30 \_ /sbin/upsmon root@gwlin:/etc/nut# cat /etc/nut/nut.conf | egrep -v (^#.*|^$) MODE=netserver root@gwlin:/etc/nut# cat /etc/nut/ups.conf | egrep -v (^#.*|^$) [ippon] driver = usbhid-ups port = auto root@gwlin:/etc/nut# cat /etc/nut/upsd.conf | egrep -v (^#.*|^$) LISTEN 127.0.0.1 LISTEN 10.0.0.1 root@gwlin:/etc/nut# cat /etc/nut/upsd.users | egrep -v (^#.*|^$) [local_mon] password = XX upsmon master [server_mon] password = XX upsmon slave [root] password = XX actions = SET instcmds = ALL root@gwlin:/etc/nut# cat /etc/nut/upsmon.conf | egrep -v (^#.*|^$) MONITOR ippon@localhost 1 local_mon XX master MINSUPPLIES 1 SHUTDOWNCMD /sbin/shutdown -h +0 NOTIFYCMD /usr/local/bin/upsmail POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/nut/killpower NOTIFYFLAG ONLINE EXEC+SYSLOG NOTIFYFLAG ONBATT EXEC+SYSLOG NOTIFYFLAG LOWBATT EXEC+SYSLOG NOTIFYFLAG FSD EXEC+SYSLOG NOTIFYFLAG COMMOK EXEC+SYSLOG NOTIFYFLAG COMMBAD EXEC+SYSLOG NOTIFYFLAG SHUTDOWN EXEC+SYSLOG NOTIFYFLAG REPLBATT EXEC+SYSLOG NOTIFYFLAG NOCOMM EXEC+SYSLOG RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 root@gwlin:/etc/default# cat ./halt | egrep -v (^#.*|^$) HALT=poweroff root@gwlin:/etc/init.d# upsmon -K Network UPS Tools upsmon 2.6.0 UPS: ippon@localhost (master) (power value 1) Using power down flag file /etc/nut/killpower Power down flag is not set -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839490] Re: NUT is not shutdown UPS
I have nut version 2.6.0-1ubuntu3 upsmon forks 2 instances - yes, I have they. But why killpower is setting by unprivileded instance (nut)? I confirm, SHUTDOWNCMD is launched proper (by privileged instance). I have 3 servers on Ubuntu 11.04 with UPS APC on each. Config files,daemons are identical. Differents only in UPS. APC SmartUPS 750i (SUA750I), BackUPS CS 500 (BK500EI), BackUPS ES 550. All connected with driver = usbhid-ups. So, many info: root@gwlin:/etc/nut# ps faux | grep ups root 231 0.0 0.1 2412 556 ?SSep03 0:00 upstart-udev-bridge --daemon root 668 0.0 0.0 2412 468 ?SSep03 0:00 upstart-socket-bridge --daemon root 12368 0.0 0.1 5304 852 pts/1S+ 15:22 0:00 \_ grep --color=auto ups nut 2510 0.0 0.0 2196 444 ?Ss Sep03 5:20 /lib/nut/usbhid-ups -a ippon nut 2512 0.0 0.0 2128 456 ?Ss Sep03 0:53 /sbin/upsd root 2514 0.0 0.1 2108 568 ?Ss Sep03 0:00 /sbin/upsmon nut 2516 0.0 0.1 2108 576 ?SSep03 0:30 \_ /sbin/upsmon root@gwlin:/etc/nut# cat /etc/nut/nut.conf | egrep -v (^#.*|^$) MODE=netserver root@gwlin:/etc/nut# cat /etc/nut/ups.conf | egrep -v (^#.*|^$) [ippon] driver = usbhid-ups port = auto root@gwlin:/etc/nut# cat /etc/nut/upsd.conf | egrep -v (^#.*|^$) LISTEN 127.0.0.1 LISTEN 10.0.0.1 root@gwlin:/etc/nut# cat /etc/nut/upsd.users | egrep -v (^#.*|^$) [local_mon] password = XX upsmon master [server_mon] password = XX upsmon slave [root] password = XX actions = SET instcmds = ALL root@gwlin:/etc/nut# cat /etc/nut/upsmon.conf | egrep -v (^#.*|^$) MONITOR ippon@localhost 1 local_mon XX master MINSUPPLIES 1 SHUTDOWNCMD /sbin/shutdown -h +0 NOTIFYCMD /usr/local/bin/upsmail POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/nut/killpower NOTIFYFLAG ONLINE EXEC+SYSLOG NOTIFYFLAG ONBATT EXEC+SYSLOG NOTIFYFLAG LOWBATT EXEC+SYSLOG NOTIFYFLAG FSD EXEC+SYSLOG NOTIFYFLAG COMMOK EXEC+SYSLOG NOTIFYFLAG COMMBAD EXEC+SYSLOG NOTIFYFLAG SHUTDOWN EXEC+SYSLOG NOTIFYFLAG REPLBATT EXEC+SYSLOG NOTIFYFLAG NOCOMM EXEC+SYSLOG RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 root@gwlin:/etc/default# cat ./halt | egrep -v (^#.*|^$) HALT=poweroff root@gwlin:/etc/init.d# upsmon -K Network UPS Tools upsmon 2.6.0 UPS: ippon@localhost (master) (power value 1) Using power down flag file /etc/nut/killpower Power down flag is not set -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839490] Re: NUT is not shutdown UPS
** Description changed: Description:Ubuntu 11.04 Release:11.04 nut version 2.6.0-1ubuntu3 - Problem: + Problem: upsmon working under nut user (not root). nut user can't create file /etc/killpower Example: 1) Mains out. UPS on battery 2) Battery low. set FSD 3) upsmon executes shutdowncmd but fails to create /etc/killpower 4) /etc/init.d/halt executes /etc/init.d/ups-monitor poweroff 5) /etc/init.d/ups-monitor poweroff executes upsmon -K to check /etc/killpower (but file does not exist) 6) not sending shutdown command to UPS (upsdrvctl shutdown is not executed) 7) system halted, but UPS stays on battery 8) mains come back, ups going on mains, but load is not switched off/on - 9) PC stay OFF (need manual start) + 9) PC stays OFF (need manual start) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839490] Re: NUT is not shutdown UPS
** Description changed: Description:Ubuntu 11.04 Release:11.04 nut version 2.6.0-1ubuntu3 - Problem: + Problem: upsmon working under nut user (not root). nut user can't create file /etc/killpower Example: 1) Mains out. UPS on battery 2) Battery low. set FSD 3) upsmon executes shutdowncmd but fails to create /etc/killpower 4) /etc/init.d/halt executes /etc/init.d/ups-monitor poweroff 5) /etc/init.d/ups-monitor poweroff executes upsmon -K to check /etc/killpower (but file does not exist) 6) not sending shutdown command to UPS (upsdrvctl shutdown is not executed) 7) system halted, but UPS stays on battery 8) mains come back, ups going on mains, but load is not switched off/on - 9) PC stay OFF (need manual start) + 9) PC stays OFF (need manual start) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839490] [NEW] NUT is not shutdown UPS
Public bug reported: Description:Ubuntu 11.04 Release:11.04 nut version 2.6.0-1ubuntu3 Problem: upsmon working under nut user (not root). nut user can't create file /etc/killpower Example: 1) Mains out. UPS on battery 2) Battery low. set FSD 3) upsmon executes shutdowncmd but fails to create /etc/killpower 4) /etc/init.d/halt executes /etc/init.d/ups-monitor poweroff 5) /etc/init.d/ups-monitor poweroff executes upsmon -K to check /etc/killpower (but file does not exist) 6) not sending shutdown command to UPS (upsdrvctl shutdown is not executed) 7) system halted, but UPS stays on battery 8) mains come back, ups going on mains, but load is not switched off/on 9) PC stay OFF (need manual start) ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839490] Re: NUT is not shutdown UPS
Temp. solution: 1) rm -f /etc/killpower 2) chmod -R g+w /etc/nut/ 3) edit upsmon.conf and change POWERDOWNFLAG /etc/nut/killpower 4) service nut restart After this all fine! UPS shutdowns correctly. PC starts up when UPS goes on. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839509] [NEW] nut can not log to syslog when shutdown
Public bug reported: Ubuntu 11.04 NUT 2.6.0 System shutting down (battery low, FSD set) and executes /etc/init.d /ups-monitor poweroff ups-monitor script contains section poweroff. in this section we can see log_daemon_msg which sends info to syslog but rsyslogd already stopped. This is in syslog when shutdown: Sep 2 17:37:58 gwlin upsmon[1229]: Signal 10: User requested FSD Sep 2 17:37:58 gwlin upsd[1225]: Client local_mon@127.0.0.1 set FSD on UPS [ippon] Sep 2 17:37:58 gwlin upsmon[1229]: Executing automatic power-fail shutdown Sep 2 17:37:58 gwlin upsmon[1229]: Auto logout and shutdown proceeding Sep 2 17:38:03 gwlin kernel: Kernel logging (proc) stopped. Sep 2 17:38:03 gwlin rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=374 x-info=http://www.rsyslog.com;] exiting on signal 15. ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839509] Re: nut can not log to syslog when shutdown
Sorry. Expected messages like Shutting down the UPS ..., Waiting for UPS to cut the power, ... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839490] [NEW] NUT is not shutdown UPS
Public bug reported: Description:Ubuntu 11.04 Release:11.04 nut version 2.6.0-1ubuntu3 Problem: upsmon working under nut user (not root). nut user can't create file /etc/killpower Example: 1) Mains out. UPS on battery 2) Battery low. set FSD 3) upsmon executes shutdowncmd but fails to create /etc/killpower 4) /etc/init.d/halt executes /etc/init.d/ups-monitor poweroff 5) /etc/init.d/ups-monitor poweroff executes upsmon -K to check /etc/killpower (but file does not exist) 6) not sending shutdown command to UPS (upsdrvctl shutdown is not executed) 7) system halted, but UPS stays on battery 8) mains come back, ups going on mains, but load is not switched off/on 9) PC stay OFF (need manual start) ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839490] Re: NUT is not shutdown UPS
Temp. solution: 1) rm -f /etc/killpower 2) chmod -R g+w /etc/nut/ 3) edit upsmon.conf and change POWERDOWNFLAG /etc/nut/killpower 4) service nut restart After this all fine! UPS shutdowns correctly. PC starts up when UPS goes on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839509] [NEW] nut can not log to syslog when shutdown
Public bug reported: Ubuntu 11.04 NUT 2.6.0 System shutting down (battery low, FSD set) and executes /etc/init.d /ups-monitor poweroff ups-monitor script contains section poweroff. in this section we can see log_daemon_msg which sends info to syslog but rsyslogd already stopped. This is in syslog when shutdown: Sep 2 17:37:58 gwlin upsmon[1229]: Signal 10: User requested FSD Sep 2 17:37:58 gwlin upsd[1225]: Client local_mon@127.0.0.1 set FSD on UPS [ippon] Sep 2 17:37:58 gwlin upsmon[1229]: Executing automatic power-fail shutdown Sep 2 17:37:58 gwlin upsmon[1229]: Auto logout and shutdown proceeding Sep 2 17:38:03 gwlin kernel: Kernel logging (proc) stopped. Sep 2 17:38:03 gwlin rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=374 x-info=http://www.rsyslog.com;] exiting on signal 15. ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839509] Re: nut can not log to syslog when shutdown
Sorry. Expected messages like Shutting down the UPS ..., Waiting for UPS to cut the power, ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315576] Re: screen resolution incorrect after switching off/on flat panel notebook
No problem when using binary driver from nvidia! -- screen resolution incorrect after switching off/on flat panel notebook https://bugs.launchpad.net/bugs/315576 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315576] Re: screen resolution incorrect after switching off/on flat panel notebook
All files is attached in archive outputs.zip ** Attachment added: outputs.zip http://launchpadlibrarian.net/21280839/outputs.zip -- screen resolution incorrect after switching off/on flat panel notebook https://bugs.launchpad.net/bugs/315576 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315371] [NEW] xserver-xorg-core conflicts with xserver-xorg-video-4 [provided by nvidia-glx-96 96.43.09-0ubuntu2]
Public bug reported: Binary package hint: nvidia-glx-96 After update Xorg (packages xorg, server-xorg, xserver-xorg-core) I can't install nvidia-glx-96 96.43.09-0ubuntu2. My Xorg packages is: xorg [1:7.4~5ubuntu10 (jaunty, now)] xserver-xorg [1:7.4~5ubuntu10 (jaunty, now)] xserver-xorg-core [2:1.5.99.3-0ubuntu4 (jaunty, now)] Problem is: xserver-xorg-core conflicts with xserver-xorg-video-4 [provided by nvidia-glx-96 96.43.09-0ubuntu2] ** Affects: nvidia-graphics-drivers-96 (Ubuntu) Importance: Undecided Status: New -- xserver-xorg-core conflicts with xserver-xorg-video-4 [provided by nvidia-glx-96 96.43.09-0ubuntu2] https://bugs.launchpad.net/bugs/315371 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218340] Re: Big fonts after upgrade
After update WINE to the version 1.1.12~winehq0~ubuntu~8.10-0ubuntu1 and deleting folder ~/.wine problem with fonts fixed! Right now all applications under wine looking fine! ** Changed in: wine (Ubuntu) Status: Incomplete = Fix Released -- Big fonts after upgrade https://bugs.launchpad.net/bugs/218340 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315576] [NEW] screen resolution incorrect after switching off/on flat panel notebook
Public bug reported: Binary package hint: xserver-xorg-driver-nv A have notebook with Nvidia Geforce MX440 GO 64 graphics card. Installed Ubuntu and Windows XP. In windows xp with drivers 40 series for this card i have no problem. A have a button to switch off/on flat panel (display) - FN+F11. When I press this button flat pannel is swtching off. Pressing again and it switch on. But.. When it switch on i see incorrect resolution on the screen - see screenshot (attachment). To fix resolution i must go to the TTY-console (Ctrl+Alt+F1) and go back to X. Then correct resolution is restored. As I sayd in Windows XP i haven't this problem. I can't confirm this problem with binary Nvidia driver (propr.) in Ubuntu, because another issue denied installation of the nvidia-glx-96 package. I'll try to test as soon as possible P.S. Sorry for my English. ** Affects: xserver-xorg-video-nv (Ubuntu) Importance: Undecided Status: New -- screen resolution incorrect after switching off/on flat panel notebook https://bugs.launchpad.net/bugs/315576 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315576] Re: screen resolution incorrect after switching off/on flat panel notebook
** Attachment added: Photo of incorrect resolution after switch off/on flat panel http://launchpadlibrarian.net/21060982/DSCN2009.JPG ** Changed in: xserver-xorg-video-nv (Ubuntu) Sourcepackagename: xserver-xorg-driver-nv = xserver-xorg-video-nv -- screen resolution incorrect after switching off/on flat panel notebook https://bugs.launchpad.net/bugs/315576 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315576] Re: screen resolution incorrect after switching off/on flat panel notebook
** Description changed: Binary package hint: xserver-xorg-driver-nv A have notebook with Nvidia Geforce MX440 GO 64 graphics card. Installed Ubuntu and Windows XP. In windows xp with drivers 40 series for this card i have no problem. A have a button to switch off/on flat panel (display) - FN+F11. When I press this button flat pannel is swtching off. Pressing again and it switch on. But.. When it switch on i see incorrect resolution on the screen - see screenshot (attachment). To fix resolution i must go to the TTY-console (Ctrl+Alt+F1) and go back to X. Then correct resolution is restored. As I sayd in Windows XP i haven't this problem. I can't confirm this problem with binary Nvidia driver (propr.) in Ubuntu, because another issue denied installation of the nvidia-glx-96 package. I'll try to test as soon as possible + The same bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- + video-nv/+bug/110648 + P.S. Sorry for my English. ** Description changed: Binary package hint: xserver-xorg-driver-nv + xserver-xorg-video-nv 1:2.1.10-1ubuntu4 A have notebook with Nvidia Geforce MX440 GO 64 graphics card. Installed Ubuntu and Windows XP. In windows xp with drivers 40 series for this card i have no problem. A have a button to switch off/on flat panel (display) - FN+F11. When I press this button flat pannel is swtching off. Pressing again and it switch on. But.. When it switch on i see incorrect resolution on the screen - see screenshot (attachment). To fix resolution i must go to the TTY-console (Ctrl+Alt+F1) and go back to X. Then correct resolution is restored. As I sayd in Windows XP i haven't this problem. I can't confirm this problem with binary Nvidia driver (propr.) in Ubuntu, because another issue denied installation of the nvidia-glx-96 package. I'll try to test as soon as possible The same bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-nv/+bug/110648 P.S. Sorry for my English. -- screen resolution incorrect after switching off/on flat panel notebook https://bugs.launchpad.net/bugs/315576 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218340] Re: Big fonts after upgrade
I have the same problem in Ubuntu 9.04 with wine 1.1.9 ** Attachment added: Font problems in wine 1.1.9 http://launchpadlibrarian.net/20003158/wineproblem.jpg -- Big fonts after upgrade https://bugs.launchpad.net/bugs/218340 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20773] Re: [breezy] usb mouse displays error on console during boot
Addon to my prevous post: Mouse is working in ports 1 and 3 only if i connect other usb-device at usb-ports 2 or 4 Why that? -- [breezy] usb mouse displays error on console during boot https://bugs.launchpad.net/bugs/20773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78540] Re: Alt-Shift does not propagate to remote host
Ubuntu Intrepid rdesktop 1.6.0 Problem exits ** Changed in: rdesktop (Ubuntu) Status: Fix Released = Confirmed -- Alt-Shift does not propagate to remote host https://bugs.launchpad.net/bugs/78540 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78540] Re: Alt-Shift does not propagate to remote host
Temp. fix to switch using Alt+Shift is to use RIGHT alt button (Alt Gr) + left shift button -- Alt-Shift does not propagate to remote host https://bugs.launchpad.net/bugs/78540 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20773] Re: [breezy] usb mouse displays error on console during boot
After update... mouse is working an any USB-port! Great! Kernel is the same 2.6.27-2-generic #1 SMP, but was updated glibc, cpp, libstdc+ and many other... maybe this helps me? Right now i don't have problem, that i wrote upper... -- [breezy] usb mouse displays error on console during boot https://bugs.launchpad.net/bugs/20773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20773] Re: [breezy] usb mouse displays error on console during boot
I can Confirm. my kernel: 2.6.27-2-generic #1 SMP Mouse: USB A4Tech SWOP-80 Notebook Mitac 8640 After upgrading to 2.6.27 kernel my USB mouse not working in two of 4 USB-ports. For example.. connecting USB mouse to usb-port #1: # lsusb Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub No mouse! Connecting mouse to usb-port #2: # lsusb Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 022: ID 09da:000a A4 Tech Co., Ltd Port Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Mouse found and working! But usb-port #3 is the same as port #1 (mouse not working) and usb-port #4 is the same as #4 (mouse working) And if I bootup with mouse connected to ports #1 or #3 i see some USB errors and mouse not working.. -- [breezy] usb mouse displays error on console during boot https://bugs.launchpad.net/bugs/20773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246352] Re: package xserver-xorg-core 2:1.4.99.905-0ubuntu2 failed to install/upgrade
xserver-xorg 7.4 resolve this problem ** Changed in: xorg-server (Ubuntu) Status: New = Fix Released -- package xserver-xorg-core 2:1.4.99.905-0ubuntu2 failed to install/upgrade https://bugs.launchpad.net/bugs/246352 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246352] [NEW] package xserver-xorg-core 2:1.4.99.905-0ubuntu2 failed to install/upgrade
Public bug reported: Binary package hint: xserver-xorg-core Source: xorg-server (2:1.4.99.905-0ubuntu2) release of Ubuntu: Ubuntu intrepid Can't update to xserver-xorg-core 2:1.4.99.905-0ubuntu2 because of dependency from the xserver-xorg. xserver-xorg-core 2:1.4.99.905-0ubuntu2 needed xserver-xorg (1:7.3+12ubuntu2) and conflicts with xserver-xorg-input-2 and xserver- xorg-video-2 but xserver-xorg (1:7.3+12ubuntu2) is requiring xserver-xorg-input-2 and xserver-xorg-video-2! ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- package xserver-xorg-core 2:1.4.99.905-0ubuntu2 failed to install/upgrade https://bugs.launchpad.net/bugs/246352 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246398] Re: Ibex Alpha 1 BUG: Following pkgs. have unmet dependen xserver-xorg-core: Depends: xserver-xorgcies
*** This bug is a duplicate of bug 246352 *** https://bugs.launchpad.net/bugs/246352 ** This bug has been marked a duplicate of bug 246352 package xserver-xorg-core 2:1.4.99.905-0ubuntu2 failed to install/upgrade -- Ibex Alpha 1 BUG: Following pkgs. have unmet dependen xserver-xorg-core: Depends: xserver-xorgcies https://bugs.launchpad.net/bugs/246398 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
