Hi Agustin, after a long period of fails, I finally at least can mount
the drive via commandline script like:
> #!/bin/bash
> sudo cryptsetup luksOpen /dev/sdx# sdx#_crypt
Attention: the number "#" is not always the same. Normally it is for
e.g. "/dev/sdb1" something like "sdb5_crypt"
Good luck
Hi,
affects me too after update on 18.04. After installing libblockdev-
crypto2 and system restart, I get the error:
"Error unlocking /dev/sdx1. Failed to activate device: Operation not
permitted"
I tried a lot of things:
* Start gnome-disks as root
* Open Luks and mount via cryptsetup on com
It turned out that the combination of blender / pulseaudio and the log-
level of pulseaudio was the problem. When I open Blender then suspend
the machine and resume again, the above error immediately fills the
logfile with tons of data. The problem persist until blender is stopped.
So first I did
I have the exact same problem here with Standard Ubuntu 16.06:
The ~/.cache/upstart/unity7.log file is filled with this crap over and
over after suspend /resume:
"AL lib: (EE) ALCplaybackAlsa_mixerProc: start failed: File descriptor
in bad state"
I am using blender and firefox simultaneously.
-
*** This bug is a duplicate of bug 1574168 ***
https://bugs.launchpad.net/bugs/1574168
@giovanni-g: did not work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573279
Title:
package mys
*** This bug is a duplicate of bug 1574168 ***
https://bugs.launchpad.net/bugs/1574168
Thanks. But did not work. I tried this before (really tried everything I
could imagine).
whereas the list of duplicate bugs in bug #1571865 rises and rises
;-( But I am shure guys at ubuntu will fix t
*** This bug is a duplicate of bug 1574168 ***
https://bugs.launchpad.net/bugs/1574168
FIRST: I think this should be the primary bug (not duplicate of #1574168 or
#1574204 ) and because it has the most useful information in it. Someone should
fix this.
--
S
Addendum:
[4] DISABLE THE GNOME3-STAGING ppa so that your freshly installed 16.04
would not be messed up:
... by uncommenting the sources.list entry in
/etc/apt/sources.list.d/
gnome3-team-ubuntu-gnome3-staging-xenial.list
And do an:
> apt-get update
[5] after test you could purge the ppa wit
I just tried to give evolution 3.19 a try.
So I enabled (temporally) the gnome3-staging ppa, installed the evolutin
3.19 packages, but I still receive an error, when connecting to google
address book:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code5:
I also cannot
See: http://askubuntu.com/questions/593696/thunderbird-window-gets-
stuck-maximized-with-no-window-controls/697840#697840
This did not help: the only thing helped was
First exit Firefox, then rename localstore.rdf and xulstore.json in the
profiles directory of thunderbird:
cd ~/.thunderbird/you
Hi YouDontNeedMyName (why?),
sudo apt-get install php5-apcu/trusty-backports
By the way: this solution is mentioned in the thread from github that
directed you here in the last post from me and stieler-it ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
... That means, the problem is
1. not fixed for Ubuntu LTS 14.04 and major (!) third party packages, that need
this (owncloud)
2. this bug is not a duplicate of but #1500167 which asks explicitely for the
BACKPORT repo
So I think the duplicate flag should be removed and this should be
resolved
Hi,
at the moment
* php5-apcu_4.0.7-1build1~ubuntu14.04.1_amd64.deb
reached me with the standard update procedure from trusty/backports
repo:
root@server:~# apt-show-versions php5-apcu
php5-apcu:amd64/trusty-backports 4.0.7-1build1~ubuntu14.04.1 uptodate
So at least if this repository is enab
Hey.
This version switched to 4.0.7 meanwhile if you are looking into the
archive ;-)
The problem nevertheless is very annoying, because it is needed for e.g.
the actual owncloud server 8.2 !
The 4.0.7 version from 14.10 seems to be not installable in 14.04 LTS because
of dependecy problems:
Hi,
I had the same problem with a K800 Keyboard from Logitech.
a better way would be to edit the file
/etc/initramfs-tools/modules
and add
hid-logitech-hidpp
there.
Then it is sufficiant to to
sudo update-initramfs -c -k $(uname -r)
for the running kernel (or "-k all" for all kernels).
Co
Addendum: Here you can find an impressive Screenshot about this issue:
http://askubuntu.com/questions/589552/black-spaces-around-windows-and-
control-panels-ubuntu-14-04-unity-compiz-met
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi arcticpenguin,
Today, aber resume from suspend the black boarders have been there
again. So it worked for at least 3 days - which means, on the other
hand, it is not solution in the end ;-(
... searching for a solution goes on
I will post here and here for my W510: https://wiki.blue-
it.org/T
Hi there,
this bug drives me crazy since I use Ubuntu 14.04. Due to the fact, that
I am using VirtualBox for developping and Remmina (for RDP sessions to
my business) this gives me from time to time an unaccessible system.
I then have to login remotely an "setdid unity" or "compiz --replace".
Wh
Hi,
as my solution of 239 finally did not work for me, I tried:
vim /etc/X11/xorg.conf
Section "Device"
Identifier "DefaultDevice"
Option "NoLogo" "True"
Option "RegistryDwords" "EnableBrightnessControl=1"
# Prevents: Together with CCSM-> OpenGl -> disab
Hi,
on Ubuntu 14.04 according to this thread:
* http://askubuntu.com/questions/125367/enabling-mic-mute-button-and-
light-on-lenovo-thinkpads
I cannot see
/sys/devices/platform/thinkpad_acpi/leds/tpacpi::micmute/brightness as a
link in /sys/devices/platform/thinkpad_acpi/leds:
# ls /sys/device
Hi there,
as I posted above, I have the same issue on my Thinkpad W510. I edited a resume
script in /etc/sleep.d as followed:
vim /etc/pm/sleep.d/03_bug_nvidia_unity_replace
chmod + x
#!/bin/sh
#
# after suspend restart unity, because of artifacts
for USR in "$(ps aux |grep unity-panel-
Further reading offers at
http://www.ubuntuupdates.org/package/core/precise/main/proposed
/libreoffice-evolution?id=441432&page=2
Package "libreoffice-evolution"
WARNING: the "libreoffice-evolution" package was deleted from this
repository
Name: libreoffice-evolution
Description:office p
UPDATE, but no solution:
Searching for a solution I stumbled upon ubuntupdates.org:
http://www.ubuntuupdates.org/package/libreoffice/trusty/main/base
/libreoffice-gnome
>From the description:
Package "libreoffice-gnome"
This package belongs to a PPA: LibreOffice
[...]
You can extend the f
Public bug reported:
Hi,
why is there no package for libreoffice-evolution (and other e.g.
exchange) connections any more since precise? This is crucial for
connection the standard addressbook with theese external DataSources.
Greets
Axel
** Affects: libreoffice (Ubuntu)
Importance: Undeci
Is there any progress in this?
It would be an excellent feature, of working. I am using 3 three
business machines and a laptop at different places and I would like to
synchronise the installations this way. In the moment i am doing this
manually with dpkg --get-selecitons and apt-clone. But this w
I had the same problem after updates:
After
service apparmor teardown
I can shutdown the machine.
So this is definitely a problem of apparmor.
I did:
apt-get install --reinstall apparmor
And it works now.
A file named usr.sbin.libvirtd.dpkg-dist did not exist on the system
Greets
Hi,
I can confirm this behaviour. the solution withint post number #8 indeed
resolves the problem.
* Ubuntu 14.04 h
* Lenovo W510
* Card: NVIDIA Corporation GT216GLM [Quadro FX 880M]
* Driver: nvidia-331, 331.38-0ubuntu7, amd64, NVIDIA binary driver - version
331.38
--
You received this bug no
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
[UPDATE 05th March 2014]
The lenovo service was here and changed the mainboard.
No problems any more with a Crucial M500 480 GB and therefore
I think wit
[UPDATE 05th March 2014]
The lenovo service was here and changed the mainboard.
No problems any more with a Crucial M500 480 GB and therefore
I think witch any other SSD on the W510.
So the problem turned out a real hardware problem.
The lenovo
[UPDATE 05th March 2014]
The lenovo service was here and changed the mainboard.
No problems any more with a Crucial M500 480 GB and therefore
I think witch any other SSD on the W510.
So the problem turned out a real hardware problem.
The lenovo
Hi,
[Crucial M500 - a hope? - NO]
---
after returning the Samsung and found this thread in the lenovo forum:
http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/W510-SSD-My-
Story/m-p/1402387
my hope was the Crucial M500 should be compatible to the W51
Fri, 24 Jan 2014 08:54:15 +0100
08:54:15 up 1 day, 20:49, 4 users, load average: 0,90, 2,21, 1,61
Hi again,
as said in comment #50, I put a clone of the SSD, Seagate Momentus XT Hypbrid
into the laptop.
As you can see, the system is running wit
** Summary changed:
- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only
Filesystem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I will test now a STANDARD HARDDRIVE CLONE known to work with
- mainline kernel
- tlp uninstalled / installed
- standard grub and bios settings
Please be patient for news.
I will report when all tests are done (except you have any suggestions).
Greets
Axel
--
You received this bug notificatio
dmesg for sytem running from 2014-01-19 to 2014-01-21
/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.noacpi=1"
/etc/modprobe.conf
options libata noacpi=1
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3954235/+f
Duplicate bug?
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/984127
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden
DIARY since Wed, 15 Jan 2014
** Attachment added: "Diary since Jjan 15th. 2014"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3954222/+files/20140115-20140121_bug_report_diary.txt
--
You received this bug notification be
##
DIARY since Wed, 15 Jan 2014
-
Please see the attached log of this post for the last 6 days.
##
CONCLUSION (mainline kernel)
-
dmesg since 2014-01-21 with
/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
libata.noacpi=1 libata.force=1:3.0Gbps,2:1,5Gbps,2:40c
modprobe.blacklist=pata_acpi "
/etc/modprobe.d/blacklist-pata_acpi.conf
blacklist pata_acpi
/etc/modprobe.conf
options libata noacpi=1 force=1:3.0Gbps,2:
Fri, 17 Jan 2014 12:54:39 +0100
hard link reset ata1 -> readonly filesystem
=> Booting now with PCI-Express powermanagement disabled in BIOS !
Some comments:
NCQ
-
When I am diving into the subject, I see this NCQ kernel e
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem
To manage noti
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.13.0-031300rc8-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung
** Summary changed:
- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystem
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem
** Description changed:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following prob
** Attachment removed: "/etc/default/tlp"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950651/+files/tlp
** Attachment added: "tlp-stat.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950663/+files/tlp-stat.log
--
You received t
The /etc/default/tlp for sake of completeness ;-)
** Attachment added: "/etc/default/tlp"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950651/+files/tlp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
##
DATE: Fri, 17 Jan 2014 08:14:35 +0100
UPTIME: 08:14:35 up 6:21, 3 users, load average: 0,18, 0,70, 0,88
KERNEL: 3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 10:36:21 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
###
** Attachment added: "proc_modules.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950623/+files/proc_modules.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126977
** Attachment added: "proc_ioports.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950616/+files/proc_ioports.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126977
** Attachment added: "dmesg_egrep_ata_scsi_BOOT.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950612/+files/dmesg_egrep_ata_scsi_BOOT.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Yesterday evening I applied the Thinkpad dock / undock scripts from
comment #34
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/34).
I also installed tlp, which cares mainly for network interface switching
upon dock / undock evnets (see config attached).
I rebooted the pc w
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950611/+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/1269777
Title:
[
I rebooted with the paramters of comment #33 (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/33).
PCIE powermanagement is DISABLED in the BIOS.
Then I did the undocking operation:
It is working like expected without any problem!
[ 1866.096092] thinkpad_acpi: undocked from
ANALYTICS:
---
If you look at comment #31
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/31),
you will notice in dmesg.log (which I could safe at runntime to /tmp and
copy it over to another pc), that the freeze occurs right after taking
the system from the
Booting now the mainline kernel.
BIOS: turned powermanagement for PCI to AUTOMATIC, for PCIE (!) to
Disable
##
Thu, 16 Jan 2014 22:43:27 +0100
- Booting now with last mainline kernel linux-image-generic
3.13.0-031300rc8-gener
Running the mainline kernel for 3 hours now. PCI(e) powermanagement is
enabled and SATA is working in AHCI mode. This caused the standard
kernel 3.13.0-3-generic
##
DATE: Thu, 16 Jan 2014 22:31:11 +0100
UPTIME: 22:31:11 up 2:58, 4 use
What I did was taking the PC from the docking station, switch of LAN and
switch on WLAN.
Started a program to whatch TV (mythfrontend).
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950407/+files/dmesg.log
--
You received this bug
As time of writing, the error occured!
#
DATE: Thu, 16 Jan 2014 22:31:11 +0100
UPTIME: 22:31:11 up 2:58, 4 users, load average: 0,13, 0,29, 0,27
STATUS: dmesg | egrep ata|scsi|BOOT
[0.00] Command line: BOOT_IMAGE=/vmlinuz-3.13
Running the mainline kernel for 3 hours now.
PCI(e) powermanagement is enabled and SATA is working in AHCI mode.
Started virtualbox, worked a lot with the system, ... no problems occured ...
Under the same conditions, the standard kernel 3.13.0-3-generic caused
the system to freeze.
I' investig
** Attachment added: "usr_src_3.13.0-031300rc8-generic_scripts_ver_linux"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950241/+files/usr_src_3.13.0-031300rc8-generic_scripts_ver_linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "proc_modules.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950239/+files/proc_modules.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126977
** Attachment added: "proc_iomem.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950237/+files/proc_iomem.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269777
T
** Attachment added: "proc_scsi_scsi.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950240/+files/proc_scsi_scsi.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12
** Attachment added: "proc_ioports.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950238/+files/proc_ioports.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126977
** Attachment added: "ls_proc.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950235/+files/ls_proc.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
** Attachment added: "proc_cpuinfo.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950236/+files/proc_cpuinfo.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126977
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950234/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
Sorry the last dmesg.log was the wrong for this bios settings ...
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950227/+files/dmesg.log
** Attachment removed: "dmesg_egrep_ata_scsi_BOOT.log"
https://bugs.launchpad.net/ubuntu/+so
** Attachment added: "hdparm-I.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950213/+files/hdparm-I.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950216/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269777
T
** Attachment added: "dmesg_egrep_ata_scsi_BOOT.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950214/+files/dmesg_egrep_ata_scsi_BOOT.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950215/+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/1269777
Title:
[
##
Thu, 16 Jan 2014 19:08:54 +0100
- Booting now with last mainline kernel linux-image-generic
3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 10:36:21 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
- BIOS:
SATA: AHCI,
Hi Christopher,
I am now still in AHCI mode with PCI(e) powermanagement off in bios.
The system is absolutely stable.
hdparm -I /dev/sda attached
Do you need this with PCI(e) powermanagement enabled?
** Attachment added: "hdparm -I /dev/sda"
https://bugs.launchpad.net/ubuntu/+source/linux
** Description changed:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:
1. System
--
- Ubuntu 14 04 LTS (acutal development branch)
- linux-image-generic v. 3.13.x, mainline kernel 3.13.x (first testing the
stan
** Description changed:
+ Like mentioned in bug #1266305 (and before in bug #1265309) the
+ following problem occured:
+
+ 1. System
+ --
+
+ - Ubuntu 14 04 LTS (acutal development branch)
- linux-image-generic v. 3.13.x, mainline kernel 3.13.x (first testing the
stan
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Summary changed:
- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystems
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystem
--
You re
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "dmesg_egrep_ata_scsi_BOOT.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950081/+files/dmesg_egrep_ata_scsi_BOOT.jpg
--
You received this bug noti
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950079/+files/dmesg.log
--
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
Thu, 16 Jan 2014 13:18:45 +0100
- installed linux-image-generic -> 3.13.0-3-generic
- BIOS: switched AHCI, and pci/pcie power management
###
>> I filed a new bug due to new "new hardware" and new environment: bug
#1269777
###
Please be aware that this is a duplicate bug of the above one and bug
#1265309
--
You received this b
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "BIOS Mode Compat 2 - SATA"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950030/+files/20140116_45.jpg
--
You received this bug notification becau
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "BIOS Mode Compat 2 - POWER"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950031/+files/20140116_28.jpg
** Changed in: linux (Ubuntu)
Status
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950025/+files/dmesg.log
--
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "lsb_release-rd.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950026/+files/lsb_release-rd.log
--
You received this bug notification because you a
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950028/+files/uname-a.log
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950029/+files/version.log
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
Public bug reported:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:
1. System
--
- Ubuntu 14 04 LTS (acutal development branch)
- linux-
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950027/+files/lspci-vvnn.log
--
You received this bug notification because you are a mem
Unfortunately the lttng-modules for the kernel 3.13 are not installable.
Any advise for another tool to trap kernel messages?
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1267652
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please give me a few days of doing a clear testing plan about this.
** Description changed:
After a while of running the system, the SSD goes into a readonly file
system mode.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.23
ProcVersi
** Attachment added: "20140115_09-00_dmesg_error_grep_ata.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266305/+attachment/3949127/+files/20140115_09-00_dmesg_error_grep_ata.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "20140115_09-00_dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266305/+attachment/3949128/+files/20140115_09-00_dmesg.txt
** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member o
Hi, unfortunately my enthusiasm was a little bit too big.
Yesterday I got a freeze again, but this time a little time after wakeup
from standby.
- I tried then the kernel 3.12.7-031207-generic (which is the last trusty
kernel for the 3.12 line).
- I uninstalled tlp ro minimize side effects.
- I
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1266305/+attachment/3949130/+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/1266305
Due to the fact, that the drive was returned but was OK (tested in
another system), I marked the bug "Opinion" so that it is closed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Hi Christopher, thank you for the explanations.
I returned the EVO 840 and got the EVO 840 Pro instead from my local reseller.
So I cannot test any more into the subject.
I learned a lot about filing bugs in ubuntu, so this was very interesting.
Thank you for your advise so far.
I found another
A few hours ago I got a new Samsung EVO 840 Pro. I made a clone of the
actual system.
I booted up, stress tested the system (4GB file video conversion while running
a virtual machine, ...).
It runs for 3 hours now. Not any single problem so far.
MY PERSONAL CONCLUSION:
DON'T USE THE SAMSUNG EVO
Thanks Christopher for your advice.
Yes the firmware of the Samsung EVO 840 was updated to the latest one
(last firmware Dec.' 13) with the Samsung Magician software. I checked
the update twice after a reboot.
I have to add: the new replacement drive is an exact 1:1 copy of the
SSD, and shows no
Thanks Christopher for your answer.
I could not test the upstream kernel due to massive problems with the nvidia
card.
And I first wanted to the test the standard distribution - as advised.
Sorry for the wrong tagging this way ..
Nevertheless: tomorrow I try to return the drive, because it turns
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1266305/+attachment/3946973/+files/AlsaInfo.txt
** Tags removed: needs-upstream-testing
** Tags added: needs-upstream-testing-3.13.0-1.16
--
You received this bug notification because you are a member of
1 - 100 of 291 matches
Mail list logo
