I've experienced the no GUI after installing lubuntu problem.
Here are the details relevant to my case:-
Here are the technical details:-
-rw-rw-r-- 1 ian ian 630M Sep 28 17:10 lubuntu-14.10-beta2-alternate-i386.iso
-rw-rw-r-- 1 ian ian 444 Sep 28 17:07 MD5SUMS_lubuntu
ian@rutherford:~/isos$
Hi Christopher,
On 13 November 2015 at 00:56, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> While you are welcome to do that as a test (as the release and
> architecture are supported downstream via the L/Ubuntu Community), it
> wouldn't be recommended to use a i386
Hi Christopher,
On 15 November 2015 at 22:52, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Ian Bruntlett, could you please undo your WORKAROUND, test drm-intel-
> nightly and advise to the results?
>
Apologies - the results I gave you were for without
Squeezed in a bit more work today...
1. Tried kernel 4.3.0 today (the one you recommended me a few e-mails ago)
with the "nomodeset" parameter and the graphics system went into 640x480
mode, couldn't change it from the desktop. However, the graphics _worked_ :)
2. Viewing menus in GRUB. Did this
Hi Christopher,
On 27 November 2015 at 18:10, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Ian Bruntlett, the issue you are reporting is an upstream one. Could you
> please report this problem following the instructions verbatim at
> https://wiki.ubuntu.co
Hi Christopher,
On 29 November 2015 at 20:56, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Ian Bruntlett:
> >"Don't have e-mail addresses for Daniel Vetter or Jani Nikula. Let me
> have them if you want me to pass the report to them as well."
Hi Christopher,
On 25 November 2015 at 18:10, Ian Bruntlett <ian.bruntl...@gmail.com>
wrote:
> IDEA: Will try running system with Firefox set _not_ to use graphical
> hardware acceleration.
>
Tried that. No luck - bug still present.
BA,
Ian
--
-- ACCU - Professionalism in pro
Hi Christopher,
On 24 November 2015 at 11:11, Ian Bruntlett <ian.bruntl...@gmail.com>
wrote:
> There is one now available for 4.4-rc2.
>>
> Will get onto that when I have time.
>
OK.
Short story: bug still present.
Long story:
These kernel files were downloaded
Hi Christopher,
On 26 November 2015 at 02:04, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Ian Bruntlett, to clarify
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514102/comments/37
> , was this tested to work without nomodeset?
>
Yes. In V
Hi Christopher,
Spent a lot of today learning how to edit files using vim.
On 17 November 2015 at 03:08, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Ian Bruntlett, could you please test the latest mainline kernel
> (4.4-rc1) and advise to the results o
Hi Christopher,
Good news! An Intel graphics specific kernel arrived and I installed it. So
far, the graphics are working fine. However, I must point out that more
testing is required.
Here are the details of the files involved etc:-
On 23 November 2015 at 13:40, Ian Bruntlett <ian.bruntl...@gmail.com>
wrote:
> Hi Christopher,
>
> Good news! An Intel graphics specific kernel arrived and I installed it.
> So far, the graphics are working fine. However, I must point out that more
> testing is
Hi Christopher,
On 24 November 2015 at 02:22, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Ian Bruntlett:
> >"1. Even with that kernel, graphics problems are still present."
>
> Which kernel version specifically?
>
This one:-
lin
Public bug reported:
Installed O.S. on Samsung NC10. Display worked O.K. in text mode so the
install went smoothly. When the system is rebooted, however, switching
to graphics mode results in the below described screen corruption:-
Left Hand Side 80% of screen black with a blue of white pixels
Here is a photo of the problem.
** Attachment added: "Here is a photo of the problem."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+attachment/4975110/+files/Display-problem.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi Joseph,
On 18 October 2017 at 19:47, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
I received an e-mail from qatrac...@stgraber.org
Hi,
On 14 November 2017 at 07:22, Kai-Heng Feng
wrote:
> Sorry for the late reply, please try this kernel,
>
> http://people.canonical.com/~khfeng/lp1724639-2/
No problem. These are the files I downloaded:-
total 58M
-rw-rw-r-- 1 ian ian 936K Nov 15 18:37
Hi,
Tested two kernels this evening. Here are the summarised details...
Testing 21st November 2017
*Installs as kernel 4.12.0*
total 58M
-rw-rw-r-- 1 ian ian 936K Nov 21 20:08
linux-firmware-image-4.12.0_4.12.0-6_i386.deb
-rw-rw-r-- 1 ian ian 11M Nov 21 20:09
Hi Eugene,
On 1 November 2017 at 19:05, Eugene Romanenko <1724...@bugs.launchpad.net>
wrote:
> Ian, sorry, I mixed up apport with apparmor!
> "apparmor=0" kernel parameter
>
OK. Tried that. It fixed things.
Here comment about kernel 4.14
>
Hi Eugene,
On 1 November 2017 at 17:41, Eugene Romanenko <1724...@bugs.launchpad.net>
wrote:
> >From other bugs comments where users also tried 4.14 kernel, I noticed
> network problem is really apport issue. Boot kernel with apport=0
> cmdline option, and network should work.
>
Edited
Hi,
Do you prefer being called Kal-Heng?
On 9 November 2017 at 06:28, Kai-Heng Feng
wrote:
> Please try this kernel,
> http://people.canonical.com/~khfeng/lp1724639-1/
>
> 13 more kernels to test.
>
SUMMARY
=
I have tried the above kernel and the graphics
Hi John,
On 1 November 2017 at 17:08, John Roe <1724...@bugs.launchpad.net>
wrote:
> Can someone help me out how to do this edit. As I have never edited a GRUB
> before.I'm not even sure what the GRUB is
> If I press e is this giving me the GRUB?
>
I had that problem as well :) I'll do my best
Hi,
Sorry for the slow reply. I have been somewhat distracted by a physical
illness
As others have done, I set a GRUB variable with the line:-
GRUB_GFXPAYLOAD_LINUX=text
I also commented out the line that set the GRUB variable
GRUB_HIDDEN_TIMEOUT=0
With those changes in place,
1. Graphics
As I mentioned earlier, when a screenshot is taken of the corrupted
screen, a perfect snapshot is produced, suggesting the frame buffer is
OK and the problem lies elsewhere.
** Attachment added: "screenshot-taken-does-not-match-view-on-screen.png"
SUMMARY:-
Installed upscreen kernel, still got problems. See below for details:-
Did this on personal computer...
Downloaded these files:-
total 58M
-rw-rw-r-- 1 ian ian 11M Oct 19 12:18
linux-headers-4.14.0-041400rc5_4.14.0-041400rc5.201710152230_all.deb
Hi Kal,
On 19 October 2017 at 18:17, Kai-Heng Feng
wrote:
> Does this also happen to 64bit version?
>
The equipment being tested, a Samsung NC10 Netbook, is a 32-bit device, so
I am unable to test it on that.
For convenience, here are some hardware details:-
Intel
Hi Tom,
On 23 January 2018 at 19:02, tom wrote:
> With my Ubuntu version 16.04 LTS i didn't have the problem, until recently!
> I suspect with an update from kernel 4.10.x to 4.13.x
> So I manually removed the kernel image and headers from version 4.13.x,
> thereby in
Have been regularly applying Software Updates with varying degrees of
success.
One thing I did see, once, which was interesting. The "Tick Tock" noise
happened at the same time that the volume indicator started changing
"quiet then loud".
Theory - there are two things changing the sound volume -
I've been downloading and testing Ubuntu STRs (Short Term Releases) for
this bug.
Has the bug:-
20.10 (initial testing)
20.04 (initial testing)
19.10 (kernel 5.3.0-18)
19.04 (kernel 5.0.0-13)
Does not have the bug:-
18.10 (kernel 4.18.0-10)
18.04 (kernel 4.15.0-20)
--
You received this bug
Public bug reported:
This bug appears on 20.04 and 20.10
I believe it is a kernel bug.
Currently reporting from Ubuntu 20.10 (beta), having updated packages.
Kernel is x86_64, 5.8.0-21
It can be mitigated by the echo command,namely:
echo -e "\a\a\a"
So I wrote a small shell script to do
TL;DR - This bug has been fixed.
Detail...
As of last Saturday (14th November 2020), this bug no longer happens with both
Ubuntu 20.04.1 and 20.10. I also noticed that the sound was very much louder
than expected from my system - reducing the volume fixed that OK. Tested sound
by playing a
31 matches
Mail list logo