Similarly to comment #74, I have exactly the same symptoms on a Samsung
laptop with Intel HD4000 graphics (i.e. *no* nVidia or any other video
card is/was present). Moreover, it's a fresh install of Ubuntu 16.10. It
is also of note that I've never had this issue before on the same
machine with any
Well, I just did discovered something by accident. I *DID* manage to
start GDM3 just by executing 'gdm3' as *root* from a TTY. I am now able
to login just fine and GNOME works fine.
Launching GDM as a service (systemctl) does not work, though. Why is
this so? And what can I do to resolve the issue
Has this bug been reported on the kernel.org's/freedesktop.org's
bugzilla at all? Since it exists in mainline builds it's an upstream
bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/131
Andrea, it should work just fine. Which basically means: there were no new
reports of machines getting bricked that I know of since many months. For
example, I've been using np530U3C-A05 in UEFI mode just fine since June.
2014-05-09 11:24 GMT+02:00 Andrea Biolo :
> Hi! I have the ultrabook Samsu
Okay, I fooled around here with several mainline kernel versions,
letting them run for a decent amount of time, just to make sure the bug
is hit on resume.
3.13.0 – the bug IS triggered. I just booted, logged in and forgot about
it. When I came back to it, it was sleeping; on resume the bug got
tr
Played around with Unity/Compiz (moving windows, opening dash, etc.)
while running 3.13rc1 to make sure the bug is triggered. And after a
suspend it didn't come back. This leaves us with 3.12.19 being the last
version which is known for working fine, and 3.13rc1 is the first
version which is buggy.
Maybe it's worth the time to involve Unity/compiz devs in this? After
all it's very likely to be their code which screws the kernel up.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/131082
I found out the last working version to be 3.12.19 (latest in the
series) and the first buggy one – 3.13rc1. Therefore the offending
commit is somewhere in the early 3.13 series. I'm afraid cannot do much
more about this, as I am not a too tech-savvy user. I have no experience
in doing the bisectin
Hey Adrian,
Let me just quote what I wrote above 11 months ago:
"First of all, I have installed SAMSUNG BIOS upgrades from within Windows 8,
then reduced Windows partition to leave around 40–50 Gb of free space, the
remaining free space on a HDD was allocated for Ubuntu's "/home" directory.
Next
Dear Chris, have you *actually* read Iuri Diniz's messages you are thanking
him for? At this stage your template messages ARE NOT helpful and are
redundant.
Let me put it this way. First, he's having the same damn hardware as many
other users facing this bug that no one from the Ubuntu kernel wiza
Dear Iuri, maybe upstream (or even freedesktop.org's) kernel folks can help
with this? I don't think this bug has been reported to their bugzilla.
Maybe it's worth to report it there and expect their comments that would
help you out with these tags?
2014-06-17 4:24 GMT+02:00 Iuri Diniz <1315...@b
wizards, and I hope for someone to
help with answering that very exact question.
2014-06-18 1:22 GMT+02:00 Christopher M. Penalver <
christopher.m.penal...@gmail.com>:
> Žygimantas Beručka, as you can respect, this isn't userspace, and the
> triaging is done differently, both down
Dear Iuri, I have reported your bug with your comments to the upstream
bugzilla as https://bugzilla.kernel.org/show_bug.cgi?id=78381 Feel free
to comment if you have anything else to add or want to change something.
** Bug watch added: Linux Kernel Bug Tracker #78381
http://bugzilla.kernel.org/
I believe it indeed is a duplicate of your report. Just let me check if
2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 solves the issue on my machine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Dear shcharr,
A prebuilt 3.13.0-30.54 with that patch applied would be nice to have. I
could give it a test on my machine as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1331654
T
Oh, I see that you've already uploaded it on dropbox! I will give it a
test run.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1331654
Title:
[Dell Inspiron 1525] Cannot resume from sus
I'm having the same issue with the same Inspiron 1525. I have also tried
booting with mainline 3.14.1{,2}, but the issue is still present in
these versions. I haven't tried 3.15rc as of yet since the Broadcom
wireless kernel module fails to build with it.
I just tried, however, running the 3.11.0-
I also noticed that if I try to suspend the system *before* actually
logging in into a Unity session, that is, while lightdm alone is
running, resume from suspend works flawlessly. But once I login to a
Unity/compiz session, there's no comming back from a suspend.
--
You received this bug notific
I have some results from my investigation. I just tried a number of
mainline builds: 3.13rc1, 3.13.{0,6,8,9,11}. With all of them, that is,
from the first RC to the most current release in the 3.13 series,
resuming works flawlessly. It is also of note, as have already been said
above, that 3.14.{1,
Bad news. I just removed all the kernels I tested except the last one
(3.13.11), and after some time tried to suspend it again. It froze again
while coming back from a suspend. If this bug likes to hide like this
and activates just on some condition, it will be hard to nail it down. I
will try, how
Thanks, Christopher. I had wanted to submit those logs apport collects
on a fresh boot after the freeze way before, but no matter how many
times I tried, once I press the submit button, it would just close and
nothing happens. Will try to do it later the way you're suggesting.
And concerning my la
Public bug reported:
The issue hit the system right after uprading from Saucy to Trusty.
Ubuntu Trusty freezes on resume from a suspend on a DELL Inspiron 1525
machine. All I see is just LEDs for disk (just blinks for a moment) and
wifi (stays lit), fan noise and a black screen. No mouse cursor, n
Christopher, I reported the same issue as bug #1315277
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1310823
Title:
[Dell Inspiron 1525] Ubuntu freezes when lid closed
Status in “linux
Joseph, I've already mentioned that I am unable to test 3.15rc since it
boots with a completely black screen start to finish. I don't know what
is the cause and how to circumvent it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
By the way, is it possible to collect any freeze data which might shed a
light on a possible cause?
When I boot after a unclean/hard reboot and log into a Unity session, I
see a number Apport dialog windows (3 to 5 usually). However, when I
press 'OK' on one of them, enter my password, it starts c
I suspect that too as I already mentioned I can suspend/resume before a
Unity/compiz session is actually started. With only a lightdm running it
just works. You trying out a GNOME session just confirms it.
However, it still means there's a bug in the kernel since a piece of
third-party software ca
Hey all. Apologies for the long silence. I confirm that shacharr's
prebuilt packages with the cherry-picked
2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 commit fixed the issue for me.
It must be included it in the next kernel update for Trusty.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1331654 ***
https://bugs.launchpad.net/bugs/1331654
Since shacharr's prebuilt packages with the cherry-picked
2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 commit fixed the issue for me
and you, I'm marking this as a duplicate. The patch must be included it
in the
*** This bug is a duplicate of bug 1331654 ***
https://bugs.launchpad.net/bugs/1331654
Just noting that the patch seems to have been included in Linux 3.13.11.5,
released on 18 July[1]. Looking forward to its inclusion in the official
Ubuntu kernel builds.
1. http://patchwork.ozlabs.org/patch
The patch seems to have been included in Linux 3.13.11.5, released on July
18[1]. Looking forward to its inclusion in the official Ubuntu kernel
builds.
1. http://patchwork.ozlabs.org/patch/370345/
2014-08-06 20:18 GMT+02:00 29185159 :
> ops... broadcom
>
> --
> You received this bug notificati
Calant, let me put it this way. There were no confirmations either from
SAMSUNG or from Ubuntu/kernel devs that the fixes released necessarily
solve those issues (no info from SAMSUNG at all). However, as you can see,
there are almost no new reports that people are still facing the issue.
If you a
And do not forget to get the latest Samsung BIOS updates from within
Windows first! This is of utmost importance.
2013/9/11 calant <1040...@bugs.launchpad.net>
> So I figure the safest thing to do is to wait for Ubuntu 13.10 release?
> Since this uses linux kernel 3.11 which contains the anti br
32 matches
Mail list logo
