[Desktop-packages] [Bug 1021375] Re: Nautilus says the USB stick is read only when it is not

2014-01-02 Thread Johann Gail
I have the read-only bug under a slightly different condition: Its not a
external USB-Stick but a remounted partition.

For security reasons I have an archive partition which is mounted read-
only at startup of the notebook. When I mount the partition afterwards
in readwrite-mode then nautilus tells me, the partition is still read-
only. But all other tools, commandline etc. works fine.

So it seems to me, this bug has something to do with in-memory cached
directory information in nautilus. Maybe this information gets cleared
during logout/login, so it is not the observed line in the .config but
the process of relogon which solves this problem?

I have this effect since at least two years and with different versions
of ubuntu. For sure with 12.04, 13.04, 13.10 and all updates between
them. For me this bug is allways fully reproducible.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1021375

Title:
  Nautilus says the USB stick is read only when it is not

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is not.

  I tested it with two different USB sticks in two different computers
  running Ubuntu 12.04 and the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1021375/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 982889] Re: X trying to start before plymouth has finished using the drm driver

2013-06-09 Thread Johann Gail
Either this fix isn't complete or I have a similar problem.

On my fast hardware (a Clevo W370ET with SSD and a quad core i7) I
observe the same effects. Even after updating to latest versions I get
the fault. I'm running raring (XUbuntu 13.04).

I observe at 50% of booting a black screen with a blinking cursor and a
mousepointer. I can switch to a terminal console and by entering the
command sudo service lightdm restart I get a running graphical
session.

Also the workaround at comment #5, inserting a sleep 1 in lightdm.conf
does help. But I doesn't like the idea of solving a race condition by
inserting some sleep. Especially on a fast booting ssd notebook.

Should I open a new bug report or should I continue tis one?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889

Title:
  X trying to start before plymouth has finished using the drm driver

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project precise series:
  Fix Released
Status in “gdm” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  New
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “plymouth” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Precise:
  New
Status in “kde-workspace” source package in Precise:
  New
Status in “lightdm” source package in Precise:
  Fix Released
Status in “plymouth” source package in Precise:
  Fix Released
Status in “gdm” source package in Raring:
  New
Status in “kde-workspace” source package in Raring:
  New
Status in “lightdm” source package in Raring:
  Fix Released
Status in “plymouth” source package in Raring:
  Fix Released
Status in “gdm” source package in Saucy:
  Fix Released
Status in “kde-workspace” source package in Saucy:
  New
Status in “lightdm” source package in Saucy:
  Fix Released
Status in “plymouth” source package in Saucy:
  Fix Released

Bug description:
  X server fails to start the first time after boot, it works fine when
  I start it again.

  Looks like a race condition with intel drm initialization, i guess X
  tries to start faster than drm driver is initialized so it fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Apr 16 10:35:28 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:7750]
   Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] 
[1002:6738] (prog-if 00 [VGA controller])
 Subsystem: Giga-byte Technology Device [1458:21fa]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: MSI MS-7750
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic 
root=/dev/mapper/ssd-ubuntu--precise ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68A-G43 (G3) (MS-7750)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7750
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.7.6-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  

[Desktop-packages] [Bug 1176510] [NEW] gstreamer-1.0/libgsttypefindfunctions.so has a segmentation fault

2013-05-05 Thread Johann Gail
Public bug reported:

If I start rhytmbox on the new ubuntu 13.04 raring ringtail (amd64) then
i get the following message:

ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgsttypefindfunctions.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap --gst-disable-registry-fork and debug.


The installed version of gstreamer1.0-plugins-base is 1.0.6-1.

The error occurs, when I try to play any mp3.

** Affects: banshee (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/1176510

Title:
  gstreamer-1.0/libgsttypefindfunctions.so has a segmentation fault

Status in “banshee” package in Ubuntu:
  New

Bug description:
  If I start rhytmbox on the new ubuntu 13.04 raring ringtail (amd64)
  then i get the following message:

  ERROR: Caught a segmentation fault while loading plugin file:
  /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgsttypefindfunctions.so

  Please either:
  - remove it and restart.
  - run with --gst-disable-segtrap --gst-disable-registry-fork and debug.

  
  The installed version of gstreamer1.0-plugins-base is 1.0.6-1.

  The error occurs, when I try to play any mp3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1176510/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp