Public bug reported:
The first I tried to update to Focal fossa, it failed. A day or two
later it went through. As mentioned, booting in normal is no longer
possible, only in recovery mode.The GRUB shows two versions (+ 2 for
recovery), its -124 and ...-122 at the end.
ProblemType: Bug
@laney: I have disabled all my workarounds and placed "session optional
pam_sss.so" just before "session optional pam_systemd.so" in
/etc/pam.d/systemd-user on my Ubuntu 18.04.5 system. Checking
"journalctl --user" for gfvs-daemon entries:
Nov 02 22:45:31 vk2011 dbus-daemon[6128]: [session
I do not have tracker-miner-fs.service at all. My instance of gvfsd is
started by either ibus-daemon, or "systemd --user". Please see the
controversy at
https://gitlab.gnome.org/GNOME/gvfs/-/issues/481#note_948506
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The upstream determined that gvfsd as a systemd user session is starting
too early in Ubuntu, before the desktop enviroment variables are set.
Specifically, KRB5CCNAME env var is missing at the time gvfsd is
started, causing this bug. See the detailed report at
I confirm the same issue on ASROCK A300M AMD Ryzen 2500G with Ubuntu 19.10 on
update Kernel 5.3.0-51 to 5.3.0-53.
Reverting to 5.3.0-51 solves the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem persists in Ubuntu 20.04 as well.
I attempted to investigate this issue a little further, found that it is
caused by a race condition between gvfsd and ibus-daemon, and filed a
bug report upstream: https://gitlab.gnome.org/GNOME/gvfs/-/issues/481
My current workaround is hack, but it
Public bug reported:
I chose French as regional language during the installation of Kubuntu 20.04
(from a live USB key, "Try Ubuntu" installation mode).
On first reboot (I've not rebooted again yet), I noticed some applications were
displaying in English.
In Plasma systemsettings5 > Regional
Same bug for me, but :1.16 instead of :1.45.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632211
Title:
Evolution constantly loses connection to gmail
To manage notifications about this bug go
Public bug reported:
There is a video about bug:
https://www.dropbox.com/s/cbrqbvxot8hfzh0/Valgrinding%20glade.mp4?dl=0
Full valgrind report:
https://gist.github.com/v1993/8da84531b09594fb204b2c66cd882fa8
When mess begins, I usually get segfault when running without valgrind.
Some bugs/leaks
Public bug reported:
On change of user login password with "passwd", the password to unlock
seahorse keyring is not automatically updated. On a subsequent
successful login to Gnome/Unity, a user is prompted to enter his/her
password in a dialogue window that eventually appears when the user
A little correction to the above note: in bug #911426, the problem with
seahorse keyring not being updated was observed when gnome-control-
center was used. In this present case, the problem is observed when
"passwd" is used.
--
You received this bug notification because you are a member of
** Attachment added: "Refer to comment #4."
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1788192/+attachment/5179421/+files/successful%20installation%20of%20pending%20updates%20thanks%20to%20a%20manual%20execution%20of%20plasma-discover.txt
--
You received this bug notification
UPDATE to comment #3.
Executing plasma-discover from a terminal magically solved the issue!
I'll now attach a copy of what displayed in my terminal (see file "successful
installation of pending updates thanks to a manual execution of
plasma-discover.txt").
--
You received this bug notification
Same severe issue here - Kubuntu 18.04.1, recently upgraded from 16.04.5
without problems.
Since base-files 10.1ubuntu2.2 was released, it's been impossible to install it
via Discover. No user password is asked for in order to install the update.
Discover just hangs, even preventing the
Hi Simon, I can confirm the issue is solved (Kubuntu 16.04.4). Thanks!
The Driver Manager now quickly states that no proprietary pilots are available
for my machine (which seems correct since I run with an AMD CPU & GPU).
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Nautilus prompts for username and password when accessing a Samba share
on a network drive, despite having a perfectly valid unexpired Kerberos
ticket. The Kerberos ticket is obtained automatically at logon by
authentication against a Samba Active Directory server (Samba
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514698
Title:
Please remove mplayer-gui from build if it can't be maintained
To manage
I have very similar issues with 4.4.0-116-generic #140-Ubuntu SMP Mon
Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Booting with
the noibpb option does help and I am currently using it as a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@robprije: your suggested workaround in your post #5 above has fixed the
problem for me. Thank you! I had the same symptoms on my workstation,
and here is the relevant error message from syslog:
kernel: [ 1161.995672] compiz-config-p[11373]: segfault at 0 ip
7fb3e82d6d6f sp 7ffdb86ee480
Public bug reported:
It just failed in the middle of installing and told me it was a "bug"
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Public bug reported:
Tearing of the screen in open applications. Tool bar induces tearing of the
screen.
This was not present under earlier versions of Ubuntu operating system.
This is a total new event with this upgrade version I am sorry to say.
As the computer stays on and not rebutted the
Confirming what appears to be the same or very similar issue on Ubuntu
16.04.3. The starting of avahi-daemon and SIGTERM after about a minute
is a cyclical process, repeating every few minutes or hours:
Sep 29 16:01:09 host123 avahi-daemon[7072]: Process 3321 died: No such process;
trying to
Public bug reported:
I have tried the "Partial Update" route, but that also seems broken and
results in the error asking for a bug report to be filed. Couple that
with the now prevalent "Crash Every Time It Starts" problem with
Firefox, and life is not so rosy in Lubuntu land...
ProblemType: Bug
Thanks Kai. Do you refer to comment #10?
Unfortunately this test won't be possible for me, this notebook was lent to me
to eradicate a corrupted Win8 installation (job done - Linux installed) and
I'll soon have to return it to its owner. I prefer to keep a clean fresh
install (even if currently
Linux Mint 18.1 (kernel 4.4.0-72-generic) here.
My case is very similar to the one described by Lucho Nacho.
My mouse is plugged to the 1st USB port (out of 3).
When resuming from 'suspend to RAM', this very USB port 'dies' (until I reboot
my PC that is).
Then plugging in my mouse to the 2nd or
nemo 2.8.7-2~webupd8~xenial1[origin: LP-PPA-webupd8team-nemo]
Confirming this bug on Ubuntu 16.04, 4.4.0-45-generic #66-Ubuntu SMP Wed
Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It's funny.. I have not been able to get it to work correctly; On my
machine, I have 0x1b as the line-out and 0x18 as the line-in as well.
When I override 0x1b with the above settings, no sound comes out on
line-out, although pavucontrol shows activity.
When I override 0x18 with the exact same
Public bug reported:
i don 't know
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: amavisd-new 1:2.10.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sun May 8 00:52:40 2016
@Josh Make sure you are using the only supported installation method,
which is using our `./install.py` script. (See the YCM docs for
details.)
Also, providing the traceback you're getting would go a long way towards
resolving the issue for you. :) Note that the best place to report YCM
bugs is
YouCompleteMe (and ycmd) has been updated to be python 3 compatible
upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538532
Title:
Broken in Xenial, vim requires python3 now
To manage
@Matthias Please note we (the YCM developers) have nothing to do with
the vim-youcomplete package. We don't even like that it exists (the
canonical and _only_ supported way to install YCM is from source with
our `install.py` script). My commitment to have YCM ready for Xenial
refers to our desire
I'm the creator of YouCompleteMe. We're planning on supporting Python
3.3+ by the time Xenial is released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538532
Title:
Broken in Xenial, vim
I guess I'm still not understanding the release process and whether this
is fixed, if there is more information needed, and how we can test it?
Sorry for a newbie question, but what's next?
I don't mind giving it a whirl if someone shares installation
instructions. I'm unclear how to properly
Same problem, LibreOffice 4.2.8.2, build ID: 420m0 (Build:2), Ubuntu
14.04. Clicking on "Create report in design view" produces nothing. The
Report Wizard works, but produces only static reports. Dynamic reports
appear to be broken.
--
You received this bug notification because you are a member
forgot to mention:
I'm on 4.2.3-040203-generic #201510030832 SMP Sat Oct 3 12:34:31 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470730
Title:
[HP
For reference, here's the output on the HP Elitebook 9480m. Not much
difference, except that things are on the Left side. Does that matter?
When should we expect this fix to be rolled in? (don't know how things
work). I tried retasking using hdjackretask, but I was unable to get any
sound out the
I had the wrong package selected. But I'm not sure if this is a pm-utils
issue or a kernel issue.
** Package changed: alsa-driver (Ubuntu) = pm-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
I had the wrong package selected. But I'm not sure if this is a pm-utils
issue or a kernel issue.
** Package changed: alsa-driver (Ubuntu) = pm-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
as a clarification, the 820 has the BT, audio, and camera turned off in
the bios, but the 9480m does not. Those three items are not a variable
in this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I've seen this bug on multiple versions of Ubuntu (14.04 and 15.04) and
with multiple hardware (HP EliteBook 9470m, HP EliteBook 9480m, and HP
EliteBook 820). Not surprising since they appear to share a bios core.
They are all running latest BIOS.
Sleep/resume normally works
as a clarification, the 820 has the BT, audio, and camera turned off in
the bios, but the 9480m does not. Those three items are not a variable
in this issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Confirmed bug - HP EliteBook 9470m and 9480m. Works fine in WIndows.
US UltraSlim docking station (2013 model)
Although I can no longer test it, I believe this issue was also in
14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was apparently introduced in the userspace (evdev) in 12.04
rather than in the kernel. On Christopher Penalver's suggestion, I
created a new bug report,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260513, in order
to investigate this bug further. As described in post 20 in that
*** This bug is a duplicate of bug 1069964 ***
https://bugs.launchpad.net/bugs/1069964
Marty's workaround in post #6 did not work for me until I figured that I
also had to untick the relevant options in Nemo's configuration. It
seems that Gnome might be relying on Nautilus and its
@Reimundo: like in your case, many of my LEDs do not work in the UEFI
mode. I ended up switching to the CSM where the samsung-laptop module is
not blacklisted. Bluetooth and all LEDs on my laptop work just fine in
the CSM. Until the samsung-laptop module is ported to the UEFI, our
Samsung laptops
Just installed the patch from -updates on my production laptop, and the
issue is fixed! Thank you team!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311213
Title:
Evolution 3.10.4 with EWS
@stblack: the fix for this bug involved blackisting the samsung-laptop
module for the UEFI mode. In CMS, the samsung-laptop module is not
blacklisted. Therefore you must use the CMS mode in order to have the
functionality of the samsung-laptop module which includes keyboard
backlighting.
--
You
@Aki Rossi: if handling of UEFI variables was changed in Ubuntu 13.10 to
prevent tickling this bug and (supposedly) the newer Samsung firmware is
not vulnerable to this bug, is it now good time to remove the samsung-
laptop driver from blacklist?
--
You received this bug notification because you
Guys, my apologies, but I don't seem to understand what exactly I need
to do to get this working. I added Moritz' PPA, ran apt-get update,
updated the evolution-data-server component, and was informed by apt-get
that it would be installing thefollowing:
evolution-data-server-common
Brian,
Unfortunately I'm seeing the same behavior even with this patch on my
test environments.
I enabled Trusty-Proposed updates on my package manager and installed
the patch with:
sudo apt-get install evolution-data-server/trusty-proposed
I verified through dpkg -s evolution-data-server that
Public bug reported:
I ran into what appears to be a nasty bug with running the Evolution
email client 3.10.4 downloaded from the Ubuntu 14.04 Software Center
with the Exchange Web Services (EWS) plugin.
After configuring my work Exchange account using EWS, email, contacts,
and calendar
Christopher, to answer your questions:
1) The latest mainline kernel for Oneiric that did not reproduce the bug:
3.2.0-030200rc4 (201112012035).
2) The earliest mainline kernel for Precise that did reproduce the bug:
3.1.5-030105 (20111209125).
This info is in post #18 above:
Christopher, I have tested v.3.14-rc7 which is now the latest mainline
kernel:
val@vk2011:~$ uname -a
Linux vk2011 3.14.0-031400rc7-generic #201403162235 SMP Mon Mar 17 02:36:19 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
The result is the same as in prior tests: the horizontal scrolling is
broken
Christopher, unless I do something this bug is going to expire in a
couple of weeks. I don't want it to expire into a mass grave of orphaned
bugs. I've invested a significant number of hours investigating it, all
in the hope that my work won't be wasted, all in an attempt to make
Ubuntu more
Christopher, as I wrote in post #18 above the horizontal scrolling works
fine in the last mainline kernel for Oneiric and it is broken in the
first mainline kernel for Precise, chronologically speaking.
Horizontal scrolling works fine in every mainline kernel for Oneiric
that I tested, and it is
Christopher, do you have any suggestions as to what I should try next? I
am still confused, and I do not understand why my test results on
Precise are different from Oneric where the same kernel version is used
in both installs.
--
You received this bug notification because you are a member of
Christopher, I am a bit stumped. What I am getting does not make much
sense.
Test 1: 11.10 Oneiric, mainline kernel 3.2.0-030200rc4 (201112012035). This is
the last mainline kernel for Oneiric from
http://kernel.ubuntu.com/~kernel-ppa/mainline/.
Test Result: horizontal scrolling works properly.
that is generated when the USB
mouse is plugged in. This is 3.2.0-030200rc4. Precise 3.2.0-23 and
3.1.5-030105 generate very similar logs:
Jan 22 00:18:18 val-1110 kernel: [ 55.856260] usb 2-2: new full-speed USB
device number 3 using ohci_hcd
Jan 22 00:18:18 val-1110 mtp-probe: checking bus 2
The bug is still present in Trusty daily build trusty-desktop-amd64.iso
(15-Jan-2014 07:50) with mainline kernel 3.13.0-031300 (20-Jan-2014):
uname -a
Linux vk2011 3.13.0-031300-generic #201401192235 SMP Mon Jan 20 03:36:48 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed:
Christopher, as I noted in my initial submission this bug is a sequel to
LP bug #926917 and the problem has persisted with every Ubuntu release
since 12.04. That information was unfortunately edited out from my
initial submission. This bug was created on your request because the
original submitter
Christopher, this problem did not exist prior to 12.04. It seems to be a
regression in 12.04. I have been using the same mouse+keyboard combo
since 8.04 or so, and it is only in 12.04 that my mouse tilt (horizontal
scrolling) got broken.
--
You received this bug notification because you are a
Christopher, can you tell if trying all these different kernels can be
done in a guest OS in Virtualbox? To identify the offending commit I
will need to do quite a few reboots. Doing such reboots on my main
workstation means a lot of time would be wasted to idling while my
computer reboots. I
Confirming that the reported issue is still present on Trusty as of
December 12th, 2013 development build.
Also, I should note that a fix to this issue was proposed in LP #926917.
The proposed fix worked perfectly for me on LTS 12.04.
--
You received this bug notification because you are a
Christopher, please can you clarify your terminology? I know what the
mainline kernel is but I am not sure what you mean when you say
repository kernel. Which repository?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-generic x86_64
ApportVersion: 2.12.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: val2055 F pulseaudio
/dev/snd/controlC1: val2055 F pulseaudio
/dev/snd/controlC0: val2055 F pulseaudio
CurrentDesktop: Unity
Christopher, my hardware information is in LP #1260513.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975724
Title:
045e:071d External mouse horizontal scrolling no longer works
To manage
Christopher,
My USB listing is attached. As you requested, I unplugged all USB
devices first, then plugged in the mouse device (note important details
below) and then executed lsusb -v, with sudo of course.
Please note that this problem is specific to the mouse, not to Gateway
DX4860. This
Soos Gergely,
Thank you for bringing the issue of compiz support (of lack thereof) in
future versions of Ubuntu to our attention. I admit I have not even
considered the possibility that compiz may become unavailable in future
versions. This is alarming and upsetting. I like Ubuntu, it has been my
Christopher,
I did not change any kernel parameters during Ubuntu 12.10 installation. My
installation process is described in detail in comment #114 to LP: #1040557.
For convenience, here is a direct link:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557/comments/114
I thought that
Christopher: my Samsung notebook model is NP700Z5C-S03CA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114856
Title:
power button not working using non-default kernel parameters, when
Samsung
Confirming the exact same problem: Acer Aspire V5 with Windows 8 pre-
loaded and Ubuntu 13.10 installed alongside it. With UEFI Secure Boot,
Windows cannot boot from Grub - the error message is the same as
described by previous observers.
--
You received this bug notification because you are a
@Fabio: if you completely remove Win8, you will likely lose the ability
to upgrade your machine's firmware. The firmware can be upgraded only
with Samsung Updater - a Windows application.
If Win8 does not start from your newly installed Grub, you are probably hitting
the known bug:
@Gilbert: see paragraph no 14 in post #114 for a fix to this problem.
It's a known bug in update-grub - Windows EFI boot entries are not
generated correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Steve or anyone who has access to the lines of communication with
Samsung engineering team!
PLEASE can you ask the Samsung people to PLEASE clarify whether this bug
has been fixed in the latest firmware? Or at least if they believe that
it has been fixed?
I am willing to risk my NP700Z5C and
@Rui Covelo: You're doing nothing wrong, unfortunately the workaround
has the problem you mentioned. It gets stuck everytime the command is
called twice which typically happens when you hit the screen edge while
the window picker is still active.
--
You received this bug notification because you
Everyone who is attempting to upgrade BIOS, beware that the Ubuntu EFI
boot option is erased during the upgrade process. The entry in the Boot
Priority Order is gone after the upgrade, and you will need to install
EFI grub to be able to continue using Ubuntu in the EFI mode. The
upgrade process
Allright, the 3.8 mainline kernels for Quantal are probably not going to
appear in the Mainline Builds ppa any time soon. I took some time today
to try and install Raring AMD64 from daily builds on my Samsung NP700Z5C
and see if the problem with the power button is still there.
It is important to
@Yekeen Ajeigbe: if you want to be certain that your laptop survives
Ubuntu installation, install it in the CSM mode (BIOS compatibility mode
- should be an option in your system BIOS configuration). As many people
pointed out here, laptops do get bricked under certain circumstances in
the UEFI
** Attachment added: samsung-powerbutton.tgz
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1114856/+attachment/3562858/+files/samsung-powerbutton.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Joseph, I have just posted a tgz with the requested output.
It looks like I should try booting the installed version without
acpi=noirq. Right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114856
Allright. Once acpi=noirq is removed from the command line, power button
starting working just fine.
@Joseph: do you want me to post log files with acpi=noirq removed?
The still unexplained phenomenon is: in the UEFI mode, power button
works fine regardless of whether acpi=noirq is present or
Joseph, it looks like as of today I can only test on mainline kernel
v3.5.7.4-quantal. Versions v.3.6 and higher likely do not contain the
bugfix for LP: #1040557, which is known to brick Samsung laptops like
mine.
I received a tip that a new Quantal kernel will be coming to -proposed
next week.
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-23-generic 3.5.0-23.35
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: val
Emanuel: there seems to be a way to recover at least some Phoenix BIOSes with
Crisis Recovery Disk Tool:
http://www.bios-mods.com/bios-recovery/phoenix-bios-recovery/
I have not tried this tool and I cannot say whether this will help you
or not. But, with a computer already bricked, it probably
Ok problem solved. The surround speaker was muted, I unmuted it in
alsamixer with 'm' key. Then I increased the sound in surround speaker.
Thanks to all
2013/1/29 Raymond 1106...@bugs.launchpad.net
Hello,
I did the proceedings and unmuted all that I could.
But there is still no sound coming from the speakers. The headphones are
working.
May find attached a screenshot of alsamixer.
Maybe the issue is visible on it.
Thanks
2013/1/26 Dave Lentz 1106...@bugs.launchpad.net
echo options
2013/1/26 Dave Lentz 1106...@bugs.launchpad.net
echo options snd-hda-intel model=mbp55 | sudo tee -a
/etc/modprobe.d/alsa-base.conf
sudo alsa reload
pulseaudio -k
alsamixer
In alsamixer, make sure everything's unmuted. Do you have sound now?
--
You received this bug notification because
Public bug reported:
Hi,
Freshly installed ubuntu. There is no sound coming from the built-in speakers.
With earphone it works well.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
Uname:
Daniele -- other Linux distributions may or may not have this problem.
Also, they may have other problems that are not present in Ubuntu. It is
all a matter of trial and error and publicizing the results. However,
what we do know at this point is that the removal of samsung-laptop
kernel module in
Excellent work Miroslav! I installed your deb on both my 12.04 and 12.10
installations (both are 64-bit), and indicator-weather now works like a
charm on both machines!
Thank you!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Steve, could you clarify the relationship between the samsung-laptop
module that was the likely cause of bricks under UEFI, and the samsung-
laptop package in https://launchpad.net/~voria/+archive/ppa ? Should we
make Fortunato Ventre, the maintainer of the package, aware of this bug?
--
You
Arthur -- yes, to the best of my knowledge it should be safe to install
Ubuntu 12.04 from a latest daily build on your Samsung laptop. These
latest builds incorporate the same fix that worked for me.
However, if you want to be completely certain before attempting this
potentially risky process,
Steve, I have a question for you. There is a package out there named
'samsung-laptop' that is maintained by Fortunato Ventre,
https://launchpad.net/~voria/+archive/ppa. Do you know if the kernel
module with the same name, the one that triggers this bug, is somehow
related to the 'samsung-laptop'
Okay, thank you Žygimantas, I see that it's not Voria's 'samsung-laptop'
module that bricks laptops but its Quantal derivative. The practical
issue for us owners of Samsung Chronos 7 series laptops is whether other
packages are safe or not for us in
https://launchpad.net/~voria/+archive/ppa. After
I am delighted to report that Ubuntu 12.10 64-bit is now running on my
Samsung NP700Z5C, dual booting in UEFI mode from Grub2 to either Ubuntu
or pre-installed Windows 8.
My installation process is described below. However, the nature of this
bug is such that you should consider very carefully if
I am a bit stuck... need some ideas. Steve?
Here is what I have done so far:
1. switched to the CMS mode, installed Ubuntu, rebooted
3. installed Colin King's patches, rebooted, removed all previous kernel images
just in case, rebooted again and verified that indeed I have the correct
patched
Denise,
There is much more to this bug than removing a file. Unless you don't
care about your Samsung laptop, do NOT attempt installing Ubuntu on it
until a reliable fix is available. You definitely do not want to turn
your first Ubuntu experience into a disaster. This bug is *extremely*
serious.
And just to clarify my point, I am not suggesting that Canonical or the
Ubuntu team are responsible for this bug. It is the introduction of the
UEFI that brought this new world in existence where some software bug
can destroy a motherboard and brick a computer. For the folks like me
who have lived
Interestingly, I can get Ubuntu Live CD 12.10 x86_64 to boot my Samsung
NP700Z5C in Secure Boot (!) with Try Ubuntu without installing with
all the factory BIOS settings, except that the FastBIOS mode has been
disabled and the boot order has been changed accordingly to allow
booting from the Live
Steve, I am trying to decide whether I should attempt installing Ubuntu
on my Samsung NP700Z5A (and of course risk bricking the laptop in the
process) through the route of CMS boot + Colin King's patch, meaning the
route you proposed, or through the Secure Boot route.
I thought I should try to
1 - 100 of 379 matches
Mail list logo
