[Bug 1303461] Re: gsettings is ignoring my override files
This can be closed, as mc4man mentioned that I need to preface/cast my integers with "uint32" in order for gsettings to "accept" my values and work correctly. Referring to the above: idle-delay=15 needs to be idle-delay=uint32 15 (Note to self: see my forum post http://ubuntuforums.org/showthread.php?t=2215394&p=12983799) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303461 Title: gsettings is ignoring my override files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1303461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303461] [NEW] gsettings is ignoring my override files
Public bug reported:
Ubuntu Trusty Tahr (development branch) 14.04 (with the latest updates
as of this morning)
gsettings is ignoring my override files
(So is SystemSettings-->Brightness&Lock tab)
I've followed various instructions on the Internet on how to create override
files
or site-wide key files to override dconf defaults.
I created these 3 files:
/etc/dconf/profile/user
user-db:user
system-db:sitewide
/etc/dconf/db/sitewide.d/00-site-wide-defaults
[org/gnome/desktop/session]
idle-delay=15
/etc/dconf/db/sitewide.d/locks/gmooreLockPolicy
/org/gnome/desktop/session/idle-delay
`gsettings get` is incorrectly reporting the default setting of 5 minutes:
$ gsettings get org.gnome.desktop.session idle-delay
uint32 300
( SystemSettings-->Brightness&Lock tab also displays 5 minutes.)
The `dconf-editor` correctly reports 15 seconds.
(Also, if I remove the lock from file,
/etc/dconf/db/sitewide.d/locks/gmooreLockPolicy
and run `sudo dconf update`, `gsettings` is still
incorrectly reporting 300 seconds.)
I also have left my terminal idle, and watched it, around the 5 minute mark
to go to the password lock screen. Meaning, it is taking longer than
the 15 seconds that it should be locking at.
I have run:
`strace gsettings get org.gnome.desktop.session idle-delay`.
After trimming a lot of output, I do see these pertinent files being opened:
open("/usr/share/glib-2.0/schemas/gschemas.compiled", O_RDONLY) = 3
open("/etc/dconf/profile/user", O_RDONLY) = 4
open("/run/user/1000/dconf/user", O_RDWR|O_CREAT, 0600) = 4
open("/home/bee000guest/.config/dconf/user", O_RDONLY) = 4
open("/etc/dconf/db/sitewide", O_RDONLY) = 4
So it is opening all the correct files. It's just ignoring what it finds in
/etc/dconf/db/sitewide.
Is the syntax I'm using in /etc/dconf/db/sitewide.d/00-site-wide-defaults
OK for `dconf-editor`, but somehow not correct for `gsettings`?
** Affects: gsettings-desktop-schemas (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/1303461
Title:
gsettings is ignoring my override files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1303461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298093] Re: iscsi_trgt: module verification failed
Just for fun, I un-installed all the iSCSI software: `sudo apt-get purge iscsitarget iscsitarget-dkms open-iscsi` Rebooted. Machine takes about 15 seconds to go from my entering my encryption key/passphrase, until I see the login dialog on the Lubuntu GUI screen. So, my 120+ second boot with iSCSI software, is iSCSI-related. I have uploaded the correcponding .PNG file from "bootchart" package for this 15 second boot. ** Attachment added: "bootchart corresponding to 15 second boot (no iSCSI s/w installed)" https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+attachment/4047408/+files/bee005-trusty-20140327-3.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298093 Title: iscsi_trgt: module verification failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298093] Re: iscsi_trgt: module verification failed
I installed "bootchart", which pulls in pybootchartgui and python-support, rebooted, and am uploading the .png file found in /var/log/bootchart. (let me know if you want the .tgz file) Interesting picture of the boot processes. Looks like there is long 120 second idle time, for something, but I'm new to reading this bootchart image. ** Attachment added: "Picture of all the boot processes" https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+attachment/4045795/+files/bee005-trusty-20140326-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298093 Title: iscsi_trgt: module verification failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298093] [NEW] iscsi_trgt: module verification failed
Public bug reported: I am on 64-bit Lubuntu Trusty Tahr (development branch) (64-bit Lubuntu nighlty build of 2014-03-14 with updates) (this machine is set up with RAID-1, LVM, Encryption, iSCSI Target and iSCSI client, in case that matters.) Versions of iSCSI: ii iscsitarget 1.4.20.3+svn499-0ubuntu1 ii iscsitarget-dkms 1.4.20.3+svn499-0ubuntu1 I have successfully set up an iSCSI target (and client). But if I peek inside the /var/log/syslog, I see this snippet: Mar 26 17:56:29 bee005 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="710" x-info="http://www.rsyslog.com";] start ... Mar 26 17:57:03 bee005 ntpd_intres[1148]: parent died before we finished, exiting [89 second gap] Mar 26 17:58:32 bee005 kernel: [ 191.597648] iscsi_trgt: module verification failed: signature and/or required key missing - tainting kernel Mar 26 17:58:32 bee005 kernel: [ 191.598233] iSCSI Enterprise Target Software - version trunk Mar 26 17:58:32 bee005 kernel: [ 191.598297] iscsi_trgt: Registered io type fileio Mar 26 17:58:32 bee005 kernel: [ 191.598299] iscsi_trgt: Registered io type blockio Mar 26 17:58:32 bee005 kernel: [ 191.598301] iscsi_trgt: Registered io type nullio ... The machine is taking a noticeable a mount of time to boot up. (2+ minutes). This snippet in syslog, makes me want to say that the iscsi_targt module in the kernel has delayed the booting up of the machine by 90-120 seconds due to the 89 second gap in the syslog file, and that it's been 2 minutes 3 seconds since beginning of the syslog. Did some signature/key not get packaged in the latest and greatest packages of iscsitarget and iscsitarget-dkms? (and the kernel waits (or retires) for 120 seconds before continuing on?) ** Affects: iscsitarget (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/1298093 Title: iscsi_trgt: module verification failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1291641] Re: iscsitarget-dkms 1.4.20.3+svn496-1ubuntu1: iscsitarget kernel module failed to build
I had logged bug 1293108, a duplicate of this bug, but I will log my comment here as well. Short Story: The bug fix mentioned in comment #5 solved my compile error during the installing of iscsitarget-dkms and iscsitarget. Longer Story: Today, 2014-03-26, I updated my 64-bit Lubuntu Trusty Tahr with all packages, specifically, iscsitarget-dkms, and iscsitarget version 1.4.20.3+svn499-0ubuntu1. I then re-installed them via: sudo apt-get install --reinstall iscsitarget-dkms sudo apt-get install --reinstall iscsitarget I was then able to proceed with setting up an iSCSI target on machine #1, and set up an iSCSI client on machine #2 (and machine #1). I was then able to backup files from machine #2, the iSCSI client, to machine #1, the iSCSI target, via the iSCSI protocol. I also was able to view and access this iSCSI target on machine #1 from machine #1. (yes the same machine) Note to self: Since machine #1, now has a firewall (UFW) set up, I had to allow tcp port 3260 so that machine #2 could make a connection. Note to self: Machine #1 takes an extra 90 seconds or so to boot up. Not sure who's causing this: RAID, LVM, Encryption, or the new iSCSI target and iSCSI client that I just got configured. I do see this 90 second gap in /var/log/syslog: ... Mar 26 17:24:05 bee005 ntpd_intres[1217]: parent died before we finished, exiting [89 second gap] Mar 26 17:25:34 bee005 kernel: [ 142.820882] iscsi_trgt: module verification failed: signature and/or required key missing - tainting kernel Mar 26 17:25:34 bee005 kernel: [ 142.827819] iSCSI Enterprise Target Software - version trunk Mar 26 17:25:34 bee005 kernel: [ 142.827883] iscsi_trgt: Registered io type fileio ... Thank you for fixing the compile problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291641 Title: iscsitarget-dkms 1.4.20.3+svn496-1ubuntu1: iscsitarget kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1291641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279987] Re: usb-creator-gtk crashed with TypeError in __call__(): first argument must be the method signature string: GLib.Variant('a{sv}', {})
Same results for me.
One 8 GB Cruzer Micro USB causes this problem.
(I had GParted reformat this to FAT32, then to ext4. Same error.)
I have this othe 16 GB Sandisk Cruzer USB, and I don't have a problem
using Startup Disk Creator on it.
If the 8 GB USB is plugged in, Startup Disk Creator crashes immediately upon
starting up.
Or if the 8 GB is not plugged, I can start up Startup Disk Creator, but as soon
as I insert the
8 GB USB into the port, Startup Disk Creator crashes immediately.
`lsusb --verbose` shows this for the two USB sticks.
Bus 002 Device 004: ID 0781:5406 SanDisk Corp. Cruzer Micro U3
Couldn't open device, some information will be missing
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize064
idVendor 0x0781 SanDisk Corp.
idProduct 0x5406 Cruzer Micro U3
bcdDevice2.00
iManufacturer 1
iProduct2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes2
Transfer TypeBulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes2
Transfer TypeBulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Bus 002 Device 005: ID 0781:5530 SanDisk Corp. Cruzer
Couldn't open device, some information will be missing
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize064
idVendor 0x0781 SanDisk Corp.
idProduct 0x5530 Cruzer
bcdDevice1.03
iManufacturer 1
iProduct2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes2
Transfer TypeBulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes2
Transfer TypeBulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279987
Title:
usb-creator-gtk crashed with TypeError in __call__(): first argument
must be the method signature string: GLib.Variant('a{sv}', {})
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1279987/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
[Bug 1293108] [NEW] Setting up iscsitarget-dkms fails with error: ‘struct ipv6_pinfo’ has no member named ‘daddr’
Public bug reported:
I am on 64-bit Lubuntu Trusty Tahr (development branch)
(64-bit Lubuntu nighlty build of 2014-03-14 with updates)
(this machine is set up with RAID-1, LVM and Encryption, in
case that matters.)
and am trying to set up an iSCSI target (and client).
2 years ago, I successfully did this on PrecisePangolin following these
instructions:
http://www.howtoforge.com/using-iscsi-on-ubuntu-10.04-initiator-and-target
Today, on TrustyTahr, I can't get past the installing of the
iscsitarget-dkms package.
I'm getting a simple(?) compile error.
iscsitarget-dkms package is at version 1.4.20.3+svn496-1ubuntu1
(is there an alternative iSCSI target package that Ubuntu uses/blesses?)
-- begin of package installation
--
$ sudo apt-get install --reinstall iscsitarget-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 25 not upgraded.
1 not fully installed or removed.
Need to get 0 B/79.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 117830 files and directories currently installed.)
Preparing to unpack .../iscsitarget-dkms_1.4.20.3+svn496-1ubuntu1_all.deb ...
--
Deleting module version: 1.4.20.3+svn496
completely from the DKMS tree.
--
Done.
Unpacking iscsitarget-dkms (1.4.20.3+svn496-1ubuntu1) over
(1.4.20.3+svn496-1ubuntu1) ...
Setting up iscsitarget (1.4.20.3+svn496-1ubuntu1) ...
* Starting iSCSI enterprise target service
modprobe: FATAL: Module iscsi_trgt not found. [fail]
invoke-rc.d: initscript iscsitarget, action "start" failed.
dpkg: error processing package iscsitarget (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up iscsitarget-dkms (1.4.20.3+svn496-1ubuntu1) ...
Creating symlink /var/lib/dkms/iscsitarget/1.4.20.3+svn496/source ->
/usr/src/iscsitarget-1.4.20.3+svn496
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area
make KERNELRELEASE=3.13.0-17-generic -C /lib/modules/3.13.0-17-generic/build
M=/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build..(bad exit status: 2)
Error! Bad return status for module build on kernel: 3.13.0-17-generic (x86_64)
Consult /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/make.log for more
information.
Errors were encountered while processing:
iscsitarget
E: Sub-process /usr/bin/dpkg returned an error code (1)
-- end of package installation
--
-- Contents of
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/make.log ---
$ cat /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/make.log
DKMS make.log for iscsitarget-1.4.20.3+svn496 for kernel 3.13.0-17-generic
(x86_64)
Sun Mar 16 08:55:39 EDT 2014
make: Entering directory `/usr/src/linux-headers-3.13.0-17-generic'
LD /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/built-in.o
LD /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/built-in.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/tio.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/iscsi.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/nthread.o
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/nthread.c: In function
‘do_recv’:
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/nthread.c:147:1:
warning: the frame size of 1096 bytes is larger than 1024 bytes
[-Wframe-larger-than=]
}
^
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/wthread.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/config.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/digest.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/conn.o
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/conn.c: In function
‘conn_info_show’:
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/conn.c:51:19: error:
‘struct ipv6_pinfo’ has no member named ‘daddr’
&inet6_sk(sk)->daddr);
^
make[2]: *** [/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/conn.o]
Error 1
make[1]: *** [/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel] Error 2
make: *** [_module_/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build] Error 2
make: Leaving directory `/usr/src/linux-headers-3.13.0-17-generic'
-- end of make.log --
begin of snippet of conn.c
void conn_info_show(struct seq_file *seq, struct iscsi_session *session)
{
struct iscsi_conn *conn;
struct sock *sk;
char buf[64];
[Bug 1278062] Re: firefox crashes on startup (but apparently layunched properly to enable me to post this)
Maybe you are hitting the same problem as me: https://bugzilla.mozilla.org/show_bug.cgi?id=981066 which is related to the environment variable XDG_CONFIG_DIRS ** Bug watch added: Mozilla Bugzilla #981066 https://bugzilla.mozilla.org/show_bug.cgi?id=981066 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278062 Title: firefox crashes on startup (but apparently layunched properly to enable me to post this) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1278062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003179] Re: compiz crashes after starting up vnc4server and then unity launcher is not displayed via vnc client
Just to get the 32-bit machine out of the question, I just tested and have the same problem if I vnc from one of the 64-bit machines to the other 64-bit machines. (no pop up message about compiz crashing and compiz still shows up as a process running) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003179 Title: compiz crashes after starting up vnc4server and then unity launcher is not displayed via vnc client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1003179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003179] [NEW] compiz crashes after starting up vnc4server and then unity launcher is not displayed via vnc client
Public bug reported: My VNC client (RemoteDesktopViewer) is on a netbook running 32-bit pae PrecisePangolin. I have 2 other machines using totally different hardware, running 64-bit PrecisePangolin and will be running `vnc4server` as the VNC Server. When I start up the vnc4server on either machine, I sometimes get a window that says: "compiz has crashed". When I vnc to either machine from the 32-bit netbook, I am missing the Unity launcher and the top menu bar. I only have the background image showing. (FYI: I am able to go in the reverse direction, with the vnc4server running on my 32-bit netbook. I can see the whole console window with top menu bar and the Unity launcher. I have noticed that there is no "compiz" binary nor "compiz-decorator" running on the 32-bit netbook prior to running vnc4server. Thus, I don't get the compiz crashing message, since it's not even running. I don't know why compiz is not running nor know really what compiz is or does. ) I don't know where the problem lies: compiz, unity, vnc4server or other but am willing to help narrowing this down with some guidance. ** Affects: compiz (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/1003179 Title: compiz crashes after starting up vnc4server and then unity launcher is not displayed via vnc client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1003179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003141] [NEW] cannot add an application/icon to the unity launcher via vnc4server
Public bug reported: (cutting and pasting from http://ubuntuforums.org/showthread.php?t=1981201) >From a 32-bit PrecicePangolin laptop running a vnc client >(RemoteDesktopViewer), I am connecting to a vnc4server running on a 64-bit PrecisePangolin machine. (virtual machine running under Xen 4.1). When I connect via VNC, I can see the Unity launcher and top menu bar. But if I try to drag an application from the Dash/Search application to the Unity launcher, it doesn't stick. I can't add an App to the Unity Launcher. But I am able to right click an icon in the Unity Launcher and choose "Unlock from Launcher" successfully. So I am able to delete Apps from the Unity Launcher. (the deletion is persistent on the actual Console after logging out then back in again.) FYI: I have the same results when going from a 64-bit LucidLynx RemoteDesktopViewer client, to the 32-bit vnc4server PrecisePangolin laptop. FYI: I am able to connect to a 64-bit vnc4server LucidLynx machine and add an application to the quick launch section on the top menu bar which is also noticable on the real Console of that machine (after logging in and then out). I thing that is a comparable test that shows the console should be alterable via VNC. Summary: Can anyone change the Unity Launcher on PrecisePangolin via any VNC Server product (preferably vnc4server). ** Affects: unity (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/1003141 Title: cannot add an application/icon to the unity launcher via vnc4server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1003141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997297] Re: tmpbridge is the name of the bridge and networking not working
so the solution for me to get all this automajic bridging to work is to add this line to /etc/network/interfaces: iface eth0 inet dhcp Such that my /etc/network/interfaces look like: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Then reboot. That line seems to stop NetworkManager from managing that eth0 interface. Which then seems to allow the /etc/xen/scripts/network-bridge script to be successful. Such that after the reboot, this is the output of `sudo ifconfig -a`: eth0 Link encap:Ethernet HWaddr 00:22:19:2c:b9:db inet addr:192.168.0.108 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::222:19ff:fe2c:b9db/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18370 errors:0 dropped:0 overruns:0 frame:0 TX packets:16217 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22075797 (22.0 MB) TX bytes:2582972 (2.5 MB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:100 errors:0 dropped:0 overruns:0 frame:0 TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7600 (7.6 KB) TX bytes:7600 (7.6 KB) peth0 Link encap:Ethernet HWaddr 00:22:19:2c:b9:db inet6 addr: fe80::222:19ff:fe2c:b9db/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:20195 errors:0 dropped:0 overruns:0 frame:0 TX packets:16226 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22774536 (22.7 MB) TX bytes:2653740 (2.6 MB) Interrupt:21 Memory:fe6e-fe70 I now have a "peth0" interface. And the output of `sudo brctl show` now shows: bridge name bridge id STP enabled interfaces eth0 8000.0022192cb9db no peth0 Rather than showing the broken "tmpbridge" bridge. and once I bring up a virtual machine with: `sudo xl create /etc/xen/xen002.cfg` I see that I have another interface successfully getting created on the dom0 machine: vif1.0Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff inet6 addr: fe80::fcff::feff:/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:99 errors:0 dropped:0 overruns:0 frame:0 TX packets:470 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:10898 (10.8 KB) TX bytes:88627 (88.6 KB) NetworkManager still periodically (every 60 seconds) pops up a message of: "Wired network. Disconnected" so maybe I need to stop the NetworkManager service all together to stop its pesky meddling with these newly created interfaces or at least have it stop the irritating, and, I think, non-fatal messages. I also now have ssh connectivity between my dom0 and domU and vice-versa. (although, I have to use IP addresses and not the hostnames. Evidently, the DNS server does not know about these hosts?) So I think this "bug" can be closed, although it would be nice if the scripts took into account Network Manager meddling and either provided a solution inside the network-bridge script to disable NetworkManager temporarily or spit out a message to the user about what they need to do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997297 Title: tmpbridge is the name of the bridge and networking not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-common/+bug/997297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997297] Re: tmpbridge is the name of the bridge and networking not working
i'm getting stuff to work. Will post within a day with more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997297 Title: tmpbridge is the name of the bridge and networking not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-common/+bug/997297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997297] [NEW] tmpbridge is the name of the bridge and networking not working
Public bug reported: I was under the impression that the name of the default bridge would be "eth0" (or "peth0" or "xenbr0"), instead I see "tmpbridge" as having been created. In either case, I can't ssh to Dom0 from DomU, nor the reverse. Nor can I ping any machine on the Internet from DomU. I think xen-tools is not working correctly on Ubuntu PrecisePangolin 12.04 with xen-tools 4.2.1-1. I also see my Network Manager icon constantly reporting that something has been disconnected every 30 seconds or so. Output from `sudo ifconfig -a` on Dom0: eth0 Link encap:Ethernet HWaddr 00:22:19:2c:b9:db inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::222:19ff:fe2c:b9db/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:136340 errors:0 dropped:0 overruns:0 frame:0 TX packets:93781 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:176393891 (176.3 MB) TX bytes:14595539 (14.5 MB) Interrupt:21 Memory:fe6e-fe70 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4115 errors:0 dropped:0 overruns:0 frame:0 TX packets:4115 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:470107 (470.1 KB) TX bytes:470107 (470.1 KB) tmpbridge Link encap:Ethernet HWaddr 92:45:75:85:57:a7 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Contents of one of my VM's config file: /etc/xen/xen002.cfg: kernel = '/boot/vmlinuz-3.2.0-24-generic' ramdisk = '/boot/initrd.img-3.2.0-24-generic' vcpus = '1' memory = '1024' root= '/dev/xvda2 ro' disk= [ 'phy:/dev/vg1/xen002-disk,xvda2,w', 'phy:/dev/vg1/xen002-swap,xvda1,w', ] name= 'xen002' vif = [ 'ip=192.168.0.201,mac=00:16:3E:25:6F:08' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash= 'restart' Contents of xend-config.sxp with commented and blank lines removed: $ cat xend-config.sxp | grep -v "^#" | sed -e '/^$/d' (network-script network-bridge) (vif-script vif-bridge) (dom0-min-mem 196) (enable-dom0-ballooning yes) (total_available_memory 0) (dom0-cpus 0) (vncpasswd '') I also will add that I don't think the syntax of naming a bridge works either. Meaning, If I change the network-script line to (network-script 'network-bridge bridge=br3') I don't see anything get created named "br3". I have zero experience with Xen so there may be a lot of user error here but I am willing and able to provide more tests and information. ** Affects: xen-tools (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/997297 Title: tmpbridge is the name of the bridge and networking not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-tools/+bug/997297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996789] Re: 70-install-ssh does not prevent sshd from starting up
Yes, I believe 997063 should address my issue with sshd starting up (which is the beginning of the end for me) during the installation of openssh-server package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996789 Title: 70-install-ssh does not prevent sshd from starting up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-tools/+bug/996789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996789] Re: 70-install-ssh does not prevent sshd from starting up
Oh, and I forgot to mention. After the failed installation, `sshd` is running: $ ps -alef | grep sshd 4 S root 1302 1 0 80 0 - 12487 poll_s 08:03 ?00:00:00 /usr/sbin/sshd -D $ and I cannot stop it via `service` command from Dom0 (cause it was started from a different machine/root): $ sudo service ssh stop stop: Unknown instance: $ But I certainly can kill it (which is untrue if this sshd was started from Dom0 as another sshd would get started when something detected it died.) $ sudo kill -9 1302 $ ps -alef | grep sshd $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996789 Title: 70-install-ssh does not prevent sshd from starting up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-tools/+bug/996789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996789] Re: 70-install-ssh does not prevent sshd from starting up
Looking at the code of xen-create-image, --keep would only matter if somewhere along the lines FAIL was set to 1and that "exit" was not called at the point of the error. The failure occurs during a `umount` of a busy device. (it's still busy cause `sshd` is running.) The perl program just exits at that point which at this point is inside the routine, runCommand() at the last 2 lines: $FAIL = 1; exit 127; If --keep were to work, I would have had to see this line get printed: Removing failed install: The installation is not programmatically being removed via the command, xen-delete-image. The installation is being removed cause of this line in the beginning: use File::Temp qw/ tempdir /; Meaning, once the perl program exits, and before control is given back to the user, Perl automajically removes any file systems that was created with the intention of them being temporary. "tempdir" represents the entire installation and it is this directory that is being "correctly" cleaned up behind the scenes without any notice to the end user. "Correctly" meaning, Perl is only doing what it is supposed to do. Anyways, I just did this per your request: Ran UpdateManager to get any updates. (none) rebooted machine. Shut down the `sshd` on Dom0 Unedit by hack in /usr/lib/xen-tools/karmic.d/70-install-ssh. sudo xen-create-image --fs=ext4 --image=full --memory=1Gb --size=20Gb --swap=2Gb --install-method=debootstrap --arch=amd64 --dist=precise --lvm=vg1 --hostname=xen004 --vcpus=1 --ip=192.168.0.245 --gateway=192.168.0.1 --broadcast=192.168.0.255 --netmask=255.255.255.0 --keep --verbose and that resulted in an empty installation under my mounted volume at /tmp/P_4Wff0FTJ. This was the final n lines from the xen-create-image: ... Setting up root password Generating a password for the new guest. All done Executing : umount /tmp/P_4Wff0FTJ/proc Finished : umount /tmp/P_4Wff0FTJ/proc 2>&1 Unmounting : /tmp/P_4Wff0FTJ/dev/pts Executing : umount /tmp/P_4Wff0FTJ/dev/pts Finished : umount /tmp/P_4Wff0FTJ/dev/pts 2>&1 Unmounting : /tmp/P_4Wff0FTJ Executing : umount /tmp/P_4Wff0FTJ umount: /tmp/P_4Wff0FTJ: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) Finished : umount /tmp/P_4Wff0FTJ 2>&1 Running command 'umount /tmp/P_4Wff0FTJ 2>&1' failed with exit code 256. Aborting See /var/log/xen-tools/xen004.log for details cannot remove directory for /tmp/P_4Wff0FTJ: Device or resource busy at /usr/share/perl/5.14/File/Temp.pm line 902 $ and then I surmise between the message of "cannot remove directory" and the Unix prompt, Perl is effectively doing this: `rm -rf /tmp/P_4Wff0FTJ`. Actually I discovered this, cause during my 100s of installations fighting with this problem, I had commented out one of the umount commands for .../proc. So when xen-create-image failed and got the regular messages as in the above, I also got all these messages about how it couldn't "unlink" a bunch of files under /tmp/XX/proc/... I said to myself, huh? where is that code that is doing all this removing. I then stumbled upon that line: use File::Temp qw/ tempdir /; and looked up what that Perl Class does. And the intent is to clean up after the programmer all files and directories once the program exits. (Having said that, not sure why "root" couldn't unlink those directories. But that isn't important.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996789 Title: 70-install-ssh does not prevent sshd from starting up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-tools/+bug/996789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996789] [NEW] 70-install-ssh does not prevent sshd from starting up
Public bug reported:
On 64-bit Ubuntu 12.04 PrecisePangolin, the
/usr/lib/xen-tools/karmic.d/70-install-ssh file
from the 4.2.1-1 xen-tools package does not prevent the
`sshd` from starting up when the openssh-server package
gets installed.
I don't know why it doesn't, I just see it running.
[ Aside: if the dom0 machine happens to have
sshd running, then no additional `sshd` process will start
to run during the installation of the openssh-server package
on the domU machine. Then the entire run of xen-create-image
will be successful.
]
[Aside: I did have to do the following to begin to use
xen-create-image.
cd /usr/share/doc/xen-tools
sudo ln -s karmic.d precise.d
sudo vi /etc/default/xen
Change:
TOOLSTACK=
to:
TOOLSTACK=xl
]
The short story on how to fix my dilemna was to edit:
/usr/lib/xen-tools/karmic.d/70-install-ssh
And to add code to shut down the sshd process that was just started
after installing the openssh-server package:
chroot ${prefix} /usr/sbin/service ssh stop
Longer story:
The xen-create-image perl script has the intention of preventing the sshd
process from starting up, but it's not working. I don't really know why.
Because this sshd binary starts up upon the installation of the
openssh-server package and loads up other libraries, the
clean up "END" subroutine in xen-create-image fails while unmounting
the /tmp/ directory.
That failed unmounting is not fatal.
The new machine is still intact at that moment.
But when the perl script, xen-create-image, exits, any temporary
directory location as created by the File::Temp Perl class gets
removed automajically.
The /tmp/ directory was created via this File::Temp Perl class
and will get removed. Unfortunately it's not the empty directory
as it should be after successful unmounting, it's the entire new machine
file heararchy since the unmounting failed.
Thus after xen-create-image, when one tries to list out the contents
of the root of the new machine, for me it would be at the top of my
volume, I see no directories, no files. Nothing.
** Affects: xen-tools (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/996789
Title:
70-install-ssh does not prevent sshd from starting up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xen-tools/+bug/996789/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973473] Re: Login Manager only shown in upper half of screen, unless restart lightdm
1.) I also only see half of the Display during the installation of the Precise 32-bit Desktop release. (yes it was painful to operate the mouse/keyboard missing half of the GUI, and what I was seeing was not actually there unless I used the mouse to repaint under its hover area, and then by finding the dialog window's top border and moving the window around to repaint itself.) After the installation and reboot, the same 1/2 GUI problem exists. >From the tty1 console screen, as mentioned above, I ran the `sudo stop lightdm` and sudo start lightdm` to rectify the situation. 2.) I then ran UpdateManager and got the latest 53 updates since GA, rebooted machine, and the problem persists. 3.) `lspci` lists: VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) (rev 07) 4.) I'm on a Dell Inspiron Mini 10 netbook. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973473 Title: Login Manager only shown in upper half of screen, unless restart lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-psb/+bug/973473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912031] Re: ubiquity crashed with TypeError in partman_column_name(): argument of type 'NoneType' is not iterable
Here is my hard drive information, in case that matters: $ sudo fdisk -l Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0080 Device Boot Start End Blocks Id System /dev/sda1 63 192779 96358+ de Dell Utility /dev/sda2 * 192780 4289354 2048287+ 83 Linux /dev/sda3 4289355 625137344 3104239955 Extended /dev/sda5 42894188621055940960571 83 Linux /dev/sda6 602341173 62513734411398086 82 Linux swap / Solaris /dev/sda786212608 1886126075120 83 Linux /dev/sda8 188614656 2910146555120 83 Linux Partition table entries are not in disk order -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912031 Title: ubiquity crashed with TypeError in partman_column_name(): argument of type 'NoneType' is not iterable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/912031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912031] Re: ubiquity crashed with TypeError in partman_column_name(): argument of type 'NoneType' is not iterable
I also confirm this bug with 2012-02-27 build of 64-bit PrecisePangolin Desktop LiveCD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912031 Title: ubiquity crashed with TypeError in partman_column_name(): argument of type 'NoneType' is not iterable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/912031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701351] Re: grub-install fails to install on a raid1 array
I believe I have this exact problem using LucidLynx Alternate CD 10.04.4. I put my specifics here: http://ubuntuforums.org/showthread.php?p=11709060 I even edited /etc/mdadm/mdadm.conf as suggested in comment #55 of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/527401, but that didn't change anything. I am still unable to run in an Alternate CD rescue mode shell: grub-install --no-floppy --force --modules="raid mdraid" /dev/md0` I get 3 errors of: /usr/sbin/grub-probe: error: no mapping exists for `md0'. How does anyone set up RAID1 using LucidLynx. Has this been broken for 2 years? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/701351 Title: grub-install fails to install on a raid1 array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/701351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678420] Re: smbd sometimes does not start on startup
Happens intermittently on our Ubuntu 10.04.3 LTS 64-bit systems. I just checked 2 machines where smbd was not started after a reboot. I notice the same "smbd respawning too fast, stopped" in /var/log/syslog. This message is appearing up to12 seconds prior to Network Manager acquiring an IP address, etc. So to me it looks like samba is failing cause the network is not established yet. Should smbd go to sleep and try again in a few minutes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678420 Title: smbd sometimes does not start on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/678420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
similar to the stack trace in comment #6 above, winbind crashed today (on machine bee64) with this stack trace as gotten from gdb against the core file left behind: (gdb) bt #0 0x7f70d81fda75 in raise () from /lib/libc.so.6 #1 0x7f70d82015c0 in abort () from /lib/libc.so.6 #2 0x7f70da6a3460 in dump_core () at lib/fault.c:337 #3 0x7f70da6b428e in smb_panic (why=) at lib/util.c:1496 #4 0x7f70da6a385d in fault_report (sig=11) at lib/fault.c:52 #5 sig_fault (sig=11) at lib/fault.c:75 #6 #7 get_cache (domain=0x0) at winbindd/winbindd_cache.c:139 #8 0x7f70da616888 in resolve_username_to_alias (mem_ctx=, domain=0x0, name=0x7f70db4aacb0 "gautam.naik", alias=0x7fffab4a4110) at winbindd/winbindd_cache.c:1019 #9 0x7f70da609016 in normalize_name_map (mem_ctx=0x7f70db496180, domain=0x0, name=0x7f70db4aacb0 "gautam.naik", normalized=0x7fffab4a4110) at winbindd/winbindd_util.c:1442 #10 0x7f70da6076ef in fill_grent_mem_domusers (domain=0x7f70db4b0d40, state=, group_sid=0x7f70db46ced0, group_name_type=, num_gr_mem=, gr_mem=, gr_mem_len=0x7fffab4a44c8) at winbindd/winbindd_group.c:330 #11 fill_grent_mem (domain=0x7f70db4b0d40, state=, group_sid=0x7f70db46ced0, group_name_type=, num_gr_mem=, gr_mem=, gr_mem_len=0x7fffab4a44c8) at winbindd/winbindd_group.c:578 #12 0x7f70da607a9f in getgrsid_sid2gid_recv (private_data=0x7f70db46ceb0, success=, gid=563) at winbindd/winbindd_group.c:866 #13 0x7f70da600ba0 in process_loop (argc=, argv=, envp=) at winbindd/winbindd.c:1115 #14 main (argc=, argv=, envp=) at winbindd/winbindd.c:1440 I am running the latest winbind of 2:3.4.7~dfsg-1ubuntu3.6 So the problem still persists after upgrading to 2:3.4.7~dfsg- 1ubuntu3.6. What other information do you want me to provide? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736757] Re: [SRU] PANIC (pid 18442): internal error in winbindd
Everything still working fine on all 80 machines since 2011-04-27. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736757 Title: [SRU] PANIC (pid 18442): internal error in winbindd -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736757] Re: [SRU] PANIC (pid 18442): internal error in winbindd
I pushed out the patch to 24 more machines ( 29 total) on Monday 2011-04-25 6:30 PM. All is fine since then. Pushing out the patch to the rest of the 80 machines, right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736757 Title: [SRU] PANIC (pid 18442): internal error in winbindd -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736757] Re: [SRU] PANIC (pid 18442): internal error in winbindd
It's been 6 days, and the 5 machines that I have this patch on now, are doing fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736757 Title: [SRU] PANIC (pid 18442): internal error in winbindd -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736757] Re: [SRU] PANIC (pid 18442): internal error in winbindd
It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash, as I call it, on any of the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package. Will still be monitoring this, and may even install it on a few more machines, today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736757 Title: [SRU] PANIC (pid 18442): internal error in winbindd -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 753330] Re: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd).
*** This bug is a duplicate of bug 736757 *** https://bugs.launchpad.net/bugs/736757 It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash on any of the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package. Will still be monitoring this, and may even install it on a few more machines, today. Any date on when this proposed version will be generally available? 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/753330 Title: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd). -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash on any of the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package. This particular "rpc_pipe_np_smb_conn" crash, as I call it, is covered here https://bugs.launchpad.net/ubuntu/+source/samba/+bug/753330. So once this ~dfsg-1ubuntu3.6 package package is made generally available and I install it on my 80 machines, then I will go back to the original problem that I initiated here and try to get more information for you all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
Instead of downloading the .deb files, i did the more appropriate, SynapticPackageManager --> repositories --> Updates and Click "Pre-released updated (lucid-proposed)" check box which when installing winbind, it pulled in the proposed versions of libwbclient0, samba, samba-common, and smbclient. I did this on 2 machines (bee02 and bee75). Will wait for winbind to crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
1.) Per https://launchpad.net/ubuntu/lucid/+package/winbind there are several "proposed" versions to choose from: winbind 2:3.4.7~dfsg-1ubuntu3.5 in amd64 (Proposed) winbind 2:3.4.7~dfsg-1ubuntu3.6 in amd64 (Proposed) i will choose the newer "3.6" winbind 2:3.4.7~dfsg-1ubuntu3.6 in amd64 (Proposed) since the version that is currently installed is: 2:3.4.7~dfsg-1ubuntu3.5 2.) I will also purge the samba-dbg package in case that is conflicting. 3.) I will choose 2 machines to install the winbind 2:3.4.7~dfsg-1ubuntu3.6 in amd64 (Proposed) and then wait and see what happens... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 753330] Re: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd).
FYI: I have reported this exact same backtrace (at least the last 3 calls) here https://bugs.launchpad.net/ubuntu/+source/samba/+bug/667269?comments=all for us, winbind is dead, black screen on Console, no longer can ssh into machine using Active Directory credentials. I must kill any winbind processes running, then restart it. It's happening more frequently, (hourly) on 25% or more of our 80 64-bit LucidLinux machines, integrated with ActiveDirectory(winbind). I am desperate to get this bug fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753330 Title: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd). -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
Please, can someone raise the importance of this bug from Medium to whatever the highest level is. This winbind crashing problem is critical for us and is occurring with more frequency on more machines, daily if not hourly. It's affecting the confidence level of all our developers and QA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
I just did a backtrace on another machine(bee37), of another core file, the back trace takes a different path, but the final 3 calls are the same as my previous post and the same last e calls as Mau's back trace: rpc_pipe_np_smb_conn rpccli_set_timeout winbindd_lookup_sids ... Unfortunately these 3 back traces that have the same last 3 calls, are all different than my original backtrace I posted on 12/27/2010, but I'll take any winbind fix for any problem at this point. I had 22 of 80 machines experience a winbind problem yesterday, Monday 2011-04-18. I will throw one red herring of an idea out there. Is it possible that the cause of this is if a user is in a Windows group per his poilicy file but that group isn't active anymore? winbind can work for days at a time, so this problem is not deterministic. There's some other factor that is causing this to happen, and I can't figure it out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
I thought I would just add another backtrace from a core file that occurred today on a machine where winbind crashed several times: #0 0x7f089b9b6a75 in raise () from /lib/libc.so.6 #1 0x7f089b9ba5c0 in abort () from /lib/libc.so.6 #2 0x7f089de5c450 in dump_core () at lib/fault.c:337 #3 0x7f089de6d27e in smb_panic (why=) at lib/util.c:1496 #4 0x7f089de5c84d in fault_report (sig=11) at lib/fault.c:52 #5 sig_fault (sig=11) at lib/fault.c:75 #6 #7 rpc_pipe_np_smb_conn (p=0x0) at rpc_client/rpc_transport_np.c:402 #8 0x7f089df48048 in rpccli_set_timeout (rpc_cli=0x0, timeout=35000) at rpc_client/cli_pipe.c:2956 #9 0x7f089dde27a1 in winbindd_lookup_sids (mem_ctx=0x7f089e746290, domain=, num_sids=, sids=, domains=0x7fffa6901bd0, names=0x7fffa6901be0, types=0x7fffa6901bd8) at winbindd/winbindd_rpc.c:1221 #10 0x7f089dde5092 in lookup_groupmem (domain=0x7f089e7a4a00, mem_ctx=0x7f089e745eb0, group_sid=0x7f089e79ca60, num_names=0x7fffa6901f1c, sid_mem=, names=, name_types=0x7fffa6901ee8) at winbindd/winbindd_ads.c:1124 #11 0x7f089ddcc503 in lookup_groupmem (domain=, mem_ctx=, group_sid=, num_names=0x7fffa6901f1c, sid_mem=0x7fffa6901ed8, names=0x7fffa6901ee0, name_types=0x7fffa6901ee8) at winbindd/winbindd_cache.c:2211 #12 0x7f089ddbf5e7 in expand_groups (domain=0x7f089e7a4a00, state=, group_sid=, group_name_type=SID_NAME_DOM_GRP, num_gr_mem=, gr_mem=, gr_mem_len=0x7fffa69022a8) at winbindd/winbindd_group.c:468 #13 fill_grent_mem (domain=0x7f089e7a4a00, state=, group_sid=, group_name_type=SID_NAME_DOM_GRP, num_gr_mem=, gr_mem=, gr_mem_len=0x7fffa69022a8) at winbindd/winbindd_group.c:604 #14 0x7f089ddc0a9f in getgrsid_sid2gid_recv (private_data=0x7f089e767140, success=, gid=4549) at winbindd/winbindd_group.c:866 #15 0x7f089ddb9ba0 in process_loop (argc=, argv=, envp=) at winbindd/winbindd.c:1115 #16 main (argc=, argv=, envp=) at winbindd/winbindd.c:1440 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 502920] Re: [needs-packaging] Canon UFR II driver needs packaging
I had same problem: "PDL IMG Invalid Data" on the screen of our new Canon imageRunner Advance C5030 printers. The link I used was: http://support-my.canon-asia.com/P/search?category=Business+Multi-function+Devices&series=imageRUNNER+ADVANCE+series&model=iR-ADV+C5030&menu=download&filter=0 and at bottom of that page is a link to: http://support-my.canon-asia.com/contents/MY/EN/0100270807.html The download button at the very bottom. Followed above instructions in comment #5 above by Aurelien Jacobs.(thank you Aurelien!) All is well now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/502920 Title: [needs-packaging] Canon UFR II driver needs packaging -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
Can we get some traction on this bug? This problem still consistently occurs on at least 5 machines per week out of our 80 machines. Or throw me some ideas to either narrow down the problem further or work-arounds. I still feel that whatever winbind does to keep itself busy while being idle is causing it to go into this unresponsive state. Is it pinging our Active Directory server every X minutes and amassing a queue of awaiting responses back? Is it pinging DNS servers every X minutes, etc. It must be doing something, other than just merely authenticating a user when they log in. I think these background tasks is the core of the problem. I also can't believe no one is reporting this, unless we are the only establishment using ActiveDirectory on Ubuntu. Help, please. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
I didn't specifically reproduce the problem, but the problem has happened, on its own. There also happens to be a recent core file around. $ sudo find /var/log -type f | grep core | xargs sudo ls -al -rw--- 1 root root 1564672 2010-12-27 04:12 /var/log/samba/cores/winbindd/core I then run `gdb winbindd`, "core core", and then "bt" for a backtrace: Program terminated with signal 6, Aborted. #0 0x7f5862af1a75 in raise () from /lib/libc.so.6 (gdb) bt #0 0x7f5862af1a75 in raise () from /lib/libc.so.6 #1 0x7f5862af55c0 in abort () from /lib/libc.so.6 #2 0x7f5864f97430 in dump_core () at lib/fault.c:337 #3 0x7f5864fa825e in smb_panic (why=) at lib/util.c:1496 #4 0x7f5864f9782d in fault_report (sig=11) at lib/fault.c:52 #5 sig_fault (sig=11) at lib/fault.c:75 #6 #7 get_cache (domain=0x0) at winbindd/winbindd_cache.c:139 #8 0x7f5864f0a888 in resolve_username_to_alias (mem_ctx=, domain=0x0, name=0x7f5866dadf70 "puneet.arora", alias=0x7fff22b0bb00) at winbindd/winbindd_cache.c:1019 #9 0x7f5864efd016 in normalize_name_map (mem_ctx=0x7f5866d56530, domain=0x0, name=0x7f5866dadf70 "puneet.arora", normalized=0x7fff22b0bb00) at winbindd/winbindd_util.c:1442 #10 0x7f5864efb6ef in fill_grent_mem_domusers (domain=0x7f5866db2d60, state=, group_sid=0x7f5866d6eed0, group_name_type=, num_gr_mem=, gr_mem=, gr_mem_len=0x7fff22b0beb8) at winbindd/winbindd_group.c:330 #11 fill_grent_mem (domain=0x7f5866db2d60, state=, group_sid=0x7f5866d6eed0, group_name_type=, num_gr_mem=, gr_mem=, gr_mem_len=0x7fff22b0beb8) at winbindd/winbindd_group.c:578 #12 0x7f5864efba9f in getgrsid_sid2gid_recv (private_data=0x7f5866d6eeb0, success=, gid=563) at winbindd/winbindd_group.c:866 #13 0x7f5864ef4b98 in process_loop (argc=, argv=, envp=) at winbindd/winbindd.c:1109 #14 main (argc=, argv=, envp=) at winbindd/winbindd.c:1434 Is this helpful? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
I have just installed the samba-dbg package. When this problem happens again, what do I need to run, look at, provide back to this forum, etc? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667269] Re: winbind crashes
from my original post, I want to strike that there is a core file. Since then I have looked for a core file when the problem happens, and it is not there. So don't waste time debugging the attached core file. In regards to errr's note above, maybe why it is quick for him/her to fix, is that they are not using ActiveDirectory/LDAP and I am, and there is some time out period, and # of retries that "something" tries to do, hence why it takes about 2 1/2 minutes (5 tries of 30 second wait times each, maybe?) for me to get any command to complete. Restarting winbindd, does not always work (possibly never works). Well it may seem that it works, but there are still old winbindd processes still hanging around. Hence why my protocol is to `kill -9` the windbindd processes first. Then, restarting winbind via: `sudo /etc/init.d/winbind restart` Same as errr's comment above, that there is nothing in the log.winbindd file, except: [2010/11/03 16:25:25, 0] winbindd/winbindd.c:1252(main) winbindd version 3.4.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2010/11/03 16:25:25, 1] lib/tdb_validate.c:446(tdb_validate_and_backup) tdb '/var/cache/samba/winbindd_cache.tdb' is valid [2010/11/03 16:25:25, 1] lib/tdb_validate.c:456(tdb_validate_and_backup) Created backup '/var/cache/samba/winbindd_cache.tdb.bak' of tdb '/var/cache/samba/winbindd_cache.tdb' -- winbind crashes https://bugs.launchpad.net/bugs/667269 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 667269] Re: winbind crashes
** Attachment added: "Core file found under: /var/log/samba/cores/winbindd/core" https://bugs.launchpad.net/bugs/667269/+attachment/1713033/+files/core -- winbind crashes https://bugs.launchpad.net/bugs/667269 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 667269] [NEW] winbind crashes
Public bug reported: Binary package hint: samba Occasionally on various Ubuntu 64-bit LucidLynx systems (10.04.1), winbind goes into a state such that logging in fails. (we use ActiveDirectory for logging in. We do not use the Likewise-open product.) Although, it appears that there are 1 or more winbindd processes running, they are all dead/not_working/hung, etc. The only recourse to fix the problem, is that I log in with a local account that has sudo privilege, find and kill all the winbindd processes, and restart, nmbd, winbindd and samba. (not sure if I need to restart nmbd and samba, but I do it anyways.) This problem seems to happen more often on systems that are shared with other users. Some of those other users are connected from across the Wan via ssh. The problem seems to occur more often over the weekend. Meaning, Monday morning, is when we discover the machines are un-loginable with Active Directory account names. This problem does not happen with all 80+ machines. All machines are built out the same, and are on approximately the same type of hardware. This problem has existed since the onset of LucidLynx from what I can remember. The problem occurs frequently enough, that I had to set up a self-help web page for users with the problem. From there I have a script that will log into the machine in question, with a local sudo privileged account, kills all the winbind processes and restarts nmbd, winbindd and samba. Even with using the local account, each command takes about 2 1/2 minutes to complete. It takes about 12 minutes to accomplish the "fixing" of the machine due to the # of commands that need to be run. I am assuming the core file under /var/log/samba/cores/winbindd/core will be relevant to the problem I am having. $ lsb_release -rd Description:Ubuntu 10.04.1 LTS Release:10.04 $ apt-cache policy winbind winbind: Installed: 2:3.4.7~dfsg-1ubuntu3.2 Candidate: 2:3.4.7~dfsg-1ubuntu3.2 Version table: *** 2:3.4.7~dfsg-1ubuntu3.2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 2:3.4.7~dfsg-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- winbind crashes https://bugs.launchpad.net/bugs/667269 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 570944] Re: passwd : gives "Authentication token manipulation error"
I have interleaved the information, removed the timestamps and substituted DOMAIN\first.last for the actual: $ passwd Changing password for DOMAIN\first.last passwd[30381]: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in /etc/passwd passwd[30381]: pam_winbind(passwd:chauthtok): getting password (0x0028) (current) NT password: passwd[30381]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' granted access passwd[30381]: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in /etc/passwd passwd[30381]: pam_winbind(passwd:chauthtok): getting password (0x) Enter new NT password: Retype new NT password: passwd: password updated successfully passwd[30381]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' OK passwd[30381]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' password changed passwd[30381]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' granted access gnome-keyring-daemon[30390]: gp11_module_get_slots: assertion `data->funcs' failed gnome-keyring-daemon[30390]: lookup_login_session: assertion `slot' failed gnome-keyring-daemon[30390]: lookup_login_keyring: assertion `GP11_IS_SESSION (session)' failed gnome-keyring-daemon[30390]: create_credential: assertion `GP11_IS_SESSION (session)' failed gnome-keyring-daemon[30390]: egg_error_message: assertion `error' failed gnome-keyring-daemon[30390]: couldn't create new login credential: (unknown) passwd[30381]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match. $ and the password has changed via a test of `ssh`-ing into any Linux machine. -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 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 588031] Re: [Realtek ALC269] no sound on external speaker jack (Optiplex 980)
I have same problem: no sound from headphones in front or rear jack on two Optiplex 980's with i5 chip, 64-bit LucidLynx. I do have an internal speaker, and that does work, and it does shut off when I plug the headphones in. These are the first 980's/i5's that i have worked with. Optiplex 745, 755, 760, 780 with Intel duo core and lesser work fine. -- [Realtek ALC269] no sound on external speaker jack (Optiplex 980) https://bugs.launchpad.net/bugs/588031 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 570944] Re: passwd : gives "Authentication token manipulation error"
FYI: I can get `passwd` to work if I change one line in common-password >From the winbind default-configured line of: password [success=1 default=ignore] pam_winbind.so use_authtok try_first_pass To: password [success=1 default=ignore] pam_winbind.so try_first_pass So looks like just the "use_authtok" parameter is misbehaving. (not sure what that really means or with whom the problem lies) -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 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 570944] Re: passwd : gives "Authentication token manipulation error"
FYI: I can get `passwd` to work if I change the line in common-password From: password [success=1 default=ignore] pam_winbind.so use_authtok try_first_pass To: password sufficient pam_winbind.so I'm not sure if I'm creating other problems with the above edit, since I'm not PAM savvy. I have to wait one day to change my password again, but I will try a more minimal change of: password [success=1 default=ignore] pam_winbind.so try_first_pass Meaning, I will just remove the "use_authtok" to see if that is the problem. -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 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 570944] Re: passwd : gives "Authentication token manipulation error"
Is this what you need? $ cd /etc/pam.d $ cat common-auth common-session-noninteractive common-session common-password common-account | grep -v "^#" auth[success=2 default=ignore] pam_unix.so nullok_secure auth[success=1 default=ignore] pam_winbind.so krb5_auth krb5_ccache_type=FILE cached_login try_first_pass authrequisite pam_deny.so authrequiredpam_permit.so session [default=1] pam_permit.so session requisite pam_deny.so session requiredpam_permit.so session requiredpam_unix.so session optionalpam_winbind.so session [default=1] pam_permit.so session requisite pam_deny.so session requiredpam_permit.so sessionrequiredpam_mkhomedir.so skel=/etc/skel/ umask=0027 session requiredpam_unix.so session optionalpam_winbind.so session optionalpam_ck_connector.so nox11 password[success=2 default=ignore] pam_unix.so obscure sha512 password[success=1 default=ignore] pam_winbind.so use_authtok try_first_pass passwordrequisite pam_deny.so passwordrequiredpam_permit.so passwordoptionalpam_gnome_keyring.so account [success=2 new_authtok_reqd=done default=ignore]pam_unix.so account [success=1 new_authtok_reqd=done default=ignore]pam_winbind.so account requisite pam_deny.so account requiredpam_permit.so Here is the smb.conf, with comments removed and substituted in , , where appropriate. [global] workgroup = security = ADS password server = ..com, ..com realm = .COM server string = %h server (Samba, Ubuntu) dns proxy = no log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d encrypt passwords = true passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes map to guest = bad user idmap backend = idmap_rid:=50-99 idmap uid = 50-99 idmap gid = 50-99 allow trusted domains = no winbind offline logon = true template shell = /bin/bash template homedir = /home/%D/%U winbind normalize names = yes winbind use default domain = yes usershare allow guests = yes -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 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 570944] Re: passwd : gives "Authentication token manipulation error"
i am not using likewise-open on Lucid cause likewise-open no longer supports setting up Samba shares with ActiveDirectory integration. Meaning from a Windows machine, I cannot access \\linuxmachinename\sharename and this is important to our Windows/Linux workplace. (And I no longer see the advantage or point to using likewise-open. It only adds another mysterious layer to the whole samba/winbind realm.) -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 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 554023] Re: gdm fails to start
Short Story: Kernel 2.6.32-11.15 is a kernel that causes the problem on my LucidLynx machine with all updated packages. Kernel 2.6.32-10.14 is a kernel that boots fine on my LucidLynx machine with all updated packages. Attached is the Xorg.0.log file from booting with the latest 2.6.32-21.32 kernel with "nomodeset" and with ModeDebug. SideNote: the Beta 1 LiveCD boots fine on my machine, and that release used kernel 2.6.32-16.25 (so that part doesn't make sense to me, since that kernel as of today does NOT work, but I'll let you deal with this conflicting information. (Unless the Beta 1 LiveCD used "nomodeset" to boot up and Betat2 LiveCD did not?)) Longer story: I did this testing today: 2.6.32-7.10Boots fine. 2.6.32-10.14 Boots fine. (2 tests) 2.6.32-11.15 Fails but works fine with "nomodeset" (2 tests) 2.6.32-12.16 Fails but works fine with "nomodeset" 2.6.32-12.17 Fails but works fine with "nomodeset" 2.6.32-14.20 Fails but works fine with "nomodeset" 2.6.32-16.25 Fails but works fine with "nomodeset" 2.6.32-16.25 in the form of the Beta1 LiveCD boots fine. <-- does this make sense? 2.6.32-17.26 Fails but works fine with "nomodeset" 2.6.32-18.27 Fails but works fine with "nomodeset" 2.6.32-19.28 Fails but works fine with "nomodeset" 2.6.32-20.29 Fails but works fine with "nomodeset" 2.6.32-21.32 Fails but works fine with "nomodeset" The infromation in the previous posting had a syntax error, the word Device needed quotes, as in: Section "Device" and thank you again for your time on this. ** Attachment added: "Xorg.0.log_nomodeset_ModeDebug" http://launchpadlibrarian.net/46691474/Xorg.0.log_nomodeset_ModeDebug -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
If I go here, https://edge.launchpad.net/ubuntu/+source/linux/2.6.32-12.17, and download https://edge.launchpad.net/ubuntu/+archive/primary/+files/linux_2.6.32.orig.tar.gz this is not revision 17, this is revision 0 or 1 , right? How do I apply patches or revs to get that souce code tar ball up to rev 17? (sorry) and then I would just run these 3 commands: make mrproper fakeroot make-kpkg --initrd --append-to-version=-doggy kernel-image kernel-headers then install whatever .deb file is lying around, via `sudo dpkg -i *.deb` ? -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
Thank you. Adding "nomodeset" to the linux boot line via editing GRUB, worked 3 out of 3 boots. That is excellent. Not using "nomodeset" failed 4 out of 4 times. (just making sure I the problem still exists) Aside: when I initially moved the machine that I just tested from its directly attached monitor/keyboard/mouse to my cube with the 4-way TRENDnet KVM, it actually booted up fine for the first time. Then failed on subsequent times as expected. I may have seen that phenomena on other occasions. I felt like mentioning it may be important. Also, when the first problem occurred, and I may have said this way above, I think, I booted up the 2 previous kernels that were available to me on the GRUB menu and those failed as well. That's why I always thought it wasn't a kernel problem, but I know nothing about all of this and who knows what I did so long ago. I will grab the BETA1 kernel, if possible, since I know the BETA1 LiveCD works and see if the older kernel amongst all the newer packages works or not. -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 570944] Re: passwd : gives "Authentication token manipulation error"
Correct, `passwd` works with likewise-open on hardy, and fails with winbind on lucid. I do not know what the outcome of `passwd` is on hardy without likewise-open, nor the outcome of `passwd` on lucid with likewise-open. I will ask this on the Lucid forum at http://ubuntuforums.org/showthread.php?t=1459309 -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 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 570944] Re: passwd : gives "Authentication token manipulation error"
Yes it works on HardyHeron. I used likewise-open to faciitate the ActiveDirectory integration on HardyHeron, rather than just the native samba/winbind integration on LucidLynx. But that may have nothing to do with it, but is worthy of mentioning. -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 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 570944] [NEW] passwd : gives "Authentication token manipulation error"
Public bug reported: Binary package hint: samba `passwd` for ActiveDirectory account gives "Authentication token manipulation error" I have latest and greatest of LucidLynx updates. winbind2:3.4.7~dfsg-1ubuntu3 samba 2:3.4.7~dfsg-1ubuntu3 I have ActiveDirectory integration with Samba/Winbind. (not Likewise-Open) Logging into Console window or `ssh`-ing into machine works fine using DOMAIN\first.last account names. Trying to change password with the `passwd` program: $ passwd Changing password for DOMAIN\first.last (current) NT password: passwd: Authentication token manipulation error passwd: password unchanged $ In the /var/log/auth.log file I get this output in conjunction with the above passwd attempt: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in /etc/passwd passwd[16109]: pam_winbind(passwd:chauthtok): getting password (0x002a) passwd[16109]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' granted access passwd[16109]: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in /etc/passwd passwd[16109]: pam_winbind(passwd:chauthtok): getting password (0x0012) I don't see anything particularly wrong with that output, other than it seems to stop prematurely. This is my default-created /etc/pam.d/common-password file: password [success=2 default=ignore] pam_unix.so obscure sha512 password [success=1 default=ignore] pam_winbind.so use_authtok try_first_pass password requisite pam_deny.so password required pam_permit.so password optional pam_gnome_keyring.so I've Googled for "Authentication token manipulation error", but most cases involve local Linux accounts or other uninteresting problems. I don't think any entries in smb.conf have an effect on passwd, but here's a snippet of entries with the word "pass" or "encrypt" in them: password server = machine.domain.com encrypt passwords = true passdb backend = tdbsam unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes encrypt passwords = true I can successfully change password, using `passwd` for a local Linux account. $ passwd Changing password for localAccount. (current) UNIX password: Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully $ ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 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 501130] Re: hostname -f does not show FQDN
** Tags removed: needs-upstream-testing -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] Re: hostname -f does not show FQDN
I downloaded linux-image-2.6.34-020634rc5-generic_2.6.34-020634rc5_amd64.deb and installed it, and ran it at the Grub menu. $ uname -a Linux bee69.omgeollc.com 2.6.34-020634rc5-generic #020634rc5 SMP Tue Apr 20 09:07:31 UTC 2010 x86_64 GNU/Linux $ Same problem: `hostname -f` and `hostname -i` are broken as described above. -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/45571849/UdevLog.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/45571843/ProcCpuinfo.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] Lspci.txt
apport information ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/45571840/Lspci.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/45571847/ProcModules.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/45571848/UdevDb.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/45571846/ProcInterrupts.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/45571839/CurrentDmesg.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/45571842/Lsusb.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/45571838/BootDmesg.txt -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 501130] Re: hostname -f does not show FQDN
1.) I just built out a brand new machine with LucidLynx Release Candidate and updated to the latest packages and rebooted. So this is a virgin system. ( i haven't edited a thing.) 2.) Here is the result of this set of commands: $ hostname; hostname -f; hostname -s; hostname -i machine69 machine69 machine69 127.0.1.1 $ sudo ifconfig -a eth1 Link encap:Ethernet HWaddr 00:21:70:53:d3:77 inet addr:164.179.215.77 Bcast:164.179.215.255 Mask:255.255.255.0 >From another machine in the network: $ nslookup machine69 machine69.DOMAIN.com 164.179.215.77 >From my point of view, I clearly have an IP address, so `hostname -i` is wrong. I clearly am in DNS in the network with a FQDN, so `hostname -f` is wrong. (not sure what I think what just `hostname` should output at this time.) 3.) If I edit /etc/hostname, and change machine69 to "machine69.DOMAIN.com" and run `sudo hostname machine69.DOMAIN.com`, I should be able to influence both the `hostname` and `hostname -f` command. $ hostname; hostname -f; hostname -s; hostname -i machine69.DOMAIN.com machine69 machine69 127.0.1.1 So at least `hostname` has been "fixed", but `hostname -f` and `hostname -i` still broken. 4.) I will run `apport-collect -p linux 501130` after this posting. 5.) the hostname, "machine69" and domain name "DOMAIN" has been changed from the real names in this posting. 6.) Does anyone agree with me about what `hostname -f` and `hostname -i` should output? 7.) And does anyone else show the same lack of output from the hostname commands? ** Tags added: apport-collected ** Description changed: On LucidLynx (with all the current updated), while connected to my company's internal network, when I run this: hostname; hostname -f; hostname -s; hostname -i I get this: machine15 machine15 machine15 127.0.1.1 What I expect to get (as compared to being on HardyHeron) is this: machine15.domain.com machine15.domain.com machine15 From a default installation of LucidLynx, I have changed /etc/hostname from just the short name (machine15) to the long hostname (machine15.domain.com). This is all I needed to do to make the above hostname commands provide the desired output on a HardyHeron installation. The machines, when they boot up get assigned an IP address correctly and are registered correctly in DNS. (meaning `nslookup machine15` returns a valid entry of: Name: machine15.domain.com Address: - (I purposely have changed my machine name and domain name in the above - write up) + (I purposely have changed my machine name and domain name in the above write up) + --- + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory + AplayDevices: aplay: device_list:223: no soundcards found... + Architecture: amd64 + ArecordDevices: arecord: device_list:223: no soundcards found... + DistroRelease: Ubuntu 10.04 + InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) + MachineType: Dell Inc. OptiPlex 755 + Package: linux (not installed) + PciMultimedia: + + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=3b8a4088-fc00-4ed8-a1c1-db4d06b9b507 ro quiet splash + ProcEnviron: + LANG=en_US.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 + Regression: Yes + Reproducible: Yes + Tags: lucid networking regression-potential needs-upstream-testing + Uname: Linux 2.6.32-21-generic x86_64 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + dmi.bios.date: 12/09/2008 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A12 + dmi.board.name: 0PU052 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 15 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA12:bd12/09/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: + dmi.product.name: OptiPlex 755 + dmi.sys.vendor: Dell Inc. -- hostname -f does not show FQDN https://bugs.launchpad.net/bugs/501130 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 554023] Re: gdm fails to start
Assuming the problem is with the package, xserver-xorg-video-intel, would it be helpful and possible to purge this package and install various versions of this to identify the exact version where the regression occurred? If yes, how does one get hold of all the interim versions of xserver-xorg-video-intel (without rebuilding them on my machine.) -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
I just burned a HardyHeron 8.04.4 CD. That LiveCD boots up fine. -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
Attached is /var/log/dmesg after having added "drm.debug=0x04" without the quotes on the linux command line via the Grub edit menu. This file was created several minutes ago. ** Attachment added: "dmesg+with_drm.debugAndKVM" http://launchpadlibrarian.net/45523833/dmesg%2Bwith_drm.debugAndKVM -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
Just added "video=VGA1:800x600" to end of linux line (without the quotes) and booted (), No change in the outcome. I did a diff between this Xorg.0.log and one previously without that option. It made no difference. Here is the diff: $ diff Xorg.0.log_withKVM Xorg.0.log 7,9c7,9 < Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=5a4c1fd6-dd2e-4bf1-b39e-868aaba80337 ro quiet splash < Build Date: 15 April 2010 11:05:58PM < xorg-server 2:1.7.6-2ubuntu5 (Bryce Harrington ) --- > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic > root=UUID=5a4c1fd6-dd2e-4bf1-b39e-868aaba80337 ro quiet splash > video=VGA1:800x600 > Build Date: 23 April 2010 05:11:46PM > xorg-server 2:1.7.6-2ubuntu7 (Bryce Harrington ) 16c16 < (==) Log file: "/var/log/Xorg.0.log", Time: Fri Apr 23 09:33:52 2010 --- > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 26 10:43:56 2010 -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
1A.) I found a file dmesg_withDebug. I'll assume it was the file that I was supposed to attach a long time ago. 1B.)I'll make another one, some time today. 2.) I just upgraded with latest LucidPackages this morning. Rebooted. Same dead screen problem. 3.) I just booted, successfully, off the Beta 1 LiveCD that I burned on 4/06/2010. (that proves that it's not the KVM switch nor the monitor that are having problems, right?) (not to mention, that earlier in my notes, I tried other KVM switches with same problem.) 4.) I did another test, 2 weeks ago, on yet another different machine, using a Belkin switch. These switches have their own power supply. The TRENDnet, that I'm having a problem with do not. With the latest and greatest Lucid on that machine, with same VGA chipset, did seem to boot successfully using that Belkin switch. But it's not one of my best tests, since that machine belongs to someone else, including the Belkin switch, I can't drag both over to my cube and do better divide and conquer tests. So don't jot this note down as fact.(yet) But I wanted to mention it. 5.) But having said all of that, even if we assume that it is a power thing, the Beta LiveCD works fine. So it still is a software problem. It used to work. 6.) I will burn a HardyHeron CD, to prove that these KVM switches work fine with older releases. 7.) I owe you one test with "video=VGA1:800x600" on linux command line via Grub menu. ** Attachment added: "dmesg_withDebug" http://launchpadlibrarian.net/45522955/dmesg_withDebug -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
** Package changed: linux (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
using the ReleaseCandidate that I burned today, 4-23-2010, booting the LiveCD exemplifies the same problem. Black/dead screen when using KVM(TRENDnet) switch. I never see the purple screen with the 5 dots blinking. LiveCD boots fine without KVM switch. -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
I've updated my machine with latest Lucid updates. No change in problem: Same problem where using the TRENDnet KVM switch causes X to not recognize the monitor. Without the KVM, everything is fine. Looking at both Xorg.0.log files, the files are identical for the first 151 lines, then right at the line of: (II) intel(0): EDID for output VGA1 is where they begin to differ. When machine is hooked up to KVM switch, the next line is: (II) intel(0): EDID for output HDMI1 When machine is not hooked up to KVM, the next line starts hundreds of lines of Monitor resolutions and Mouse detections. -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
LiveCD of 4/16/2010 still does not work with my TRENDnet KVM switch. Another point to make, I can boot up a machine with a monitor directly attached. And then I can rearrange the monitor cable such that I am going through the KVM switch. That works. So, the problem is when "the thing" that does monitor detection, or KVM detection, is screwing up on the KVM detection. But the Grub Menu is displayed, so Grub has no problem throwing bits up through the KVM switch. -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 522410] Re: no support for Samba 3.4.5
On April 5th, Likewise-Open confirmed that they will not support the Samba integration for Lucid platform. Thus the solution that I chose, is to: `sudo apt-get purge likewise-open` and implement the native solution using winbind and samba. Now that I got that working, I can't see what benefit there is to using Likewise-Open, other than it does all the manual configuration steps for you but then sticks in its own glue which evidently can get in the way when Likewise-Open decides to not support a feature that is native with samba/winbind. -- no support for Samba 3.4.5 https://bugs.launchpad.net/bugs/522410 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 554023] Re: gdm fails to start
on a different machine than any of the above, but with same VGA controller, the LiveCD of 4/12/2010 boots up, using a Belkin KVM switch. (not a TRENDnet). One difference between the Belkin and TRENDnet KVM switches, is that Belkin has an AC/DC adapter that provides power to the switch, the TRENDnet does not. (does that help anyone?) -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
Problem still exists with a live CD burned today, 4/12/2010. (this bug is critical to us, as we outfit each developer with a Windows machine, a Linux machine, one monitor, and of course, one KVM switch.) -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
just to reiterate, I am able to boot the Beta1 LiveCD , using the KVM switch. (proving the KVM switch is good) I have another machine that I rebuilt out with Beta1 LiveCD and no further updates. It boots fine on a different KVM switch, but cannot boot up using an April 5th LiveCD. (proving again that the KVM switch is good, with a whole different set of equipment) FYI: the KVM switches we are using, are TRENDnet, usb-type, 2-port and 4-port. We have dozens in use with HardyHeron, and a half dozen in use with LucidLynx machines. These are good no-frill KVM switches. They do not have a separate power supply like Belkin switches do. -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
attached is dmesg_withDebug which is /var/log/dmesg but with "linux " line in grub menu appended with "drm.debug=0x04". This is booting the machine with the KVM switch and the dead screen. -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
Xorg.0.log_withKVM is attached ** Attachment added: "Xorg.0.log_withKVM" http://launchpadlibrarian.net/43555767/Xorg.0.log_withKVM -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
Adding an extra wrinkle to my problem(sorry). I have determined that my problem still is a problem, but it exists only if I am using a KVM switch for the machines. If the monitor is directly attached, the console window comes up fine, and, a LiveCD (April 5th) comes up fine. But with the KVM switch, I have the dead screen problem. I've tried a second KVM switch and a second monitor. Same problem. It used to work with the KVM switch prior to March 23rd. Would this still be the intel driver? I've attached Xorg.0.log_noKVM (where it does work), and Xorg.0.log_withKVM where it doesn't work. ** Attachment added: "Xorg.0.log_noKVM" http://launchpadlibrarian.net/43555634/Xorg.0.log_noKVM -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Re: gdm fails to start
On a second machine (with same problem), I just booted up 2.6.32-16 kernel, and the problem (dead screen) happened. But having said that, that -16 kernel was installed on 3/13/2010, per /var/log/apt/history.log and I did not have the problem then. The problem occurred about March 23rd after an update(a large one, over hundred packages). I don't have the -17, or -18 kernel. But if I remember correctly, once the problem occurred, booting up any older kernel didn't fix anything. And isn't the problem more in the xserver-xorg-video-intel (2.9.1-1ubuntu13, 2.9.1-1ubuntu16), package rather than the kernel? (xserver-xorg-video-intel did get upgraded on 3.23.2010) (doing the drm.debug=0x04 next. As soon as I figure out how to do that.) -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] setxkbmap.txt
apport information ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/43429216/setxkbmap.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/43429221/xdpyinfo.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/43429215/Xrandr.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/43429211/XorgLogOld.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/43429207/XorgLog.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/43429201/UdevLog.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/43429199/UdevDb.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/43429198/RelatedPackageVersions.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/43429196/ProcModules.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/43429192/ProcInterrupts.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/43429190/ProcCpuinfo.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] PciDisplay.txt
apport information ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/43429188/PciDisplay.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/43429187/Lsusb.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] Lspci.txt
apport information ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/43429185/Lspci.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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 554023] GdmLog2.txt
apport information ** Attachment added: "GdmLog2.txt" http://launchpadlibrarian.net/43429182/GdmLog2.txt -- gdm fails to start https://bugs.launchpad.net/bugs/554023 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
