further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next ... so possibly this already appears somewhere
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next ... so possibly this already
), using batteries however
reproducible within = 30min (it just happens).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash
actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next
hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next ... so possibly this already appears somewhere
---
ApportVersion
- nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next ... so possibly this already appears somewhere
---
ApportVersion: 2.14.1-0ubuntu3.2
times and under different identities (as tge and
lightdm), with additional background processes ... This was quite annoying
but not first priority and I could not
imagine that there might be a relationship, therefore I also did not take
any notes/screenshots/... - not more details available
further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where
that data ended up and what to do next ... so possibly this already
appears somewhere
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment
, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
- PS: I used the GUI-based crash reporting function but have no clue where
- that data ended up and what to do next ... so possibly this already
- appears somewhere
+ PS
).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what
).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what
actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next
).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what
).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what
).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what
).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do
process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next ... so
).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do
).
Affected actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do
actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next
actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next
actual process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next
process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next ... so
process (mozStorage in this example) varies, ultimately the
OS hangs.
Used memtest86 - nothing found.
If there is any further info needed, pls let me know!
Thx!!
tge
PS: I used the GUI-based crash reporting function but have no clue where that
data ended up and what to do next ... so
Rgd bluetooth - well, actually the GUI status says so, but:
tge@nutmeg:/tmp$ ps -ef | grep blue
root 726 1 0 Jun01 ?00:00:00 /usr/sbin/bluetoothd
tge 2910 2472 0 Jun01 ?00:00:00
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
tge
25 matches
Mail list logo
