in my case, ubuntu-19.04, besides dashtodock also activity configurator
does not work anymore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1819086
Title:
Ubuntu 19.04: Dash-to Dock
kernel 4.15.0-21:
hi cascardo,
previously, I attempted to remove the kernel via synaptic. And
linux-image-4.15.0-21 could not be removed.
This time I did
apt-get remove --purge.
I get (translation from german)
rmdir: /lib/modules/4.15.0-21-generic could not be removed: not empty,
and
dpkg:
ad #3 (continued):
attempt to de - install kernel 4.15.0-21: not possible to de - install the
image 4.15.0-21!
Removed the .postrm and .generic.list files, related to this kernel, in
/var/lib/dpkg/info/ in order to be able to get "apt" working.
Found 4.15.0-20~16.04 (version april 25) in
ad #3:
earlier today, I have tested the kernel 4.15.0-21 under lubuntu-16.04,
taken from ppa:canonical-kernel-team/ppa.
So far, 3 consecutive boots without problems.
I will report back after I have de - installed this kernel again, and
have replaced it by what I find in xenial-proposed.
--
kernel 4.15.0-20, backported to 16.04:
install is okay, BUT no boot (kernel panic); afterwards, the kernel is
uninstallable!
The same behaviour is found with kernel 4.19.0-19 for bionic.
Had to remove the .postinit, .postrm, etc. files in /var/lib/dpkg/info/
in order to be able to use the apt
#15:
after modifying /etc/initramfs-tools/conf.d/resume as described it is
necessary to do
sudo update-initramfs -u.
After doing this,the boot is normal; in my case the total boot time is
6.8s.
Apparently, there is a problem with the UUID in /resume.
--
You received this bug notification
slow boot:
a description of "my bug" can obviously be found in askubuntu.com, question:
1013830.
I followed the suggestion to modify
/etc/initramfs-tools/conf.d/resume
and replaced the line RESUME=UUID= . by RESUME=none
Unfortunately, it did NOT resolve "my bug".
@nio-wiklund
Could you
@nio-wiklund
as I mentioned in #5, also in my case the bug (33sec delay during boot) occurs
with lubuntu only (not with xubuntu, kubuntu, mate, ubuntu). Thus, it appears
that the bugs reported by us may be related.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can report the following:
- Export of a lubuntu-18.04 VM running in VB in a 32bit host with HD.
This VM does not show the delay of about 30sec.
- Import of this VM into VB on the 64bit host with SSD; on this host all
64bit lubuntu-18.04 VMs show the 30 sec delay.
- Run the 32bit VM in VB on
exactly same problem for my lubuntu/lxqt bionic 64bit installation in
virtualbox: 33.9 sec from the boot menu to login screen. No problems for
the other flavours as mentioned above.
No such problems for a 32 bit installation without SSD, again as virtual
machine.
--
You received this bug
Update of lubuntu-18.04 (and ubuntu-mate-18.04)from kernel 4.13.0-36 to kernel
4.15.0-10:
boot fails:
Boot stops shortly after the boot screen appears, then screen becomes
black. Afterwards, the system tries several times to come up with the
boot screen again, but never succeeds; then stops
Boot of both ubuntu-mate and lubuntu/lxqt (both 18.04) with kernel
4.15.0-10 in virtualbox:
Boot starts correctly until the boot screen appears; continues to boot
for the fraction of a second. Then screen becomes black. System tries
again to come up to the boot screen several times. Then stops
ad #27:
for a very recent kernel, you could try 4.14.0-17 from the canonical-
kernel-team PPA: for me (Dell e6500) it runs reliably.
However, you need the boot option acpi=off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ad #28:
you need to use the canonical-kernel-team/unstable PPA!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to linux-image-extra-4.13.0-26-generic the system
ad #22 and 23:
same with me: 4.13.0-31 not working
BUT 4.4.0-112 working (without boot options) (32bit installation)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to
ad #19
I've tried 4.14.14 as well: no boot without additional boot options.
With the above mentioned 5 boot options it fails to boot "sometimes"; one out
of three, may be.
It should mention that I'm using a dell latitude e6500 for these tests; the
discrepancy between our results will probably
ad #16:
in my case, mainline kernels, including 4.15-rc8, do also not work (even
with acpi=off).
However, 4.15-rc8 boots when adding (in grub) the 5 (!) options (all
seem to be necessary) acpi=off noapic nolapic irqpoll pnpbios=off (the
first 3 options are not sufficient; the last two options
for me,lubuntu,16.04, 32 bit installation, no kernels 4.13 and 4.14
boot, neither without or with acpi=off. Without acpi=off, boot stops
right after leaving the grub menu; with acpi=off after the message
"starting to show plymouth boot screen".
Neither does kernel 4.14.14-041414 boot; it fails
ad #16 to 19:
the problem, as described above, has disappeared with kernel 4.11.0-11
-> internet access is possible when strongswan vpn is activated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ad #16:
the problem, as described above, still exists with kernel 4.11.0-9.
Upgrading to 4.12.0-4 solves the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
Title:
no internet
ad 16:
problem still exists with kernel 4.11.0-8: no internet access when strongswan
vpn is activated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
Title:
no internet connection when
add #16:
Thanks for your comments and suggestions!
kernel 4.11.0-7 has the same problem as the previous 4.11 builds:
strongswan vpn is activated, but no access to internet is possible.
Mainline kernel 4.11.6 (version from 17-06-2017): As I mentioned in one
of my previous mails to you, it has
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898749/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898748/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898750/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898743/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898752/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898751/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898754/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898753/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
Title:
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898745/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898746/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
Title:
no
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898744/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898742/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
Title:
no
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1698918/+attachment/4898747/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698918
apport information
** Tags added: apport-collected xenial
** Description changed:
After the update from 4.10.0-22 to 4.11.0-6 there is no connection to the
internet anymore after starting strongswan vpn, v5.5.1. Strongswan vpn starts
as expected, but no http - connections can be
Public bug reported:
After the update from 4.10.0-22 to 4.11.0-6 there is no connection to the
internet anymore after starting strongswan vpn, v5.5.1. Strongswan vpn starts
as expected, but no http - connections can be established.
The same problem with the mainline kernel 4.6.11.
Downgrading
ad #7:
I confirm that your recent build 4.9.0-8 in ppa:canonical-kernel-team/unstable
boots properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642192
Title:
i386 4.9 in -proposed fails to
ad #5:
with the kernel 4.9-rc8 the boot problem described above has returned! No boot
possible; same behaviour as for the kernel versions BEFORE 4.9-rc7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
at #4:
with the newest version of kernel 4.9, namely 4.9-rc7, the problem
mentioned above has disappeared: I can boot correctly with this new
kernel version for lubuntu-17.04. This holds for a lubuntu-17.04 VM
under virtualbox.
--
You received this bug notification because you are a member of
No boot with any of the the available 4.9 kernels, in particular
4.9.0-1, under Lubuntu-17.04 and 16.04.
Find similar lines in the console log, in particular the following which
was mentioned above:
Begin: Waiting for root file system ... Begin: running /scripts/local-block ...
done.
Begin:
Public bug reported:
lxqt was installed with lxqt metapackage. Afterwards, ppa:lxqt/ppa was
added, and update made via sudo apt-get update.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblxqt-l10n (not installed)
ProcVersionSignature: Ubuntu 4.6.0-12.14-generic 4.6.7
Uname: Linux
ad #15:
I also feel that we talk about two different issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570352
Title:
strongswan vpn cannot be established via the network-manager
To manage
ad #12:
Strange, for me, vpn can be established also from the GUI. I checked it with
two machines, both Lubuntu-16.04 under kernels 4.4.0-25 and 4.6.0-7.
Have you checked that you can set - up vpn via the console by using the
"ipsec" commands? (That worked also when I had the problem with
strongswan vpn, establishing connection via network manager:
with the most recent version of the network-manager-gnome,
v1.2.0-0ubuntu.16.04.3, vpn can again be established via the network
manager! No complaints anymore from my side.
--
You received this bug notification because you are a
for completeness:
the very recent network-manager, v 1.1.93-0ubuntu4 did not solve the problem:
situation is unchanged, strongswan vpn cannot be established via the
network-manager.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ad #3:
I would need some advice if you wish me to become active here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570352
Title:
strongswan vpn cannot be established via the network-manager
To
ad #2:
Setup of VPN via the network manager was working previously.
According to the network manager, the last successful contact to VPN was made 4
days ago
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
strongswan vpn cannot be established via the network-manager
-> connection fails without error message.
When attempting to do "configure vpn" with the network-manager, the
error appears "The VPN service org.freedesktop.NetworkManager.strongswan
could not be found
ad #4:
simon, just checked with kernel 4.3.0-4: strongswan vpn works now!
(This test is made with lubuntu-15.10)
Thanks for your remarks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
ad #4:
simon, just checked with kernel 4.3.0-4: strongswan vpn works now!
(This test is made with lubuntu-15.10)
Thanks for your remarks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523133
ad #2:
the problem appears still not to be fixed with kernel 4.3.0-3.12 (dec 10):
strongswan vpn does not work (same behavior as described in #1).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
ad #2:
the problem appears still not to be fixed with kernel 4.3.0-3.12 (dec 10):
strongswan vpn does not work (same behavior as described in #1).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
strongswan vpn does not work with any of the published kernels 4.3
(including 4.3.0-2):
I have already reported this problem some days ago to strongswan.org under
ticket #1189:
"I'm using strongswan 5.1.2-0ubuntu8 in lubuntu-16.04 (development) with kernel
4.3.
Setting up
Public bug reported:
strongswan vpn does not work with any of the published kernels 4.3
(including 4.3.0-2):
I have already reported this problem some days ago to strongswan.org under
ticket #1189:
"I'm using strongswan 5.1.2-0ubuntu8 in lubuntu-16.04 (development) with kernel
4.3.
Setting up
affects me too after upgrading from Lubuntu 15.04 to 15.10.
Tried to reinstall the package because with "systemd-analyze" I get the answer:
"boot not yet finished. Try later".
In fact, the boot finishes after 20 min.
I traced the problem back to mysql.service. Consequently, I tried to re
-
affects me too after upgrading from Lubuntu 15.04 to 15.10.
Tried to reinstall the package because with "systemd-analyze" I get the answer:
"boot not yet finished. Try later".
In fact, the boot finishes after 20 min.
I traced the problem back to mysql.service. Consequently, I tried to re
-
at #2:
probably similar behaviour as reported in #2 when installing this kernel in
lubuntu-15.04: boots normally, but mouse freezes immediately afterwords, then
machine crashes.
Previous kernel version -13.15 works correctly.
--
You received this bug notification because you are a member of
error occurs with daily build of lubuntu 15.10 (20150914) when booting
with usb made with unetbootin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495017
Title:
ubiquity crashed with permission
ad #5:
thats exactly what I did in #4.
So far, I did not encounter problems related to the gcc5 transitions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483424
Title:
Depends: libstdc++6 (=
libreoffice ~wily1+gcc5:
I got the above version of libreoffice installed under lubuntu 15.10 from
ppa:libreoffice/ppa after activating the wily-proposed pocket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
kernel 3.19.0-18:
works for me with dell e6500 under 15.04-lubuntu (i386 architecture) (while
kernel 3.19.0-17 was not working).
Startup time is 4.9s (kernel), similar to other recent kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
at #13:
v4.0-rc7 mainline boots okay on dell e6500.
Startup time under systemd is about 5.7sec (kernel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage
at #15:
one time boot with 3.19.0-17:
added 'drm.debug=0xe' to the boot options, removed quiet no splash.
Boot attempt with 3.19.0-17 was made at 10:56, I suppose.
Later, successfully booted was with 4.0.
Included /var/log/kern.log.
** Attachment added: boot attempt with 3.19.0-17
ad #18:
... boot the bad one without drm.debug, quiet and splash, hoping that
you'll get something on the screen instead.. take a picture if you do
did it ... produces some pages... I could send you /var/log/boot?
On the other hand, how could I write the boot messages into a file?
Please give
ad #17:
tried again with 3.19.0-17 (14:30).
Aterwards, restart with with 4.0.2.
kern.log attached
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453593/+attachment/4398059/+files/kern.log
--
You received this bug notification because you are a member
#24:
first bisect kernel at
http://koti.kapsi.fi/~tjaalton/gm45;
my architecture is i386, 32bit? Can I contribute something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
[gm45]
at #3 - bios upgrade:
considering the fact that such an upgrade is a sensitive matter, I feel
that the suggested procedures are somewhat risky because not being
really transparent to me.
On the other hand, I have a virtual win7 machine (32bit install) (under
virtualbox) at my disposal.
Maybe,
at #3 - bios upgrade:
i just discover that sudo dmidecode -s bios-version sudo dmidecode -s
bios-release-date do not work with kernel 4.0, but still work under 3.19.0-16.
I get the response: /dev/mem: no such file
Is this a bug or a new feature?
--
You received this bug notification because
at #6:
3.19.6-vivid boots normally. Startup time (kernel) under systemd is 4.8s (about
what is found for other recent kernels).
For completeness, I tested also 3.19.8-vivid: boots also normally. However,
startup time (kernel) is considerably longer, about 8s!
--
You received this bug
at #6:
3.19.8-vivid boots.
Observation: startup under systemd appears to be unusually slow: startup
finished in 8s (kernel) (as compared to normally about 4.7s).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
at #18:
could only repeat / duplicate the report of richard jones??
However, please let me know if you would eventually need the output of
some specific commands concerning my system!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
3.19.0-17, no boot:
probably the same finding as reported in #1453302.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453542
Title:
15.04 with 3.19.0-17 kernel boot failure
To manage
3.19.0-17, no boot:
lubuntu 15.04 on dell e6500 boots normally with the upstream kernel
4.1-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453542
Title:
15.04 with 3.19.0-17 kernel boot
3.19.0-17, no boot - at #12:
15.04 on dell e6500 boots normally with the upstream kernel 4.1-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453302
Title:
Linux kernel freeze (it seems in
Public bug reported:
boot with 3.19.0-17 freezes at very early stage, way before the
appearance of login screen.
no such problems with kernel 3.19.0-16.
Tested upstream kernels 4.0.0-1, 4.01, 4.0.2 and 4.1-rc2: all of them
boot normally.
No problems to boot with 3.19.0-17 in a lubuntu15.04
ad #20:
okay!
used ubuntu-bug linux running with 3.19.0-16.
hope it helps!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453302
Title:
Linux kernel freeze (it seems in current/3.19.0-17) on Dell
kernel 3.19.0-17:
no boot that kernel on dell e6500; black screen at an early stage (way before
login).
However, boots as follows: - recovery mode - resume normal boot
(without taking any action prior to resuming!).
No boot problems with 3.19.0-16 nor with 4.0.0-1 (both boot normally).
--
You
kernel 3.19.0-17:
forgot to mention that there are no boot problems when running the
kernel 3.19.0-17 in a virtual machine in virtualbox (on the same
hardware)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
kernel 3.19.0-17:
no boot on dell latitude d505 neither.
However, the kernel obviously boots with the grub option nomodeset because I
can open a console (ctrl+alt+f1); could not open the display, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
dpkg -i --force-overwrite
/var/cache/apt/archives/lxpanel_0.7.2-1ubuntu1_i386.deb (see #4)
did not help in my case, but
dpkg -i --force-overwrite /var/cache/apt/archives/lxpanel-
data_0.7.2-1ubuntu1_all.deb
indeed solved the problem - the lxde desktop works properly again!
--
You received
made the update to version ubuntu2 via sysnaptic without any problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417244
Title:
package lxpanel-data (not installed) failed to install/upgrade:
same problem with i386 architecture:
in fact, the same error messages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417244
Title:
package lxpanel-data (not installed) failed to install/upgrade:
Public bug reported:
upgrade from 14.10 lubuntu to lubuntu-15.04 (dev):
sudo do-release-upgrade -d fails
extras.ubuntu and archive.canaonical.com are de - activated
all ppa'a de - activated
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubuntu-release-upgrader-core 1:14.10.9
I found a workaround which is probably simpler:
sudo sed -i 's/utopic/vivid/g' /etc/apt/sources.list
followed by
sudo apt-get update and sudo apt-get dist-upgrade.
In this way, the ppa version of systemd is upgraded to the most recent ubuntu
version!
Following your suggestion I would, besides
kernel 3.18.0-2:
no luck with this kernel either: same behavior as for the other tested
versions (in particular 3.18-rc3).
dmesg produces: BUG unable to handle kernel null pointer dereference
at ... (as for the other tested kernels).
On the other hand, the new version of kernel 3.16
Public bug reported:
kernels 3.18-rcx (x=1,2,3) and 3.18.0-1:
boot process obviously ends before normal termination.
After finishing booting, there are the following problems and observations:
-boot process takes unusually long,
-horizontal task bar is missing,
- I can use normal terminal
cannot send the output of lspci because of problem with sudo commands
(see above)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388769
Title:
incomplete boot of lubuntu-14.10 with all kernels
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+bug/1388769/+attachment/4251969/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388769
Title:
incomplete boot
** Attachment added: uname.log
https://bugs.launchpad.net/ubuntu/+bug/1388769/+attachment/4251967/+files/uname.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388769
Title:
incomplete boot
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+bug/1388769/+attachment/4251968/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388769
Title:
incomplete
@#2
I will send you first the output of ubuntu-bug firmware-b43-installer for the
(working) version 1:018-2.
Then I will reinstall the version 1:019-1 and send you again the output of
ubuntu-bug firmware-b43-installer
--
You received this bug notification because you are a member of Ubuntu
@christopher penalver
after re - installing version 1:019-1, WIFI works also with the actual version
1:019-1!
Nevertheless, I have sent the output of ubuntu-bug firmware-b43-installer
when using the most recent version of b43.
The only relevant changes I may have made (since filing the bug)
@christopher penalver
I checked the version 1:019-1 of b43 and of the firmware now also with
kernel 3.16.0-24. WIFI works; no problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357436
Title:
boot problems with 3.18:
an observation which may be related to the described problem:
using kernel 3.18-rc2-vivid (or any other 3.18 kernel published so far!) in
lubuntu-14.10 x86 32bit the machine does not come up correctly. In particular,
it comes up without WIFI. Moreover, sudo does not
Public bug reported:
wifi with broadcom 4309 (14e4:4324):
wifi does not work with b43-fwcutter, version 1:019-1. But works after
replacing b43-fwcutter, version 1:019-1 by version 1:018-2.
This is for lubuntu-14.10.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You
** Package changed: ubuntu = b43-fwcutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357436
Title:
no wifi after update of b43-fwcutter
To manage notifications about this bug go to:
wifi problem persists with kernel 3.15.0-1.5 (version 5):
no wifi with broadcom bcm 4309 (driver b43-fwcutter). This is for lubuntu-14.04
trusty.
Connection via cable works,
volker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
wifi problem persists with kernel 3.15.0-1.4:
no wifi with broadcom bcm 4309 (driver b43-fwcutter). This is for lubuntu-14.04
trusty.
Connection via cable works.
On the other hand, wifi is okay when using kernels 3.15 (checked with
3.13 and 3.14).
volker
--
You received this bug
#36
newest aptdaemon (1.1.1-1ubuntu5) does not fix the problem for me: could not
install the newest kernel 3.15.0-1 automatically. Had to do sudo dpkg --install
/path/package.debi.
Using lubuntu-14.04.
volker
--
You received this bug notification because you are a member of Ubuntu
Bugs,
1 - 100 of 148 matches
Mail list logo
