Running 16.04 in 2 different machines, one of which is affected by the bug and
the other not.
I prefer to stay with Xenial since I admin a few family systems and the
workload reduces over time with Xenial now in caretaker mode.
Each was installed at different times, the unaffected one having
Participating in bug
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476 for the last
couple of days.
Clevo barebook W540 pentium 3805U 1.90G onboard graphics BroadwellGT1 single
ssd, intel Wless 3160, only hardware hanging off it is a usb wireless mouse.
Had indefinite hang begin with
Booting into the *-26 kernel gave a very quick handover to Gnome, but with some
kind of
badly painted cursor and progress images apparently bleeding through from the
plymouth screens.
However the deal breaker is that networking isn't enabled at all.
Report then is that *-26 kernel is not a
Further to the above on wireless start, booting into *.23 kernel, Bionic loses
all the retarding
symptoms for Gnome start and for wireless network start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Installing plymouth 0.9.3-3 over the distro 0.9.3-1 had no effect on this
system - amd64 - either.
Steps taken with dpkg for a hash-checked .deb were:
Preparing to unpack .../plymouth_0.9.3-3_amd64.deb ...
Unpacking plymouth (0.9.3-3) over (0.9.3-1ubuntu7) ...
Setting up plymouth (0.9.3-3) ...
I can report a very similar experience after the update to kernel *-24.
The difference with my machine - a barebook Clevo packaged by Pioneer Computers
Australia -
is that no keyboarding, usb mouse, or touchpad use reproducably reduces the
hang time by plymouth to less than an average 90seconds.
This problem appears to be resolved with a recent update. I've restarted
my server and Samba came right up.
--
Windows clients cannot connect unless Samba manually restarted
https://bugs.launchpad.net/bugs/554094
You received this bug notification because you are a member of Ubuntu
Server Team,
This problem appears to be resolved with a recent update. I've restarted
my server and Samba came right up.
--
Windows clients cannot connect unless Samba manually restarted
https://bugs.launchpad.net/bugs/554094
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: kubuntu-netbook
Kubuntu netbook remix's icon order (the icons in any menu -- games,
utilities, etc.) keeps changing and seems to be random every time the
system boots.
** Affects: kubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
The problem seems to have been corrected with the 10.04 release or
earlier. I consider the matter closed, with regards to those who
squashed the bug.
--
Failed boot: After update, cannot detect any hard drives
https://bugs.launchpad.net/bugs/564871
You received this bug notification because you
The following is the only log entry made after last server reboot. This
is after the most recent 10.04 updates. I've also updated the clients
and rebooted them, and they still cannot connect (until Samba is
restarted). Only the last two entries are of the right time:
Public bug reported:
After rebooting from a recent update (update posted in-between 10 April
2010 and 16 April 2010) my server can no longer boot.
It goes to a busybox recovery console, which indicates that absolutely
no sd* devices in /dev.
The boot drive is on an LSI SAS 1068 controller, but
A little more info:
Using Ubuntu Server 10.04 AMD64. Kernel 2.6.32-19-preempt
The UUID in my fstab is accurate, verified in recovery mode with 'blkid'.
Recovery mode accesses the drive fine.
I tried reinstalling grub. No change.
--
Failed boot: After update, cannot detect any hard drives
This appears to be a problem with linux-image-preempt, because upon
telling Grub2 to boot the new vanilla server kernel, the server was able
to boot.
--
Failed boot: After update, cannot detect any hard drives
https://bugs.launchpad.net/bugs/564871
You received this bug notification because you
The following is the only log entry made after last server reboot. This
is after the most recent 10.04 updates. I've also updated the clients
and rebooted them, and they still cannot connect (until Samba is
restarted). Only the last two entries are of the right time:
The network is defined in /etc/network/interfaces as follows:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
The motherboard has two NICs, but
The network is defined in /etc/network/interfaces as follows:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
The motherboard has two NICs, but
Attached is smb.conf
** Attachment added: smb.conf
http://launchpadlibrarian.net/43012220/smb.conf
--
Windows clients cannot connect unless Samba manually restarted
https://bugs.launchpad.net/bugs/554094
You received this bug notification because you are a member of Ubuntu
Server Team,
Attached is the smb.conf from the previous configuration. The
differences should be minor and unrelated to the issue, but I've
attached it in case I am wrong. This configuration worked on the
previous setup with Ubuntu 9.10. When the server was restarted, Windows
systems could resume share
Requested information:
# dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba
libpam-smbpass 2:3.4.7~dfsg-1ubuntu1 samba install ok installed
libsmbclient 2:3.4.7~dfsg-1ubuntu1 samba install ok installed
libwbclient0 2:3.4.7~dfsg-1ubuntu1 samba install ok installed
samba
Attached is smb.conf
** Attachment added: smb.conf
http://launchpadlibrarian.net/43012220/smb.conf
--
Windows clients cannot connect unless Samba manually restarted
https://bugs.launchpad.net/bugs/554094
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attached is the smb.conf from the previous configuration. The
differences should be minor and unrelated to the issue, but I've
attached it in case I am wrong. This configuration worked on the
previous setup with Ubuntu 9.10. When the server was restarted, Windows
systems could resume share
Public bug reported:
Binary package hint: samba
Windows clients cannot connect to the server after the server is restarted. The
samba process is running according to
status smbd and is working fine according to smbstatus.
This has been the case since updating the server from 9.10 to 10.04
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42898298/Dependencies.txt
** Attachment added: SambaInstalledVersions.txt
http://launchpadlibrarian.net/42898299/SambaInstalledVersions.txt
--
Windows clients cannot connect unless Samba manually restarted
Public bug reported:
Binary package hint: samba
Windows clients cannot connect to the server after the server is restarted. The
samba process is running according to
status smbd and is working fine according to smbstatus.
This has been the case since updating the server from 9.10 to 10.04
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42898298/Dependencies.txt
** Attachment added: SambaInstalledVersions.txt
http://launchpadlibrarian.net/42898299/SambaInstalledVersions.txt
--
Windows clients cannot connect unless Samba manually restarted
Public bug reported:
Mounting /tmp noexec is a somewhat common practice for security reasons.
Many script kiddies will paste code they found into /tmp somehow,
compile it, and run it.
Apt doesn't seem to handle this at all, either through checks to see if
/tmp is mounted exec, or through
The same happens on my system with Alpha 6. Two motherboard-integrated
NICs (Pro/1000's) went from eth0, eth1 to eth2, eth3. This broke all
network-related settings which depend on these not changing.
May be somehow related to: https://bugs.launchpad.net/bugs/153727
--
upgrading to Jaunty
Removing the duplicate entries from 70-persistent-net.rules did not solve the
problem on my system. The entries were appended to the file once again (after
the duplicates, which were commented out).
If this is the case for anyone else, try also editing
75-persistent-net-generator.rules.dpkg-old
Public bug reported:
When upgrading from 7.10 (10 April 2008 update) to 8.04 beta, the upgrade
failed, referring to what looks like a corrupt blackjack.xml.
The upgrade command was: sudo do-release-upgrade --devel-release
The following is the last part of the console log from the upgrade
Public bug reported:
Binary package hint: shorewall
Shorewall 3 is configured to store its lock file in a directory which
does not exist.
File: shorewall.conf
Line: SUBSYSLOCK=/var/lock/subsys/shorewall
Solution 1: Change the file to point to a directory that exists, like /var/lock
Solution 2:
Public bug reported:
Binary package hint: shorewall
udev misbehaves in Ubuntu when working with wireless LAN cards,
incrementing the device number without reason.
Using driver: madwifi
Running the following commands:
# ifconfig ath0 down
# wlanconfig ath0 destroy
# wlanconfig ath0 create
32 matches
Mail list logo
