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
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--BrightnessLock tab)
I've followed various instructions on the Internet on how to create override
files
or site-wide key
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
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
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
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
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
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
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
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
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
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
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
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
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).
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
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
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
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
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
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
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.
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
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.
[
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
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
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
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
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,
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,
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
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
Everything still working fine on all 80 machines since 2011-04-27.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/736757
Title:
[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
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
Server Team, which is subscribed to samba in
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.
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
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/736757
Title:
[SRU] PANIC (pid 18442): internal
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
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
*** 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
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
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
*** 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
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
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
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
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.
--
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
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
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
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
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
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.
--
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
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
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
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+Devicesseries=imageRUNNER+ADVANCE+seriesmodel=iR-ADV+C5030menu=downloadfilter=0
and at
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
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
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
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
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
Server Team, which is subscribed to samba in ubuntu.
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
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
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
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
** 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
Server Team,
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
** 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
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]:
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]:
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Just added video=VGA1:800x600 to end of linux line (without the quotes) and
booted (CTRL-X),
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
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
--
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
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
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
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.
--
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.
--
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.
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
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.
--
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.
1 - 100 of 164 matches
Mail list logo
